@sellable/mcp 0.1.410 → 0.1.412

package/skills/generate-messages/SKILL.md

@@ -228,12 +228,16 @@ must choose a signal-led, event-led, job-post-led, or proof-led motion from the
 current brief and row evidence instead of inheriting a preset first-message
 template.
 Post-engager first messages should thank the prospect for the support on the
-sender-owned post before asking the light relevance question. Prefer the gold
-shape `Thanks for the support on my post about {{post_topic_line}}` over
+sender-owned post and then stop. Do not add a relevance question, CTA, product
+line, meeting ask, or extra paragraph after the thank-you opener unless the
+operator explicitly asks for a longer first message. Prefer the gold shape
+`Thanks for the support on my post about {{post_topic_line}}` over
 surveillance-flavored wording like `saw you pop up`, unless the sender explicitly
 asks for that older wording.
 Short form: use the CXConnect Post-Engager Warm Reply-Rate Pattern only when the source is sender-owned Post Engagers.
 Short form: Never use that warm post-engager pattern for Shared Signal Discovery or Shared Cold Fallback.
+Short form: Post-engager warm first messages stop after the thank-you line.
+Short form: Do not add `curious`, `open to`, `trying to`, product copy, or a CTA after the post-engager thank-you line.
 
 ### Shared Cold Fallback quality bar
 
@@ -245,6 +249,12 @@ must read like final create-campaign/generate-messages output.
 - Ask one clear buyer problem question.
 - Keep the product line minimal and buyer-readable; do not turn the note into a
   product-stack dump.
+- Do not describe Sellable as a process checklist such as "campaign idea into
+  prospects, filters, messages, and sequence setup"; that reads like internal
+  product plumbing, not a buyer reason to reply.
+- Do not use awkward product-process nouns in reviewed cold samples:
+  `sequence-prospects`, `dashboard overhead`, `campaign map`, `send-ready copy`,
+  `reviewed prospect lists`, or "one campaign would look like" as a default CTA.
 - Use no self-intro such as "We're building" or "We're working on a way" in the
   reviewed samples.
 - Use no opt-out shrug such as "If this isn't relevant, ignore me."
@@ -252,6 +262,39 @@ must read like final create-campaign/generate-messages output.
   samples. If two samples would still read the same after replacing names and
   companies, revise or rerun.
 
+### Shared Evergreen Signal Discovery hard gate
+
+For Shared Signal Discovery and other shared evergreen lanes, signal-led copy
+must be safer than the legacy weak-signal examples. These lanes are reused by
+multiple senders, so the first line cannot sound like a scraped-activity excuse
+or a founder self-intro.
+
+- `hope this is relevant`, `might be interested`, and `saw you in a few conversations` are blocked openers for shared evergreen lanes.
+- do not write first-person singular founder language such as `I'm building`,
+  `I've mapped`, `my company`, or `my team` unless exactly one sender can
+  credibly say it and the lane is not shared.
+- Do not put internal workflow vocabulary in buyer-facing copy: `Codex`, `MCP`,
+  `Claude-style agent workflows`, `agent workflows`, `workflow table`, `lead
+  source`, or `signal discovery`.
+- Do not use `Claude`, `Codex`, `MCP`, `agent`, `dashboard`, `workflow`,
+  `source`, `sequence`, `send-ready copy`, or `reviewed prospect list` as
+  buyer-facing explanation in shared evergreen samples unless the buyer's own
+  company/product category uses that exact word and the line still sounds human.
+- Write a concrete signal/problem bridge instead of a relevance hedge. Good
+  shapes are `the AI-assisted GTM conversations keep coming back to [buyer
+  problem]`, `teams trying to turn LinkedIn signal into pipeline usually hit
+  [problem]`, or `when [observable business moment] is live, [buyer workflow]
+  gets harder to run consistently`.
+- If the row evidence is too weak to write a concrete bridge, omit the source
+  line and start from a buyer problem, event, role, or company observation.
+- Shared evergreen lanes must pass this gate before `confirmed`, before saving a
+  reusable template, and before any route-proof approval.
+
+Short form: shared evergreen copy cannot use `hope this is relevant`.
+Short form: shared evergreen copy cannot use `might be interested`.
+Short form: shared evergreen copy cannot use `I'm building`.
+Short form: write a concrete signal/problem bridge instead of a relevance hedge.
+
 ### Rich Personalization Contract
 
 The `create-campaign` asset `references/ai-native-tokens.md` is the canonical
