@sellable/mcp 0.1.446 → 0.1.447

package/README.md

@@ -16,7 +16,7 @@ Each message gets 5+ minutes of Claude attention with deep research - no other t
 
 ### Prompt Source Of Truth
 
-There are seven public Sellable entrypoints shared across hosts:
+There are eight public Sellable entrypoints shared across hosts:
 
 - `sellable:create-campaign`
 - `sellable:create-ab-test`
@@ -24,6 +24,7 @@ There are seven public Sellable entrypoints shared across hosts:
 - `sellable:foundation`
 - `sellable:content`
 - `sellable:create-post`
+- `sellable:refresh-sender-engagement`
 - `sellable:refill-sends`
 
 The create-campaign public wrapper at
@@ -64,6 +65,13 @@ reader value, validates proof/AI tells, and saves content artifacts under
 
 - `mcp/sellable/skills/create-post/SKILL.md`
 
+The refresh-sender-engagement public command wrapper finds active sender-owned
+Post Engagers / Signal Discovery campaigns, refreshes recent sender-authored
+posts, pulls latest engagers, filters to ICP, and adds net-new leads without
+sending from:
+
+- `mcp/sellable/skills/refresh-sender-engagement/SKILL.md`
+
 The refill-sends public command wrapper plans and executes approval-gated send
 refills. It supports `--yolo` and optional sender selectors such as
 `--sender "Christian Reyes"`, optional through-date selectors such as
@@ -195,10 +203,12 @@ The installer does the full local setup:
 After the installer passes, fully quit and reopen Codex Desktop. Start a new
 thread and select `Sellable Create Campaign`, `Sellable Create A/B Test`,
 `Sellable Create Evergreen Campaigns`, `Sellable Foundation`,
-`Sellable Content`, `Sellable Create Post`, or `Sellable Refill Sends`; or invoke
+`Sellable Content`, `Sellable Create Post`, `Sellable Refresh Sender Engagement`,
+or `Sellable Refill Sends`; or invoke
 `$sellable:create-campaign`, `$sellable:create-ab-test`,
 `$sellable:create-evergreen-campaigns`, `$sellable:foundation`,
-`$sellable:content`, `$sellable:create-post`, or `$sellable:refill-sends`. If the app still says
+`$sellable:content`, `$sellable:create-post`,
+`$sellable:refresh-sender-engagement`, or `$sellable:refill-sends`. If the app still says
 `mcp__sellable__*` tools are missing after the installer passes, check that
 `~/.codex/config.toml` contains both `[marketplaces.sellable]` and
 `[plugins."sellable@sellable"]`.
@@ -215,6 +225,7 @@ Use these names consistently:
 - Claude Code command: `/sellable:foundation`
 - Claude Code command: `/sellable:content`
 - Claude Code command: `/sellable:create-post`
+- Claude Code command: `/sellable:refresh-sender-engagement`
 - Claude Code command: `/sellable:refill-sends`
 - Codex command: `$sellable:create-campaign`
 - Codex command: `$sellable:create-ab-test`
@@ -222,6 +233,7 @@ Use these names consistently:
 - Codex command: `$sellable:foundation`
 - Codex command: `$sellable:content`
 - Codex command: `$sellable:create-post`
+- Codex command: `$sellable:refresh-sender-engagement`
 - Codex command: `$sellable:refill-sends`
 - Codex Desktop plugin: `sellable@sellable`
 - Codex visible skill: `Sellable Create Campaign`
@@ -230,6 +242,7 @@ Use these names consistently:
 - 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`
 - Codex skill frontmatter name: `create-campaign`
 - Codex skill frontmatter name: `create-ab-test`
@@ -237,6 +250,7 @@ Use these names consistently:
 - Codex skill frontmatter name: `foundation`
 - Codex skill frontmatter name: `content`
 - Codex skill frontmatter name: `create-post`
+- Codex skill frontmatter name: `refresh-sender-engagement`
 - Codex skill frontmatter name: `refill-sends`
 - MCP server name: `sellable`
 - Internal workflow prompt: `create-campaign-v2`
@@ -301,6 +315,13 @@ Use the refill command for sender send refills:
 /sellable:refill-sends --sender "Christian Reyes" --sender "Thomas Nobbs"
 ```
 
+Use the refresh command to top up sender-owned post-engager campaigns from the
+latest relevant sender-authored posts:
+
+```
+/sellable:refresh-sender-engagement --sender "Christian Reyes"
+```
+
 Then describe intent naturally, for example:
 
 - "Let's make a campaign with sellable"
@@ -329,6 +350,12 @@ $sellable:refill-sends --yolo --until 2026-06-30
 $sellable:refill-sends --sender "Christian Reyes" --sender "Thomas Nobbs"
 ```
 
+Use the Codex refresh command for latest post engagers:
+
+```
+$sellable:refresh-sender-engagement --sender "Christian Reyes"
+```
+
 Installed skill package path:
 
 - `~/.codex/plugins/cache/sellable/sellable/<version>/skills/sellable-create-campaign/SKILL.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.446",
+  "version": "0.1.447",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/refresh-sender-engagement/SKILL.md

@@ -1,7 +1,28 @@
 ---
 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: internal
+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
@@ -11,27 +32,60 @@ You are a pipeline supply agent. People who engage with a sender's LinkedIn post
 </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, refresh every connected sender in the active workspace.
+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), and the target campaign name (default: the sender's existing "<Name> - Post Engagers" campaign found via `get_campaigns`/`list_tables`).
+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 sender:
-
-1. **Find the target campaign**: locate the sender's post-engagers campaign table (`get_campaigns` + `get_campaign`, or `list_tables`). If none exists, report "no post-engagers campaign — create one first" and skip; do not silently create campaigns on a schedule.
-2. **Fetch recent posts**: `fetch_linkedin_posts({ linkedinUrl: sender profile, limit: 25 })`. Keep original posts (not reposts) from the lookback window, ranked by engagement.
-3. **Pull engagers**: for the top posts (up to 5 per sender per run), `fetch_post_engagers({ postUrl, sources: "both" })`.
-4. **Filter to ICP** using the campaign's existing headline ICP criteria (from `get_campaign` brief/rubrics). Judge each engager's headline against those criteria; exclude obvious non-fits, the sender's own colleagues, and anyone with no headline. When the campaign has no criteria, keep decision-makers and operators, exclude students/job-seekers/competitors.
-5. **Add net-new leads only**: `add_on_demand_leads({ tableId, leads, skipDuplicates: true })` with name, headline-derived title, and profile URL. Dedupe is the default — never disable it on a scheduled run.
-6. **Report**: posts scanned, engagers found, ICP-passing, net-new added per sender. If a sender posted nothing in the window, say "no recent posts — nothing to refresh" (that is a truthful no-op, not a failure).
+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` or any send/approve tool.
+- Never call `start_campaign`, `attach_sequence`, `queue_campaign_cells`, `start_campaign_message_preparation`, approval tools, or any send/schedule tool.
 </safety>
 
 <output>