@sellable/install 0.1.284 → 0.1.286

package/README.md

@@ -100,6 +100,7 @@ Use the same public entrypoints in both hosts:
 - Claude Code: `/sellable:foundation`
 - Claude Code: `/sellable:content`
 - Claude Code: `/sellable:create-post`
+- Claude Code: `/sellable:refresh-sender-engagement`
 - Claude Code: `/sellable:refill-sends`
 - Codex: `$sellable:create-campaign`
 - Codex: `$sellable:create-ab-test`
@@ -107,6 +108,7 @@ Use the same public entrypoints in both hosts:
 - Codex: `$sellable:foundation`
 - Codex: `$sellable:content`
 - Codex: `$sellable:create-post`
+- Codex: `$sellable:refresh-sender-engagement`
 - Codex: `$sellable:refill-sends`
 - Codex Desktop plugin: `sellable@sellable`
 - Codex visible skill: `Sellable Create Campaign`
@@ -115,6 +117,7 @@ Use the same public entrypoints in both hosts:
 - Codex visible skill: `Sellable Foundation`
 - Codex visible skill: `Sellable Content`
 - Codex visible skill: `Sellable Create Post`
+- Codex visible skill: `Sellable Refresh Sender Engagement`
 - Codex visible skill: `Sellable Refill Sends`
 - Internal MCP workflow prompt: `create-campaign-v2`
 - Internal MCP workflow prompt: `refill-sends-workflow`

package/bin/sellable-install.mjs

@@ -190,7 +190,7 @@ Auth:
   Install is auth-free by default. Sign in happens on the first run of
   /sellable:create-campaign, /sellable:create-evergreen-campaigns,
   /sellable:foundation, /sellable:content, /sellable:create-post, or
-  /sellable:refill-sends in Claude Code or Codex,
+  /sellable:refresh-sender-engagement, or /sellable:refill-sends in Claude Code or Codex,
   where the agent walks you through signup or sign-in and stores credentials
   in ~/.sellable/config.json.
 
@@ -220,6 +220,7 @@ function printCreateCommandHint() {
     { label: "Foundation", command: "/sellable:foundation" },
     { label: "Content", command: "/sellable:content" },
     { label: "Post", command: "/sellable:create-post" },
+    { label: "Refresh", command: "/sellable:refresh-sender-engagement" },
     { label: "Refill", command: "/sellable:refill-sends" },
   ]);
   console.log("");
@@ -231,6 +232,7 @@ function printCreateCommandHint() {
     { label: "Foundation", command: "$sellable:foundation" },
     { label: "Content", command: "$sellable:content" },
     { label: "Post", command: "$sellable:create-post" },
+    { label: "Refresh", command: "$sellable:refresh-sender-engagement" },
     { label: "Refill", command: "$sellable:refill-sends" },
   ]);
   console.log("");
@@ -1094,6 +1096,29 @@ const REFILL_SENDS_ALLOWED_TOOLS = [
   "mcp__sellable__get_sender",
 ];
 
+const REFRESH_SENDER_ENGAGEMENT_ALLOWED_TOOLS = [
+  "mcp__sellable__get_auth_status",
+  "mcp__sellable__start_cli_login",
+  "mcp__sellable__wait_for_cli_login",
+  "mcp__sellable__get_active_workspace",
+  "mcp__sellable__list_workspaces",
+  "mcp__sellable__set_active_workspace",
+  "mcp__sellable__get_subskill_prompt",
+  "mcp__sellable__search_subskill_prompts",
+  "mcp__sellable__list_senders",
+  "mcp__sellable__get_sender",
+  "mcp__sellable__get_campaigns",
+  "mcp__sellable__get_campaign",
+  "mcp__sellable__get_campaign_context",
+  "mcp__sellable__get_campaign_table_schema",
+  "mcp__sellable__list_tables",
+  "mcp__sellable__get_rows_minimal",
+  "mcp__sellable__fetch_linkedin_posts",
+  "mcp__sellable__select_promising_posts",
+  "mcp__sellable__fetch_post_engagers",
+  "mcp__sellable__add_on_demand_leads",
+];
+
 function allowedToolsYaml(tools) {
   return [...new Set(tools)].map((tool) => `  - ${tool}`).join("\n");
 }