@@ -269,12 +312,15 @@ conditional good/bad fill reference.
 - Use this shape for any hook, bridge, or row-specific relevance line:
   `[PERSONALIZATION_LINE — Intent: write one short sentence that anchors the
 note to why this might matter now. DO: connect one observable role/company/
-activity signal to the buyer problem or offer with low-certainty language like
-"hope this is relevant if...", "saw you might be interested in...", "saw you in
-a few conversations around...", or "figured this might matter if...". DON'T: recap
-their resume, list companies, compliment their background, name a product their
-company sells, use source-citation phrasing, or use generic nouns like "your
-work".
+activity signal to the buyer problem or offer with a permissioned bridge. For
+shared evergreen lanes, do not use `hope this is relevant`, `might be
+interested`, or `saw you in a few conversations`; use a concrete
+signal/problem bridge instead. For non-evergreen weak-signal campaigns only,
+legacy low-certainty language like "hope this is relevant if..." or "so may be
+off, but this seemed relevant" can be considered when the source is otherwise
+awkward. DON'T: recap their resume, list companies, compliment their
+background, name a product their company sells, use source-citation phrasing, or
+use generic nouns like "your work".
 FALLBACK: if unsupported, omit the entire line.]`
 - The rendered personalization line should usually be 6-14 words. If it needs
   two clauses, multiple companies, or abstract tags like `GTM`, `international
@@ -433,9 +479,9 @@ artifact.**
 
    Safer shapes:
 
-   - `hope this is relevant if {{signal_topic}} is part of the plan`
-   - `saw you might be interested in {{signal_topic}}, so hope this is relevant`
-   - `saw you in a few conversations around {{signal_topic}}, so hope this is relevant`
+   - `hope this is relevant if {{signal_topic}} is part of the plan` for non-evergreen weak-signal campaigns only
+   - `saw you might be interested in {{signal_topic}}, so hope this is relevant` for non-evergreen weak-signal campaigns only
+   - `saw you in a few conversations around {{signal_topic}}, so hope this is relevant` for non-evergreen weak-signal campaigns only
    - `saw you in a few conversations about {{signal_topic}}, so may be off, but this seemed relevant`
    - `appreciate you showing some love on my post about {{signal_topic}}` only when the sender/client authored the source post and the row proves a reaction or comment
    - `thanks for showing support on my {{signal_topic}} post` only when the sender/client authored the source post and the row proves a reaction or comment
@@ -499,20 +545,22 @@ artifact.**
    magnet replies, or scraped conversations), it is acceptable to reference the
    conversation when it explains why the note exists. Keep it topic-level, not
    activity-log-level: `saw you in a few conversations around
-   {{signal_topic}}, so hope this is relevant` is acceptable; `saw you
-   commented on {{post_context}}` and `your LinkedIn activity around...` are
-   not. Reserve `raise your hand` phrasing for explicit lead-magnet comments,
-   replies, or opt-ins. For ordinary thread discovery, use `saw you in a few
-   conversations around {{signal_topic}}...` or `found you in a thread about
-   {{signal_topic}}...`.
+   {{signal_topic}}, so hope this is relevant` is acceptable only for
+   non-evergreen weak-signal campaigns; it is blocked for Shared Evergreen
+   Signal Discovery. `saw you commented on {{post_context}}` and `your LinkedIn
+   activity around...` are not acceptable. Reserve `raise your hand` phrasing
+   for explicit lead-magnet comments, replies, or opt-ins. For ordinary shared
+   evergreen thread discovery, either translate the topic into a concrete
+   buyer/problem bridge or omit the source line.
 
    Keep the apologetic nature, but aim it at uncertainty, not surveillance.
