@sellable/install 0.1.67 → 0.1.69

package/bin/sellable-install.mjs

@@ -40,7 +40,7 @@ function getMcpVersion() {
   } catch {}
   return "latest";
 }
-const CODEX_PLUGIN_VERSION = "0.1.27";
+const CODEX_PLUGIN_VERSION = "0.1.28";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -61,6 +61,7 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.24",
   "0.1.25",
   "0.1.26",
+  "0.1.27",
 ];
 const INSTALL_PACKAGE_SPEC =
   process.env.SELLABLE_INSTALL_PACKAGE_SPEC || "@sellable/install@latest";
@@ -461,6 +462,7 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
   "mcp__sellable__get_auth_status",
   "mcp__sellable__bootstrap_create_campaign",
   "mcp__sellable__get_subskill_prompt",
+  "mcp__sellable__get_subskill_asset",
   "mcp__sellable__search_subskill_prompts",
   "mcp__sellable__get_provider_prompt",
   "mcp__sellable__get_message_prompt",
@@ -829,19 +831,24 @@ updates.
 
 1. Load canonical prompt via
    \`mcp__sellable__get_subskill_prompt({ subskillName: "create-campaign-v2" })\`.
-2. Follow that prompt exactly.
-3. For message generation, load the full \`generate-messages\` prompt in the
+2. Load the canonical workflow config via
+   \`mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "core/flow.v2.json" })\`.
+   Treat the returned JSON as the active state machine. Do not read repo-local
+   copies of this file; packaged Claude Code and Codex runs must use the MCP
+   asset loader so they share the same config.
+3. Follow that prompt and workflow config exactly.
+4. For message generation, load the full \`generate-messages\` prompt in the
    same run with chunked
    \`mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages", offset, limit })\`
    calls until \`hasMore\` is false. Do not synthesize
    \`message-validation.md\` from the brief, lead review, or general knowledge.
-4. Treat message quality as the gate before minting. Do not create a campaign,
+5. Treat message quality as the gate before minting. Do not create a campaign,
    show a commit gate, or mint anything until \`message-validation.md\` proves
    the full generate-messages workflow ran and \`message-review.md\` recommends
    \`approve-message\` against the gold-standard rules.
-5. Do not create or mutate the live campaign until the approval gate returns
+6. Do not create or mutate the live campaign until the approval gate returns
    \`approve\`.
-6. Do not ask the user to run another command.
+7. Do not ask the user to run another command.
 
 ## Fallback
 
@@ -1082,6 +1089,112 @@ function codexPluginSkills() {
   ];
 }
 
+function codexCustomAgents() {
+  const commonPrefix = `You are part of the Sellable find-leads source scout.
+
+Work only on your assigned source lane. Do not import leads, create campaigns, write campaign artifacts, or draft messages. Return concise structured evidence to the parent agent so it can synthesize the lead-source decision.`;
+
+  return [
+    {
+      filename: "linkedin-engagement-scout.toml",
+      content: `name = "linkedin_engagement_scout"
+description = "Sellable lead-source scout for LinkedIn post engagement and active conversation signals."
+model_reasoning_effort = "medium"
+sandbox_mode = "read-only"
+nickname_candidates = ["LinkedIn Engagement Scout", "Post Scout", "Engager Scout"]
+developer_instructions = """
+${commonPrefix}
+
+Your lane is LinkedIn Engagement. Internally, use the signal-discovery provider prompt and the Signals tools when available.
+
+Use the inherited Sellable MCP tools when available:
+- get_provider_prompt for signal-discovery before searching
+- search_signals to find recent post lanes
+- fetch_post_engagers to sample engagers from selected posts
+
+Process:
+1. Search 3-5 keyword/topic lanes, favoring fresh posts from the last 7-14 days.
+2. Select 3-5 promising posts when available.
+3. Fetch or sample engagers for selected posts and score rough ICP fit from visible headline/display cues.
+4. Estimate usable prospects per selected post from sampled pass rate.
+5. If the sample is good but volume is low, say how many more similar posts should be added or scraped.
+
+Return:
+- keyword lanes searched, timeframe, raw posts found, finalist posts reviewed
+- selected post URL/title, author/topic, age, engager count, sampled engagers, good fits as n/N, estimated usable prospects per post, use/discard
+- sample leads if any
+- estimated good-fit range, directional reply-rate range, false positives, recommendation, confidence
+"""
+`,
+    },
+    {
+      filename: "sales-nav-scout.toml",
+      content: `name = "sales_nav_scout"
+description = "Sellable lead-source scout for Sales Navigator role, company, and activity filters."
+model_reasoning_effort = "medium"
+sandbox_mode = "read-only"
+nickname_candidates = ["Sales Nav Scout", "Role Filter Scout", "Activity Scout"]
+developer_instructions = """
+${commonPrefix}
+
+Your lane is Sales Nav.
+
+Use the inherited Sellable MCP tools when available:
+- get_provider_prompt for sales-nav before searching
+- lookup_sales_nav_filter before dynamic filters
+- search_sales_nav for campaignless preview searches
+
+Process:
+1. Preserve target role names with CURRENT_TITLE lookups; do not rely on seniority alone when the brief names concrete roles.
+2. Build a broad-but-reasonable baseline from role/title, geography, company size, industry/account context, and recent LinkedIn activity when relevant.
+3. Run the baseline plus 1-2 refinements if the first pass is noisy or under-scaled.
+4. Verify filters actually applied: search URL contains filters, first-page rows match the intended lane, and result count does not look like an unfiltered pool.
+
+Return:
+- exact filter recipe and lookup IDs used
+- raw result count, sampled people, good fits as n/N
+- estimated good-fit range after cleanup
+- directional acceptance/reply-rate ranges
+- sample leads, false positives, recommendation, confidence
+"""
+`,
+    },
+    {
+      filename: "prospeo-contact-scout.toml",
+      content: `name = "prospeo_contact_scout"
+description = "Sellable lead-source scout for Prospeo account/domain and broad contact expansion."
+model_reasoning_effort = "medium"
+sandbox_mode = "read-only"
+nickname_candidates = ["Prospeo Contact Scout", "Domain Scout", "Contact Scout"]
+developer_instructions = """
+${commonPrefix}
+
+Your lane is Prospeo Contact.
+
+Use the inherited Sellable MCP tools when available:
+- get_provider_prompt for prospeo before searching
+- load_csv_domains when the parent supplies a CSV or domain list and no domainFilterId exists
+- search_prospeo for campaignless people previews
+
+Process:
+1. Identify whether this is domain/account targeting or broad persona expansion.
+2. For domain targeting, use or create the standalone domainFilterId before searching; never pass raw domains directly into search_prospeo.
+3. Run the narrowest useful Prospeo people preview and 1-2 refinements if quality or scale is unclear.
+4. Call out that Prospeo gives contact/account coverage but usually weaker LinkedIn intent than LinkedIn Engagement or Sales Nav activity slices.
+
+Return:
+- mode and domain/account inputs
+- exact search recipe
+- raw result count, sampled people, good fits as n/N
+- estimated good-fit range after cleanup
+- directional reply-rate range
+- sample leads, false positives, recommendation, confidence
+"""
+`,
+    },
+  ];
+}
+
 function writeCodexPluginSkills(pluginRoot, opts) {
   for (const skill of codexPluginSkills()) {
     const skillRoot = join(pluginRoot, "skills", skill.dir);
@@ -1097,6 +1210,12 @@ function writeCodexPluginSkills(pluginRoot, opts) {
   }
 }
 
+function writeCodexCustomAgents(home, opts) {
+  for (const agent of codexCustomAgents()) {
+    writeFile(join(home, "agents", agent.filename), agent.content, opts);
+  }
+}
+
 function installCodexDesktopPlugin(opts) {
   const home = codexHome();
   const configPath = join(home, "config.toml");
@@ -1147,6 +1266,7 @@ function installCodexDesktopPlugin(opts) {
     opts
   );
   writeCodexPluginSkills(pluginRoot, opts);
+  writeCodexCustomAgents(home, opts);
 
   if (!opts.dryRun) {
     rmSync(cacheRoot, { recursive: true, force: true });
@@ -1213,6 +1333,7 @@ enabled = false`
     logVerbose(
       `${C.grey}+ enable [features].default_mode_request_user_input in ${configPath}${C.reset}`
     );
