@sellable/install 0.1.132 → 0.1.133

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/bin/sellable-install.mjs +3 -3
  2. package/package.json +1 -1
  3. package/skill-templates/create-campaign.md +3 -3
package/bin/sellable-install.mjs CHANGED
@@ -720,7 +720,7 @@ Use a customer-facing shape like:
720
720
  ## Find Buyers Plan
721
721
 
722
722
  I recommend starting with people already talking on LinkedIn about [plain
723
- topic]. That should help us find buyers who already care about [plain pain].
723
+ topic]. That should help us find buyers who already care about [plain problem].
724
724
 
725
725
  I'll check whether there are enough good-fit people there. If not, I'll try
726
726
  [plain fallback] next.
@@ -734,8 +734,8 @@ recommendation specific to the campaign. If LinkedIn engagement is recommended,
734
734
  name the exact post themes you will search in plain language, such as "Power BI
735
735
  dashboards they don't trust" or "teams trying to agree on the right KPIs."
736
736
  Avoid using "Signal Discovery", "source scouting", "lane", "provider",
737
- "precision/scale tradeoff", "evidence quality", "pilot volume", or "ICP" in
738
- customer-facing chat; those are internal labels. If relevant public
737
+ "precision/scale tradeoff", "evidence quality", "pilot volume", "workflow
738
+ pain", or "ICP" in customer-facing chat; those are internal labels. If relevant public
739
739
  conversations look unlikely, recommend the specific Sales Nav or Prospeo path
740
740
  instead and explain it in plain words once. Do not call \`search_signals\`,
741
741
  \`search_sales_nav\`,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.132",
3
+ "version": "0.1.133",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {
package/skill-templates/create-campaign.md CHANGED
@@ -149,7 +149,7 @@ Use a customer-facing shape like:
149
149
  ## Find Buyers Plan
150
150
 
151
151
  I recommend starting with people already talking on LinkedIn about [plain
152
- topic]. That should help us find buyers who already care about [plain pain].
152
+ topic]. That should help us find buyers who already care about [plain problem].
153
153
 
154
154
  I'll check whether there are enough good-fit people there. If not, I'll try
155
155
  [plain fallback] next.
@@ -163,8 +163,8 @@ recommendation specific to the campaign. If LinkedIn engagement is recommended,
163
163
  name the exact post themes you will search in plain language, such as "Power BI
164
164
  dashboards they don't trust" or "teams trying to agree on the right KPIs."
165
165
  Avoid using "Signal Discovery", "source scouting", "lane", "provider",
166
- "precision/scale tradeoff", "evidence quality", "pilot volume", or "ICP" in
167
- customer-facing chat; those are internal labels. If relevant public
166
+ "precision/scale tradeoff", "evidence quality", "pilot volume", "workflow
167
+ pain", or "ICP" in customer-facing chat; those are internal labels. If relevant public
168
168
  conversations look unlikely, recommend the specific Sales Nav or Prospeo path
169
169
  instead and explain it in plain words once. Do not call `search_signals`,
170
170
  `search_sales_nav`,