@sellable/install 0.1.131 → 0.1.133

package/bin/sellable-install.mjs

@@ -699,28 +699,46 @@ signals, cleanup risk, and confidence basis. If a user asks for a forecast,
 label it explicitly as not estimated from this run.
 
 Before any provider prompt, search, source scout, or signal-discovery call, show
-one source-plan gate and ask for approval. The plan must be visible before the
-question, and this first approval only authorizes finding the best places to
-look for buyers. It does not add anyone to the campaign yet. The gate should
-say:
-
-- given this campaign, the viable source options
-- the recommended first lane
-- why that lane fits the buyer, offer, and likely public activity
-- what will be tested next
-- the fallback lane if relevant posts or ICP engagement look thin
+one source-plan gate and ask for approval. Write this like a fifth grader could
+understand it: short sentences, no internal labels, and no GTM shorthand. The
+plan must be visible before the question, and this first approval only
+authorizes finding the best places to look for buyers. It does not add anyone
+to the campaign yet. The gate should say:
+
+- the buyer groups or places we could check
+- the best place to start
+- why the right buyers are likely to be there
+- what signs the next search will check
+- where you'll look next if the first place is too thin
 - what approval covers in one concise customer-facing line, such as "This only
-  approves me to look for the best places to find buyers. I won't add leads
+  approves me to look for the best places to find buyers. I won't add anyone
   yet."
 
+Use a customer-facing shape like:
+
+\`\`\`text
+## Find Buyers Plan
+
+I recommend starting with people already talking on LinkedIn about [plain
+topic]. That should help us find buyers who already care about [plain problem].
+
+I'll check whether there are enough good-fit people there. If not, I'll try
+[plain fallback] next.
+
+Approving this means I can look for the best places to find buyers. I won't add
+anyone to the campaign yet.
+\`\`\`
+
 Do not surface blanket source heuristics as product copy. Make the
 recommendation specific to the campaign. If LinkedIn engagement is recommended,
 name the exact post themes you will search in plain language, such as "Power BI
 dashboards they don't trust" or "teams trying to agree on the right KPIs."
-Avoid using "Signal Discovery" or "source scouting" in customer-facing chat;
-those are internal labels. If relevant public conversations look unlikely,
-recommend the specific Sales Nav or Prospeo lane instead and say why. Do not
-call \`search_signals\`, \`search_sales_nav\`,
+Avoid using "Signal Discovery", "source scouting", "lane", "provider",
+"precision/scale tradeoff", "evidence quality", "pilot volume", "workflow
+pain", or "ICP" in customer-facing chat; those are internal labels. If relevant public
+conversations look unlikely, recommend the specific Sales Nav or Prospeo path
+instead and explain it in plain words once. Do not call \`search_signals\`,
+\`search_sales_nav\`,
 \`search_prospeo\`,
 \`fetch_post_engagers\`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.

package/package.json

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

package/skill-templates/create-campaign.md

@@ -128,28 +128,46 @@ signals, cleanup risk, and confidence basis. If a user asks for a forecast,
 label it explicitly as not estimated from this run.
 
 Before any provider prompt, search, source scout, or signal-discovery call, show
-one source-plan gate and ask for approval. The plan must be visible before the
-question, and this first approval only authorizes finding the best places to
-look for buyers. It does not add anyone to the campaign yet. The gate should
-say:
-
-- given this campaign, the viable source options
-- the recommended first lane
-- why that lane fits the buyer, offer, and likely public activity
-- what will be tested next
-- the fallback lane if relevant posts or ICP engagement look thin
+one source-plan gate and ask for approval. Write this like a fifth grader could
+understand it: short sentences, no internal labels, and no GTM shorthand. The
+plan must be visible before the question, and this first approval only
+authorizes finding the best places to look for buyers. It does not add anyone
+to the campaign yet. The gate should say:
+
+- the buyer groups or places we could check
+- the best place to start
+- why the right buyers are likely to be there
+- what signs the next search will check
+- where you'll look next if the first place is too thin
 - what approval covers in one concise customer-facing line, such as "This only
-  approves me to look for the best places to find buyers. I won't add leads
+  approves me to look for the best places to find buyers. I won't add anyone
   yet."
 
+Use a customer-facing shape like:
+
+```text
+## Find Buyers Plan
+
+I recommend starting with people already talking on LinkedIn about [plain
+topic]. That should help us find buyers who already care about [plain problem].
+
+I'll check whether there are enough good-fit people there. If not, I'll try
+[plain fallback] next.
+
+Approving this means I can look for the best places to find buyers. I won't add
+anyone to the campaign yet.
+```
+
 Do not surface blanket source heuristics as product copy. Make the
 recommendation specific to the campaign. If LinkedIn engagement is recommended,
 name the exact post themes you will search in plain language, such as "Power BI
 dashboards they don't trust" or "teams trying to agree on the right KPIs."
-Avoid using "Signal Discovery" or "source scouting" in customer-facing chat;
-those are internal labels. If relevant public conversations look unlikely,
-recommend the specific Sales Nav or Prospeo lane instead and say why. Do not
-call `search_signals`, `search_sales_nav`,
+Avoid using "Signal Discovery", "source scouting", "lane", "provider",
+"precision/scale tradeoff", "evidence quality", "pilot volume", "workflow
+pain", or "ICP" in customer-facing chat; those are internal labels. If relevant public
+conversations look unlikely, recommend the specific Sales Nav or Prospeo path
+instead and explain it in plain words once. Do not call `search_signals`,
+`search_sales_nav`,
 `search_prospeo`,
 `fetch_post_engagers`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.