@sellable/install 0.1.167 → 0.1.169

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 (2) hide show
  1. package/package.json +1 -1
  2. package/skill-templates/create-campaign.md +12 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.167",
3
+ "version": "0.1.169",
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
@@ -226,9 +226,18 @@ website traffic (`company_website_traffic`), confirmed AI Attributes including
226
226
  integrations, key customers, Google discovery, location headcount, or
227
227
  structured ICP. When using `company_icp.company_sizes` for micro/SMB/midmarket
228
228
  or enterprise sizing, pair it with `company_headcount_range` or rely on the MCP
229
- normalization that derives the range; inspect the sample for size drift. Do not
230
- use `company_intent`, and do not invent unsupported support-channel filters or
231
- AI Attribute guesses like phone/email/chat/ticket/social.
229
+ normalization that derives the range; inspect the sample for size drift. For
230
+ lookalike seeds passed as `seedCompanies` or `seedDomains`, omit `company_oids`;
231
+ the MCP backend resolves real Prospeo company IDs. Do not invent company_oids.
232
+ For company ICP geography, `geographic_scope` only accepts `single_country` or
233
+ `multi_country`; put North America style regions in `geographic_markets` as
234
+ specific markets such as United States and Canada. Product is not a
235
+ company_icp.departments value; use `titles_include` for product roles.
236
+ `company_keywords.include/exclude` values must be at least 3 characters; use
237
+ `artificial intelligence` instead of `AI`, or use confirmed attributes such as
238
+ `uses_ai` when that is the actual signal. Do not use `company_intent`, and do
239
+ not invent unsupported support-channel filters or AI Attribute guesses like
240
+ phone/email/chat/ticket/social.
232
241
 
233
242
  After scouting, ask for a second approval on Start Import. For
234
243
  LinkedIn engagement (`signal-discovery` internally), name how many