+    logVerbose(`${C.grey}+ write Codex custom scout agents in ${home}/agents${C.reset}`);
   }
 
   return {
@@ -1435,6 +1556,18 @@ function verify(opts) {
         ? "Codex skill bundle present"
         : "Codex skill bundle missing",
     });
+    const codexAgentPaths = codexCustomAgents().map((agent) =>
+      join(codexHome(), "agents", agent.filename)
+    );
+    const hasCodexScouts = codexAgentPaths.every((agentPath) =>
+      existsSync(agentPath)
+    );
+    checks.push({
+      ok: hasCodexScouts,
+      label: hasCodexScouts
+        ? "Codex custom scout agents present"
+        : "Codex custom scout agents missing",
+    });
     const configPath = join(codexHome(), "config.toml");
     const configContent = existsSync(configPath)
       ? readFileSync(configPath, "utf8")
@@ -1585,6 +1718,7 @@ function printNextSteps(installedHosts, authReused) {
   if (hasCodex) {
     console.log(`        ${C.green}✓${C.reset} Codex Desktop plugin installed`);
     console.log(`        ${C.green}✓${C.reset} Skills installed`);
+    console.log(`        ${C.green}✓${C.reset} Codex source scout agents installed`);
   }
   if (authReused) {
     console.log(

package/package.json

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

package/skill-templates/create-campaign.md

@@ -8,6 +8,7 @@ allowed-tools:
   - mcp__sellable__wait_for_cli_login
   - mcp__sellable__bootstrap_create_campaign
   - mcp__sellable__get_subskill_prompt
+  - mcp__sellable__get_subskill_asset
   - mcp__sellable__search_subskill_prompts
   - mcp__sellable__get_provider_prompt
   - mcp__sellable__get_message_prompt
@@ -98,10 +99,15 @@ denominator, and sample basis.
 
 When the user has not supplied a source and multiple source angles are viable,
 scout those angles as independent branches when the host can actually do it:
-Signals / active LinkedIn posts, Sales Nav / title + company filters, and
-Prospeo / domains only when relevant. If the host runs them sequentially, do not
-claim they ran in parallel. In chat, call the downstream copy stage `message
-generation`; `message-validation.md` is only an internal proof artifact.
+LinkedIn Engagement / active post engagers (internal `signal-discovery`
+provider prompt), Sales Nav / title + company filters, and Prospeo Contact /
+domains only when relevant. In Codex, explicitly spawn the named custom scouts
+`linkedin_engagement_scout`, `sales_nav_scout`, and `prospeo_contact_scout` for
+the credible lanes; Codex does not infer subagent fan-out from generic source
+comparison wording. In Claude Code, keep using the existing Task agents under
+`.claude/agents/`. If the host runs them sequentially, do not claim they ran in
+parallel. In chat, call the downstream copy stage `message generation`;
+`message-validation.md` is only an internal proof artifact.
 
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
 lines short, use indexed section labels and bullets, and translate internal
@@ -449,19 +455,24 @@ updates.
 
 1. Load canonical prompt via
    `mcp__sellable__get_subskill_prompt({ subskillName: "create-campaign-v2" })`.
-2. Follow that prompt exactly.
-3. For message generation, load the full `generate-messages` prompt in the
+2. Load the canonical workflow config via
+   `mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "core/flow.v2.json" })`.
+   Treat the returned JSON as the active state machine. Do not read repo-local
+   copies of this file; packaged Claude Code and Codex runs must use the MCP
+   asset loader so they share the same config.
+3. Follow that prompt and workflow config exactly.
+4. For message generation, load the full `generate-messages` prompt in the
    same run with chunked
    `mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages", offset, limit })`
    calls until `hasMore` is false. Do not synthesize
    `message-validation.md` from the brief, lead review, or general knowledge.
-4. Treat message quality as the gate before minting. Do not create a campaign,
+5. Treat message quality as the gate before minting. Do not create a campaign,
    show a commit gate, or mint anything until `message-validation.md` proves
    the full generate-messages workflow ran and `message-review.md` recommends
    `approve-message` against the gold-standard rules.
-5. Do not create or mutate the live campaign until the approval gate returns
+6. Do not create or mutate the live campaign until the approval gate returns
    `approve`.
-6. Do not ask the user to run another command.
+7. Do not ask the user to run another command.
 
 ## Fallback