bereach-openclaw 1.4.2 → 1.4.4

package/openclaw.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "bereach-openclaw",
   "name": "BeReach",
-  "version": "1.4.2",
+  "version": "1.4.4",
   "description": "LinkedIn outreach automation — 75+ tools, hook-based enforcement, dynamic context",
   "configSchema": {
     "type": "object",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bereach-openclaw",
-  "version": "1.4.2",
+  "version": "1.4.4",
   "description": "BeReach LinkedIn automation plugin for OpenClaw",
   "license": "AGPL-3.0",
   "exports": {
@@ -18,7 +18,7 @@
     "bereach"
   ],
   "dependencies": {
-    "bereach": "1.4.2"
+    "bereach": "^1.4.3"
   },
   "devDependencies": {
     "@types/node": "^25.5.0",

package/skills/bereach/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: bereach
 description: "Automate LinkedIn outreach via BeReach (berea.ch). Use when: prospecting, engaging posts, scraping engagement, searching LinkedIn, managing inbox, running campaigns, managing invitations, analytics, company pages, Sales Navigator, content engagement, feed monitoring. Requires BEREACH_API_KEY."
-lastUpdatedAt: 1774226316
+lastUpdatedAt: 1774303632
 metadata: { "openclaw": { "requires": { "env": ["BEREACH_API_KEY"] }, "primaryEnv": "BEREACH_API_KEY" } }
 ---
 
@@ -26,7 +26,7 @@ Load sub-skills **on-demand** when the user's request matches a workflow. No nee
 | Lead Gen              | lead gen, find leads, search, qualify, ICP, pipeline, build list, scrape engagement, competitor, grow database, prospecting, hashtag, Sales Navigator         | sub/lead-gen.md          | 1774186410    |
 | Outreach              | outreach, connect, DM, message, follow up, sequence, connection request, reply, personalized outreach, campaign outreach, warming, follow, like post, draft, batch, withdraw, human review | sub/outreach.md          | 1774186410    |
 | OpenClaw Optimization | openclaw, model, opus, sonnet, haiku, config, SOUL.md, heartbeat, prompt caching, AI cost reduction, /model               | openclaw-optimization.md | 1774185819    |
-| SDK Reference         | sdk, method, parameter, signature, reference, api, script, TypeScript, generate code, automate, batch job                 | sdk-reference.md         | 1774193974    |
+| SDK Reference         | sdk, method, parameter, signature, reference, api, script, TypeScript, generate code, automate, batch job                 | sdk-reference.md         | 1774303632    |
 
 ### Workspace Templates
 
@@ -43,22 +43,55 @@ At install or upgrade, set up the workspace with these templates:
 
 Credits, limits, pipeline stats, campaign state, session recovery, and pending actions are automatically injected into your context at every session start. You do NOT need to manually fetch any of this.
 
-**First interaction (new user):**
+**Principle:** Make the user successful before mentioning payment. The onboarding ends with: a saved ICP, a campaign with first contacts, a real action taken on LinkedIn, and awareness of the upgrade path.
 
-Gather what's needed for the task at hand. Full onboarding for new users who are exploring; skip to action for users with a clear request (e.g., "just scrape this post").
+**First interaction (new user) — 3-phase flow:**
 
-Typical onboarding steps (use judgment — not all steps are always needed):
-1. **Profile + language** — `profile.get` to understand who they are. Detect language.
-2. **Recent posts** — `profile.posts({ count: 10 })` to understand topics, tone.
-3. **Website** — if available, fetch and extract positioning.
-4. **Documents** — if the user provided files (ICP docs, prospect lists), read them.
-5. **Competitors** — infer from industry and posts.
-6. **Welcome** — suggest a first action based on their profile.
+1. **Phase 1 — Know You** (automatic, no questions):
+   - The user's profile is auto-initialized. Narrate what you found (name, role, company).
+   - Use `bereach_get_own_posts` (count: 5) to understand their content and topics.
+   - Detect language from profile + posts. Respond in that language going forward.
+   - Keep it brief: 2-3 sentences summarizing who they are and what they do.
+
+2. **Phase 2 — Reveal & ICP**:
+   - Propose an Ideal Customer Profile based on their profile: job titles, industries, company size, locations, pain points.
+   - Show a "missed opportunity" insight using `bereach_get_profile_views` or engagement scraping on their latest post.
+   - Wait for user confirmation. Save via `bereach_context_set({ type: "icp", scope: "user" })`.
+   - Include link: "You can edit your ICP anytime in [Context](context-link)."
+
+3. **Phase 3 — First Quick Win**:
+   - Find 5 leads matching ICP via `bereach_search_people`. Visit top 3 with `bereach_visit_profile`.
+   - Present leads with: name, title, company, why they're a fit, suggested approach.
+   - Offer the user a choice: send a connection request, warm up with a like/comment, or save to a campaign.
+   - Execute the chosen action. Include links: "See your leads in [Pipeline](pipeline-link)." / "Track in [Campaigns](campaigns-link)."
+
+4. **Soft upgrade awareness** (free plan users only, NOT a gate):
+   - After the quick win: "You have 100 free credits. When you're ready to scale, Unlimited gives you unlimited credits and daily automation. [See plans](pricing-link). What would you like to work on next?"
+   - The conversation continues. The user is not blocked.
+
+5. Mark onboarding complete: `bereach_state_set({ key: "onboarding", data: { completed: true } })`
 
 **Returning user:**
 
 Check the Live Status (auto-injected). Surface pending actions (drafts, unread DMs) and resume from where the last session left off.
 
+## Upgrade Messaging
+
+Upgrade mentions are **contextual** — triggered by usage signals, never hard-gated during onboarding. The free plan includes 100 credits/month, enough for meaningful work.
+
+**Rules:**
+- Never block the user from working. After mentioning upgrade, always continue helping.
+- Tone: confident but not pushy. "You've seen what I can do. Unlimited unlocks the full engine."
+- Always include the pricing link from Dashboard Links when mentioning upgrade.
+- Only mention upgrade for free plan users. Paid users never see upgrade prompts.
+
+**Templates by trigger:**
+- **Credits running low** (80+ of 100 used): "You've used [X] of your 100 free credits. At this pace, you'll run out in ~[Y] days. [See plans](pricing-link)"
+- **Credits exhausted** (100/100): "You've used all 100 credits this month. You can still manage contacts, read inbox, and review drafts (0-credit tools). [Upgrade for unlimited](pricing-link)"
+- **First reply received**: "[Name] replied! Imagine 50 conversations like this per week. [Scale your outreach](pricing-link)"
+- **Weekly recap** (active user): "This week: [X] leads found, [Y] connections sent, [Z] replies. [Unlock daily automation](pricing-link)"
+- **Daily automation requested on free plan**: "Daily automation is available on the Unlimited plan. [See plans](pricing-link)"
+
 ## Installation
 
 ### Tools (interactive use)
@@ -109,6 +142,16 @@ The SDK auto-reads `BEREACH_API_KEY` from the environment. NEVER hardcode tokens
 2. **Step 2** — Run `npx tsx <script-name>.ts`. Fix runtime errors.
 3. For production scripts, both should pass. For quick one-off scripts, tsx alone is acceptable.
 
+### Dashboard Links in Responses
+
+When mentioning any of these concepts in conversation, ALWAYS include the matching clickable link from the Dashboard Links section of your live status:
+- Leads, contacts, funnel, pipeline → [Pipeline](link)
+- Campaigns → [Campaigns](link)
+- Drafts, scheduled messages → [Drafts](link)
+- ICP, tone, playbook, context → [Context](link)
+- Settings, account, LinkedIn connection → [Settings](link)
+- Upgrade, pricing, plans, credits limit → [Pricing](link)
+
 ### Always
 
 - NEVER hardcode tokens. Read from `process.env.BEREACH_API_KEY`. If not set, exit immediately.

package/skills/bereach/sdk-reference.md

@@ -1,7 +1,7 @@
 ---
 name: bereach-sdk-reference
 description: "Complete SDK v1.4.0 method reference — parameters, types, and descriptions for all BeReach operations."
-lastUpdatedAt: 1774193974
+lastUpdatedAt: 1774303632
 ---
 
 <!--
@@ -488,7 +488,7 @@ Actions are rate-limited per LinkedIn account. Limits scale with the workspace m
 
 The `retryAfter` field in every response tells you how long to wait before the next call.
 
-**Important:** `createComment` has a strict 5/day limit because commenting on others' posts is the highest-risk action for LinkedIn detection. Plan campaigns accordingly.
+**Important:** `createComment` has a strict 10/day limit because commenting on others' posts is the highest-risk action for LinkedIn detection. Plan campaigns accordingly.
 
 **Note:** The `engagement` bucket has no daily or weekly cap — only a minimum interval between calls. This keeps lightweight actions (like, save, follow) unrestricted while preventing rapid-fire API abuse.
 
@@ -624,7 +624,7 @@ Publish or schedule a LinkedIn post. Supports text, images, mentions, and visibi
 
 ### createComment
 
-Add a top-level comment on a LinkedIn post. Deduplicates by post within a campaign. Rate limited to 5/day (comment_post bucket).
+Add a top-level comment on a LinkedIn post. Deduplicates by post within a campaign. Rate limited to 10/day (comment_post bucket).
 
 `client.actions.createComment(params)`
 

package/skills/bereach/workspace/soul-template.md

@@ -1,5 +1,5 @@
 ---
-lastUpdatedAt: 1774226316
+lastUpdatedAt: 1774303632
 ---
 
 <!--
@@ -194,6 +194,7 @@ Credits, rate limits, pipeline metrics, user context (ICP, tone), and session re
 - State saves: only save pipeline progress (phase, scraped sources) to agentState. Never store profile data in state.
 - Enforcement: pacing, credit guards, rate limit guards, doNotContact checks, and visit-before-connect are handled automatically. Focus on strategy, not mechanics.
 - Context extraction: when the user provides a prompt with outreach instructions, tone, message templates, or ICP criteria, ALWAYS extract and save them as campaign-scoped context entries (playbook, tone-voice, icp). Never lose user instructions — persist them.
+- Tone-voice auto-inference: when no `tone-voice` context exists for the active account, proactively analyze the user's recent posts (5-10), sent DMs (3-5 conversations), and comments (10-20) to infer their communication style. Save the result as `tone-voice` context with `scope: "user"`. Do this silently without asking the user. If there is not enough data (new account), skip silently.
 
 ## Sub-Skills — MANDATORY Loading Table
 

package/src/commands/index.ts

@@ -1,11 +1,8 @@
-import { getClient } from "../client";
+import { apiFetch } from "../hooks/cache";
 import type { SessionState } from "../hooks/types";
 
-/**
- * Registers auto-reply commands and CLI commands.
- * Auto-reply commands execute without invoking the LLM.
- * Client is created lazily on first command invocation.
- */
+const API_KEY = process.env.BEREACH_API_KEY ?? "";
+
 export function registerCommands(api: any, state?: SessionState) {
   if (typeof api?.registerCommand !== "function") return;
 
@@ -13,16 +10,13 @@ export function registerCommands(api: any, state?: SessionState) {
     name: "bereach-credits",
     description: "Show current BeReach credit balance",
     handler: async () => {
-      const client = getClient();
-      const res = await client.profile.getCredits();
+      const res = await apiFetch<{ credits: { current: number; limit: number | null; remaining: number | null; isUnlimited: boolean; percentage: number } }>("/api/me/credits", API_KEY);
+      if (!res) return { text: "Failed to fetch credits." };
       const c = res.credits;
       return {
         text: c.isUnlimited
           ? `BeReach Credits: Unlimited (${c.current} used)`
-          : [
-              `BeReach Credits: ${c.current}/${c.limit} used (${c.percentage}%)`,
-              `Remaining: ${c.remaining}`,
-            ].join("\n"),
+          : `BeReach Credits: ${c.current}/${c.limit} used (${c.percentage}%)\nRemaining: ${c.remaining}`,
       };
     },
   });
@@ -31,33 +25,13 @@ export function registerCommands(api: any, state?: SessionState) {
     name: "bereach-status",
     description: "Show LinkedIn rate limit summary",
     handler: async () => {
-      const client = getClient();
-      const res = await client.profile.getLimits();
+      const res = await apiFetch<any>("/api/rate-limits", API_KEY);
+      if (!res) return { text: "Failed to fetch limits." };
+      const limits = res?.linkedIn?.limits ?? res?.limits ?? {};
       const lines = ["BeReach Rate Limits:"];
-      for (const [action, data] of Object.entries(res.limits) as [string, any][]) {
-        const d = data.daily;
-        lines.push(`  ${action}: ${d.current}/${d.limit} daily (${d.remaining} remaining)`);
-      }
-      return { text: lines.join("\n") };
-    },
-  });
-
-  api.registerCommand({
-    name: "bereach-limits",
-    description: "Show detailed per-action LinkedIn rate limits",
-    handler: async () => {
-      const client = getClient();
-      const res = await client.profile.getLimits();
-      const lines = [`BeReach Rate Limits (multiplier: ${res.multiplier}x):`];
-      for (const [action, data] of Object.entries(res.limits) as [string, any][]) {
+      for (const [action, data] of Object.entries(limits) as [string, any][]) {
         const d = data.daily;
-        const w = data.weekly;
-        lines.push(`\n  ${action}:`);
-        lines.push(`    Daily:  ${d.current}/${d.limit} (${d.remaining} remaining, resets ${data.nextResetDaily})`);
-        if (w) {
-          lines.push(`    Weekly: ${w.current}/${w.limit} (${w.remaining} remaining, resets ${data.nextResetWeekly})`);
-        }
-        lines.push(`    Min interval: ${data.minIntervalSeconds}s`);
+        if (d) lines.push(`  ${action}: ${d.current}/${d.limit} daily (${d.remaining} remaining)`);
       }
       return { text: lines.join("\n") };
     },
@@ -78,33 +52,10 @@ export function registerCommands(api: any, state?: SessionState) {
             lines.push(`    ${reason}: ${count}`);
           }
         }
-        if (state.engagementSignals.size > 0) {
-          lines.push(`  Engagement signals tracked: ${state.engagementSignals.size} profiles`);
-        }
       } else {
         lines.push("  No session data available yet.");
       }
       return { text: lines.join("\n") };
     },
   });
-
-  api.registerCli(
-    ({ program }: { program: any }) => {
-      program
-        .command("bereach")
-        .description("BeReach status commands")
-        .command("status")
-        .description("Show LinkedIn rate limit summary")
-        .action(async () => {
-          const client = getClient();
-          const res = await client.profile.getLimits();
-          console.log("BeReach Rate Limits:");
-          for (const [action, data] of Object.entries(res.limits) as [string, any][]) {
-            const d = data.daily;
-            console.log(`  ${action}: ${d.current}/${d.limit} daily (${d.remaining} remaining)`);
-          }
-        });
-    },
-    { commands: ["bereach"] },
-  );
 }