-   Good: `saw you in a few conversations about outbound, so may be off, but
-   this seemed relevant`, `may be off, but if outbound is relevant to what
-   you're working on...`, `if this is not relevant to your outbound workflow,
-   ignore me`, `hope
-   this is relevant if...`. Bad: `your role at {{company}} looked close...`,
-   because it asserts fit from a title and tells the buyer about themselves.
+   Good for non-evergreen weak-signal campaigns: `saw you in a few
+   conversations about outbound, so may be off, but this seemed relevant`, `may
+   be off, but if outbound is relevant to what you're working on...`, or `hope
+   this is relevant if...`. For shared evergreen lanes, these hedges are not
+   enough; use a concrete signal/problem bridge or omit the source line. Bad:
+   `your role at {{company}} looked close...`, because it asserts fit from a
+   title and tells the buyer about themselves.
 
    Block wordier source narration such as `you might not remember the thread,
    but I found you through a {{signal_topic}} discussion and your
@@ -1509,7 +1557,10 @@ Before `confirmed`, run the selected winner against these gates:
   the lead sample. If desire is inferred, use tentative framing like
   `hope this is relevant if...`, `saw you might be interested in...`,
   `saw you in a few conversations around...`, `figured this might matter if...`,
-  or `if you've ever wanted...`.
+  or `if you've ever wanted...`. Exception: for Shared Signal Discovery and
+  other shared evergreen lanes, `hope this is relevant`, `might be interested`,
+  and `saw you in a few conversations` are blocked; use a concrete
+  signal/problem bridge or omit the source line.
 - **Buyer-first opener:** after the greeting, the first substantive line
   should usually enter the buyer's world: a real signal, current-state
   pain, buyer-owned priority, or useful artifact. Sender-origin can come
@@ -1810,8 +1861,11 @@ about`, or `clearly relevant` are BLOCKED. Source-y phrases such as
   `saw you might be interested in [topic], so hope this is relevant`, `saw you
   in a few conversations around [topic], so hope this is relevant`, `found you
   in a few conversations about [topic], so may be off, but this seemed
-  relevant`, `figured this might matter if [workflow] is live at [company]`, or a similarly natural
-  line. Longer source-recap forms such as `you might not remember the thread,
+  relevant`, `figured this might matter if [workflow] is live at [company]`, or
+  a similarly natural line. For shared evergreen lanes, skip the `hope this is
+  relevant` / `might be interested` / `saw you in a few conversations` versions
+  and use the concrete bridge version. Longer source-recap forms such as `you
+  might not remember the thread,
   but I found you through a [topic] discussion...` are BLOCKED; they narrate
   the scrape path instead of creating buyer relevance.
 - **Engagement reference is opt-in, not the default opener:** do not
@@ -1956,9 +2010,9 @@ matters to the buyer, why this might be relevant, or the operator-reality that
 led to it. Acceptable openers:
 
 - `Hey {{first_name}}, [one plain sentence about what we built].`
-- `Hey {{first_name}}, hope this is relevant if [buyer context] is still on your plate.`
-- `Hey {{first_name}}, saw you might be interested in [topic], so hope this is relevant.`
-- `Hey {{first_name}}, saw you in a few conversations around [topic], so hope this is relevant.`
+- `Hey {{first_name}}, hope this is relevant if [buyer context] is still on your plate.` Not for shared evergreen lanes.
+- `Hey {{first_name}}, saw you might be interested in [topic], so hope this is relevant.` Not for shared evergreen lanes.
+- `Hey {{first_name}}, saw you in a few conversations around [topic], so hope this is relevant.` Not for shared evergreen lanes.
 - `Hey {{first_name}}, found you in a thread about [topic], so may be off, but this seemed relevant.`
 - `Hey {{first_name}}, saw you raise your hand for [topic], so figured this was (hopefully) worth sending.` Only use this for explicit lead-magnet comments, replies, or opt-ins.
 - `Hey {{first_name}}, saw you raise your hand for [topic] (creepy to reach out based on that, i know) - but this felt too on the nose to ignore.` Only use this for explicit lead-magnet comments, replies, or opt-ins.
@@ -2219,9 +2273,9 @@ Rules:
 - if `lead-sample.json` carries **any** per-lead signal for this lead — a recent post, a recent hire, a visible tool in the headline, a topic engagement, a public initiative — the **message must reference it specifically**. Category-level copy is rejected.
 - default placement is **Block 3**, not Block 1. Keep Block 1 substance-first unless the archived motion clearly earns a signal-led opener without falling into source-citation / talk-at phrasing.
 - acceptable signal use by default:
-  - `"Hope this is relevant if [topic] is part of the plan."`
-  - `"Saw you might be interested in [topic], so hope this is relevant."`
-  - `"Saw you in a few conversations around [topic], so hope this is relevant."`
+  - `"Hope this is relevant if [topic] is part of the plan."` Non-evergreen weak-signal only; blocked for shared evergreen lanes.
+  - `"Saw you might be interested in [topic], so hope this is relevant."` Non-evergreen weak-signal only; blocked for shared evergreen lanes.
+  - `"Saw you in a few conversations around [topic], so hope this is relevant."` Non-evergreen weak-signal only; blocked for shared evergreen lanes.
   - `"Saw you in a few conversations about [topic], so may be off, but this seemed relevant."`
   - `"Found you in a thread about [topic], so may be off, but this seemed relevant."`
   - `"Thought of {{company}} because [observable signal] points at [problem]."`
@@ -2239,6 +2293,11 @@ Rules:
   - `"Saw you raise your hand for [topic], so figured this was worth sending."`
   - `"Figured this was worth sending."`
 - signal-led opener shape is a **special case**, not the default. Use it only when the archived motion truly depends on it and the line can stay natural. For LinkedIn-post-sourced campaigns, prefer `"saw you in a few conversations around [topic], so hope this is relevant"` or `"found you in a thread about [topic], so may be off, but this seemed relevant"` when referencing the source makes the outreach feel less random. Avoid activity-log phrasing such as `"you commented on..."`, `"you reacted to..."`, or `"your LinkedIn activity..."` unless the approved motion is the deliberately self-aware raise-hand line for an explicit lead-magnet comment, reply, or opt-in.
+- For Shared Evergreen Signal Discovery, do not use the weak signal-led opener
+  shapes above. Translate the source into a concrete problem bridge, e.g.
+  `"The AI-assisted GTM conversations keep coming back to one problem: turning
+  good LinkedIn signal into review-ready pipeline without another dashboard."`
+  Then connect the product in buyer language.
 - tokenized engagement-source opener shape is BLOCKED by default:
   `{{first_name}}, saw you {{engagement_context}} on {{post_context}}` reads
   like surveillance unless the filled line is explicitly self-aware and