@@ -1977,6 +2002,75 @@ then retry \`get_subskill_prompt\`.
 `, host, "refill-sends");
 }
 
+function refreshSenderEngagementSkillMd(host = "shared") {
+  try {
+    const here = dirname(fileURLToPath(import.meta.url));
+    const templatePath = join(
+      here,
+      "..",
+      "skill-templates",
+      "refresh-sender-engagement.md"
+    );
+    if (existsSync(templatePath)) {
+      return stampInstalledHost(
+        addOrReplaceAllowedTools(
+          readFileSync(templatePath, "utf8"),
+          REFRESH_SENDER_ENGAGEMENT_ALLOWED_TOOLS
+        ),
+        host,
+        "refresh-sender-engagement"
+      );
+    }
+  } catch {
+    // fall through to hardcoded fallback below
+  }
+  return stampInstalledHost(`---
+name: refresh-sender-engagement
+description: Refresh sender-owned Post Engagers campaigns by finding active Signal Discovery campaigns, fetching recent sender-authored posts, and adding net-new engagers without sending.
+visibility: public
+allowed-tools:
+${allowedToolsYaml(REFRESH_SENDER_ENGAGEMENT_ALLOWED_TOOLS)}
+---
+
+# Sellable Refresh Sender Engagement
+
+Use this as the customer-facing entrypoint for the Sellable
+\`refresh-sender-engagement\` workflow. It finds active sender-owned Post
+Engagers / Signal Discovery campaigns, fetches recent sender-authored LinkedIn
+posts, pulls latest engagers, filters to ICP, and adds net-new leads with
+dedupe. It never creates messages, approves rows, schedules sends, or launches
+campaigns.
+
+## Bootstrap
+
+MCP prompt and command access are required. Do not inspect repo files, run shell
+commands, use \`npm\`, \`node\`, local harness scripts, or read local prompt
+files to emulate this workflow.
+
+If the Sellable MCP prompt tools are unavailable, stop and say this is a Codex
+install/reload problem. Tell the user to run
+\`curl -fsSL "https://app.sellable.dev/api/v2/cli/install" | sh\`, fully quit and reopen Codex
+Desktop, then start a new thread.
+
+## Execute Workflow
+
+1. Call \`mcp__sellable__get_auth_status({})\`.
+2. Load the canonical prompt via
+   \`mcp__sellable__get_subskill_prompt({ subskillName: "refresh-sender-engagement" })\`.
+   If the response has \`hasMore=true\`, continue with \`nextOffset\` until
+   \`hasMore=false\`.
+3. Follow the canonical prompt exactly. Target active/paused sender-owned Post
+   Engagers campaigns backed by Signal Discovery, and do not touch shared lanes
+   or send-state tools.
+
+## MCP Prompt Fallback
+
+If exact subskill lookup fails, use
+\`mcp__sellable__search_subskill_prompts({ query: "refresh-sender-engagement", includePublic: true, includeInternal: true })\`,
+then retry \`get_subskill_prompt\`.
+`, host, "refresh-sender-engagement");
+}
+
 function genericSellableSkillMd({ name, title, description, host = "shared" }) {
   return stampInstalledHost(`---
 name: ${name}
@@ -2450,6 +2544,12 @@ function codexPluginSkills() {
       description: "Capture ideas and draft LinkedIn posts in your voice",
       skillMd: createPostSkillMd(),
     },
+    {
+      dir: "sellable-refresh-sender-engagement",
+      displayName: "Sellable Refresh Sender Engagement",
+      description: "Refresh post-engager campaigns from recent sender posts",
+      skillMd: refreshSenderEngagementSkillMd("codex"),
+    },
     {
       dir: "sellable-refill-sends",
       displayName: "Sellable Refill Sends",
@@ -2681,6 +2781,19 @@ function claudeCommands() {
       argumentHint: "[post idea or source material]",
       skillMd: createPostSkillMd(),
     },
+    {
+      name: "refresh-sender-engagement",
+      title: "Refresh Sender Engagement",
+      filename: join("sellable", "refresh-sender-engagement.md"),
+      description:
+        "Refresh sender-owned Post Engagers campaigns from recent sender posts.",
+      argumentHint: "[--sender name-or-id ...] [lookback window]",
+      skillMd: refreshSenderEngagementSkillMd("claude"),
+      allowedTools: [
+        "AskUserQuestion",
+        ...REFRESH_SENDER_ENGAGEMENT_ALLOWED_TOOLS,
+      ],
+    },
     {
       name: "refill-sends",
       title: "Refill Sends",
@@ -3988,6 +4101,7 @@ function printNextSteps(installedHosts, authReused) {
       { label: "Foundation", command: "/sellable:foundation" },
       { label: "Content", command: "/sellable:content" },
       { label: "Post", command: "/sellable:create-post" },
+      { label: "Refresh", command: "/sellable:refresh-sender-engagement" },
       { label: "Refill", command: "/sellable:refill-sends" },
     ]);
     console.log("");
@@ -4000,6 +4114,7 @@ function printNextSteps(installedHosts, authReused) {
       { label: "Foundation", command: "$sellable:foundation" },
       { label: "Content", command: "$sellable:content" },
       { label: "Post", command: "$sellable:create-post" },
+      { label: "Refresh", command: "$sellable:refresh-sender-engagement" },
       { label: "Refill", command: "$sellable:refill-sends" },
     ]);
     console.log("");
@@ -4291,12 +4406,14 @@ async function main() {
       console.log(`    Claude Code: /sellable:foundation`);
       console.log(`    Claude Code: /sellable:content`);
       console.log(`    Claude Code: /sellable:create-post`);
+      console.log(`    Claude Code: /sellable:refresh-sender-engagement`);
       console.log(`    Claude Code: /sellable:refill-sends`);
       console.log(`    Codex: $sellable:create-campaign`);
       console.log(`    Codex: $sellable:create-evergreen-campaigns`);
       console.log(`    Codex: $sellable:foundation`);
       console.log(`    Codex: $sellable:content`);
       console.log(`    Codex: $sellable:create-post`);
+      console.log(`    Codex: $sellable:refresh-sender-engagement`);
       console.log(`    Codex: $sellable:refill-sends`);
       process.exit(0);
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.284",
+  "version": "0.1.286",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-evergreen-campaigns.md

@@ -1358,9 +1358,11 @@ Message, and verify current-revision sample messages before final completion.
      senders, the copy must be safe for every attached sender to send. Do not
      use founder-only first person such as "I'm building", "my company", "my
      team", or "I have a framework" unless every attached sender can credibly
-     say it. Prefer sender-agnostic company/team language such as "we're
-     helping CX teams..." or "at cxconnect.ai, we help..." and one clear
-     problem question.
+     say it. Prefer sender-agnostic company/team language grounded in the
+     current workspace's verified company, offer, buyer, and proof, plus one
+     clear problem question. Do not reuse unrelated fixture/example customer
+     names, domains, verticals, product categories, use cases, or proof points
+     unless the current workspace/company research independently supports them.
      Before Message Drafting runs, the campaign brief must already include
      these shared-lane hard avoids and source-use rules. Do not rely on a
      failed first generation batch to discover that self-intros, generic
@@ -1370,7 +1372,10 @@ Message, and verify current-revision sample messages before final completion.
      Shared Signal Discovery samples may use a supported topic bridge such as
      "saw you around conversations about [high-level topic], so hope this is
      relevant" when the topic is grounded in source evidence and not
-     activity-log phrasing. Translate source/tool terms into prospect-facing
+     activity-log phrasing. Signal Discovery is only a lead-source provider;
+     do not infer a product category, buyer pain, offer, asset, CTA, or
+     provider-themed message direction from the lane/provider name.
+     Translate source/tool terms into prospect-facing
      business language; do not put internal workflow vocabulary such as
      "Codex-style workflow", "MCP", "agent workflows",
      "Claude Code", or "Claude-style agent workflows" in customer-facing
@@ -1535,7 +1540,10 @@ Message, and verify current-revision sample messages before final completion.
       `issues`.
       Shared Signal Discovery samples may use `"saw you around conversations
       about [high-level topic], so hope this is relevant"` when the topic is
-      supported by source evidence and not activity-log phrasing. Shared Cold
+      supported by source evidence and not activity-log phrasing. Signal
+      Discovery is only a lead-source provider; reject provider-themed campaign
+      copy unless that language is independently supported by the current
+      workspace/company research. Shared Cold
       Fallback samples must still reject source/conversation hedges such as
       `"hope this is relevant"`, `"might be interested"`, or `"saw you in a few
       conversations"`.

package/skill-templates/refresh-sender-engagement.md

@@ -0,0 +1,98 @@
+---
+name: refresh-sender-engagement
+description: Top up a sender's post-engager pipeline — fetch their recent LinkedIn posts, pull new engagers, filter by headline ICP criteria, and add net-new leads to their post-engagers campaign with dedupe. Schedule-automation friendly ("refresh sender engagement for these people"). Read-only on LinkedIn; never sends.
+visibility: public
+allowed-tools:
+  - mcp__sellable__get_auth_status
+  - mcp__sellable__start_cli_login
+  - mcp__sellable__wait_for_cli_login
+  - mcp__sellable__get_active_workspace
+  - mcp__sellable__list_workspaces
+  - mcp__sellable__set_active_workspace
+  - mcp__sellable__get_subskill_prompt
+  - mcp__sellable__search_subskill_prompts
+  - mcp__sellable__list_senders
+  - mcp__sellable__get_sender
+  - mcp__sellable__get_campaigns
+  - mcp__sellable__get_campaign
+  - mcp__sellable__get_campaign_context
+  - mcp__sellable__get_campaign_table_schema
+  - mcp__sellable__list_tables
+  - mcp__sellable__get_rows_minimal
+  - mcp__sellable__fetch_linkedin_posts
+  - mcp__sellable__select_promising_posts
+  - mcp__sellable__fetch_post_engagers
+  - mcp__sellable__add_on_demand_leads
+---
+
+# Refresh Sender Engagement
+
+<role>
+You are a pipeline supply agent. People who engage with a sender's LinkedIn posts are their warmest prospects; your job is to capture them into the sender's post-engagers campaign before they go cold — with zero duplicates and zero sends.
+</role>
+
+<inputs>
+The invoking prompt names the senders ("refresh sender engagement for csreyes92 and thomas"). Resolve each via `list_senders` (match name/handle/LinkedIn URL). With no names given, inspect the active workspace and refresh every connected sender that has an active/paused sender-owned Post Engagers campaign backed by Signal Discovery.
+
+Optional: lookback window (default: posts from the last 30 days), engagement sources (default `both` reactions+comments), target sender names/ids, maximum posts per sender (default 5, hard cap 5 unless the user explicitly asks for more), and target campaign ids/names when the user wants to force a specific campaign.
+</inputs>
+
+<entrypoint>
+This is a public Sellable command:
+
+- Claude Code: `/sellable:refresh-sender-engagement`
+- Codex: `$sellable:refresh-sender-engagement`
+
+Use this command when the user asks to refresh recent engagers, top up tracked
+campaign post engagers, pull latest engagers from sender posts, or refill warm
+post-engager source rows. It is not a send-refill command; if the user asks to
+prepare/schedule sends after adding rows, finish this refresh first and then
+suggest `refill-sends`.
+</entrypoint>
+
+<objective>
+For each target sender/campaign:
+
+1. **Find active Signal Discovery/Post Engagers campaigns first**:
+   - Call `get_auth_status` and confirm the active workspace.
+   - Call `get_campaigns` and, when needed, `list_tables`/`get_campaign` to find candidate campaigns.
+   - Keep only active or paused campaign-backed sender-owned Post Engagers campaigns. Strong signals include campaign/table names like `<Sender> - Post Engagers`, `sourceProvider:"signal-discovery"`, sender attachment to exactly one sender, and source/list/table readback indicating post engagers.
+   - Exclude shared Signal Discovery lanes, Shared Cold Fallback lanes, archived/completed campaigns, non-campaign tables, direct/on-demand-only campaigns, and any campaign attached to multiple senders unless the user explicitly selected it and the readback proves it is sender-owned.
+   - If no matching campaign exists for a sender, report "no active Post Engagers Signal Discovery campaign — create one first" and skip; do not silently create campaigns.
+2. **Resolve the sender and source boundary**:
+   - Match each candidate campaign to its sender from `list_senders`/`get_sender`.
+   - Use the sender's own LinkedIn profile URL/handle as the only source author boundary.
+   - Never scrape third-party authors into a sender-owned Post Engagers campaign.
+3. **Find relevant sender-authored posts to refresh**:
+   - Call `fetch_linkedin_posts({ linkedinUrl: sender profile, limit: 25 })`.
+   - Keep original posts authored by that exact sender, not reposts, from the lookback window.
+   - Rank posts by recency, engagement count, and fit to the campaign's buyer/problem/topic. Prefer posts likely to attract the target buyer over generic company updates.
+   - If the campaign has an existing Signal Discovery/source state that names tracked/selected posts, prefer refreshing those posts when they are still inside the lookback window and relevant; otherwise choose the strongest recent sender-authored posts.
+   - When the product flow expects selected posts to be visible, call `select_promising_posts` before scraping.
+4. **Pull latest engagers**:
+   - For the top posts (up to 5 per sender per run), call `fetch_post_engagers({ postUrl, sources })`.
+   - Default `sources` to `"both"` unless the user requested reactions-only or comments-only.
+5. **Filter to ICP** using the campaign's existing headline ICP criteria (from `get_campaign` brief/rubrics/table schema). Judge each engager's headline against those criteria; exclude obvious non-fits, the sender's own colleagues, existing employees, students/job-seekers, competitors, and anyone with no usable headline. When the campaign has no criteria, keep likely decision-makers/operators and exclude weak-fit profiles.
+6. **Add net-new leads only**:
+   - Use `add_on_demand_leads({ tableId, leads, skipDuplicates: true })` with name, headline-derived title, profile URL, and source/post context where the tool accepts it.
+   - Dedupe is mandatory. Never disable dedupe on a scheduled run.
+   - Do not generate, approve, schedule, or send messages.
+7. **Report**: campaigns inspected, target campaigns selected, posts scanned, engagers found, ICP-passing, net-new added per sender/campaign. If a sender posted nothing in the window, say "no recent posts — nothing to refresh" (that is a truthful no-op, not a failure).
+</objective>
+
+<safety>
+- LinkedIn operations here are read-only fetches plus adding rows to a campaign table. **No messages are generated, approved, or sent by this skill.**
+- Respect workspace boundaries: only add leads to campaigns in the active workspace, and only for senders that belong to it.
+- Respect campaign boundaries: only add engagers to the matched sender-owned Post Engagers campaign/table. Do not mix shared-lane engagers into sender-owned campaigns or sender-owned engagers into shared lanes.
+- Cap provider usage per run: at most 5 posts × `fetch_post_engagers` per sender. If the invoking automation wants more, it must say so explicitly.
+- Never call `start_campaign`, `attach_sequence`, `queue_campaign_cells`, `start_campaign_message_preparation`, approval tools, or any send/schedule tool.
+</safety>
+
+<output>
+```
+Sender Engagement Refresh — {date}
+• csreyes92: 3 recent posts → 142 engagers → 38 ICP-fit → 15 net-new added to "Christian Reyes - Post Engagers"
+• thomas: no posts in last 30 days — nothing to refresh (consider /engage or /create-post to restart supply)
+Follow with fill-send-horizon to prepare messages for the new leads.
+```
+</output>