@@ -2247,7 +2306,9 @@ Rules:
 this is relevant`, `saw you in a few conversations around [topic], so hope this
 is relevant`, `saw you in a few conversations about [topic], so may be off,
 but this seemed relevant`, or `found you in a thread about [topic], so may be
-off, but this seemed relevant`. Use the self-aware raise-hand shapes only when
+off, but this seemed relevant`. For shared evergreen lanes, those weak signal
+bridges are blocked; use a concrete signal/problem bridge instead. Use the
+self-aware raise-hand shapes only when
 the source was an explicit lead-magnet comment, reply, or opt-in: `saw you raise
 your hand for [topic], so figured this was (hopefully) worth sending` or `saw you
 raise your hand for [topic] (creepy to reach out based on that, i know) - but

package/skills/refill-sends/SKILL.md

@@ -3,18 +3,8 @@ name: refill-sends
 description: Plan regular campaign and evergreen campaign send refill work through the skill-led refill workflow.
 visibility: public
 allowed-tools:
-  - mcp__sellable__refill_sends
-  - 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_routing
-  - mcp__sellable__get_campaign_waterfall
   - mcp__sellable__resolve_campaign_fill_route
   - mcp__sellable__get_campaign_refill_state
   - mcp__sellable__fill_campaign_horizon
@@ -45,50 +35,14 @@ allowed-tools:
   - mcp__sellable__get_table_rows
   - mcp__sellable__get_campaign_table_schema
   - mcp__sellable__select_campaign_cells
-  - mcp__sellable__queue_campaign_cells
   - mcp__sellable__wait_for_campaign_processing
   - mcp__sellable__get_sender
 ---
 
 # Refill Sends
 
-Use this public command wrapper for plain operator requests such as "fill",
-"refill sends", "max out sends", "load everyone up", or "fill horizon sends".
-
-Host command names:
-
-- Claude Code: `/sellable:refill-sends`
-- Codex: `$sellable:refill-sends`
-
-Accepted invocation flags in the same user request:
-
-- `--yolo`: auto-accept the rendered bounded refill packet after the required
-  fresh state reread.
-- `--sender <name-or-id>`: scope to a specific sender; repeat for multiple
-  senders.
-- `senderIds: <id>, <id>` or `senderNames: <name>, <name>`: explicit selector
-  alternatives when the host preserves natural-language arguments better than
-  shell-style flags.
-
-When the host can call typed MCP tools, start with:
-
-```text
-refill_sends({ yolo?: boolean, senders?: string[], senderIds?: string[], senderNames?: string[], horizonSendDays?: number })
-```
-
-That command helper only normalizes arguments and returns the execution
-contract. It does not mutate. Continue with the workflow below for route
-selection, state rereads, approval gating, source import, preparation, and
-bounded approval.
-
-First call `get_auth_status({})`. If auth or active workspace is not OK, follow
-the returned login/workspace guidance before route resolution. Do not run refill
-research against an implicit or guessed workspace.
-
-Treat "refill senders", "fill senders", "load everyone up", and "max out
-senders" as sender-scoped requests. The target set is senders enrolled in active
-campaign-backed sequence campaigns, not the first active campaign returned by a
-resolver.
+Use this public wrapper for plain operator requests such as "fill", "refill sends",
+"max out sends", "load everyone up", or "fill horizon sends".
 
 Load the internal workflow prompt before taking any operational step:
 
@@ -97,52 +51,10 @@ get_subskill_prompt({ subskillName: "refill-sends-workflow" })
 ```
 
 Then follow that workflow exactly. The default path is read-only research:
-resolve the route, identify the sender-relevant campaign that most recently had
-scheduler-owned sends, read refill state for that target, report the next safe
-step using campaign names first, and stop before mutation unless the user has
-explicitly approved the exact workspace, campaign/table/source ids, caps/dates,
-approval mode, expected side effects, and stop/rollback condition.
-
-For interactive Codex or Claude Code sessions, that approval must use the
-host-native structured question gate, not plain chat:
-
-- Codex: use `request_user_input`.
-- Claude Code: use `AskUserQuestion`.
-
-The approval question must present the final refill step with exactly two
-choices: `Accept` and `Decline`. The question body must include the operator
-output packet: workspace, sender scope, a campaign-by-campaign table with
-campaign name, sender names, action, target count/cap, source/list, and
-blocker/skip reason, then exact ids, expected side effects, forbidden actions,
-and the stop condition. Treat `Accept` as permission for only the rendered
-target, caps, mode, and side effects. Treat `Decline` as a hard stop with no
-mutation.
-
-If Christian includes `--yolo` in the same refill request, treat that flag as
-auto-accept for the rendered bounded refill packet after the required fresh state
-reread. For sender-scoped language with no named senders, `--yolo` means all
-eligible healthy senders enrolled in active campaign-backed sequence campaigns in
-the active workspace. Without `--yolo`, if Christian did not name senders, ask
-which eligible enrolled senders to refill before choosing campaigns or mutating.
-
-`--yolo` only covers the exact sender set, per-sender target campaigns, caps,
-approval mode, and side effects in the packet. It does not authorize
-launch/start, sending, archive or delete cleanup, direct scheduler writes, sender
-reassignment, or campaigns outside those selected for the eligible sender set.
-Stop and re-plan if the route, sender set, ids, caps, blockers, or side-effect
-class drift before mutation.
-
-In `--yolo`, the default two-day fill horizon is two send days. For each target
-sender, compute the bounded gap from that sender's healthy daily capacity,
-existing future scheduler-owned scheduled sends, and rows already ready to
-schedule across active campaigns enrolled with that sender. Then pick the best
-same-sender campaign to fill the gap: prefer recent/future scheduler-owned sends
-for that sender, then strongest recent result evidence, then source health. Do
-not stop after filling only one sender when the request was sender-scoped. If a
-same-source copy hits the campaign-table row cap, split the current source into
-a bounded LinkedIn profile source list, confirm only that smaller list into the
-same campaign, and operate on the copied review batch. Do not fall back to
-on-demand campaigns or unrelated active-campaign fills.
+resolve the route, read target refill state, report the next safe step, and stop
+before mutation unless the user has explicitly approved the exact workspace,
+campaign/table/source ids, caps/dates, approval mode, expected side effects,
+and stop/rollback condition.
 
 Public concepts are regular campaign and evergreen campaign. Internal direct
 campaign types are unsupported refill targets. `fill_campaign_horizon` is only a