@sellable/install 0.1.4 → 0.1.6

package/bin/sellable-install.mjs

@@ -9,7 +9,7 @@ import { createInterface } from "node:readline/promises";
 const DEFAULT_API_URL = "https://app.sellable.dev";
 const DEFAULT_SERVER_PACKAGE =
   process.env.SELLABLE_MCP_PACKAGE || "@sellable/mcp";
-const CODEX_PLUGIN_VERSION = "0.1.4";
+const CODEX_PLUGIN_VERSION = "0.1.6";
 const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
 
 function usage() {
@@ -395,18 +395,12 @@ function codexSkillOpenAiYaml(displayName, description) {
   return `interface:
   display_name: "${displayName.replaceAll('"', '\\"')}"
   short_description: "${description.replaceAll('"', '\\"')}"
-
-dependencies:
-  tools:
-    - type: "mcp"
-      value: "sellable"
-      description: "Sellable MCP server"
 `;
 }
 
 function createCampaignSkillMd() {
   return `---
-name: sellable:create-campaign
+name: create-campaign
 description: Create a Sellable campaign through the approval-gated workflow.
 allowed-tools:
 ${allowedToolsYaml(CREATE_CAMPAIGN_ALLOWED_TOOLS)}
@@ -418,17 +412,9 @@ Use this as the customer-facing entrypoint for Sellable campaign creation.
 
 ## Bootstrap
 
-MCP tool access is required. First load the bootstrap tools in one tool-discovery
-pass:
-
-- \`ToolSearch("select:mcp__sellable__get_auth_status")\`
-- \`ToolSearch("select:mcp__sellable__bootstrap_create_campaign")\`
-- \`ToolSearch("select:mcp__sellable__get_subskill_prompt")\`
-- \`ToolSearch("select:mcp__sellable__search_subskill_prompts")\`
-
-Do not stop before attempting this ToolSearch preload. If the
-\`mcp__sellable__*\` tools are still not exposed after ToolSearch, stop and say
-this is a Codex install/reload problem, not a campaign problem. Tell the user to
+MCP tool access is required. First call \`mcp__sellable__get_auth_status({})\`
+directly. If that tool is unavailable, stop and say this is a Codex
+install/reload problem, not a campaign problem. Tell the user to
 run \`npx -y ${INSTALL_PACKAGE_SPEC} --host all\` so the packaged MCP server,
 Codex Desktop plugin, and Sellable skill bundle are installed. If they want a
 CLI verification, tell them to run \`sellable --verify-only --host all\`. After
@@ -474,7 +460,7 @@ then retry \`get_subskill_prompt\`.
 
 function genericSellableSkillMd({ name, title, description }) {
   return `---
-name: sellable:${name}
+name: ${name}
 description: ${description}
 allowed-tools:
   - mcp__sellable__get_auth_status
@@ -488,18 +474,12 @@ Use this as the customer-facing entrypoint for the Sellable \`${name}\` workflow
 
 ## Bootstrap
 
-MCP tool access is required. Do not inspect repo files, run shell commands, use
-\`npm\`, \`node\`, local harness scripts, or read local prompt files to emulate
-this workflow.
-
-Before giving up, try to load the required tools with ToolSearch:
-
-- \`ToolSearch("select:mcp__sellable__get_auth_status")\`
-- \`ToolSearch("select:mcp__sellable__get_subskill_prompt")\`
-- \`ToolSearch("select:mcp__sellable__search_subskill_prompts")\`
+MCP tool access is required. First call \`mcp__sellable__get_auth_status({})\`
+directly. Do not inspect repo files, run shell commands, use \`npm\`, \`node\`,
+local harness scripts, or read local prompt files to emulate this workflow.
 
-If the \`mcp__sellable__*\` tools are still not exposed after ToolSearch, stop
-and say this is a Codex install/reload problem. Tell the user to run
+If the Sellable MCP tool is unavailable, stop and say this is a Codex
+install/reload problem. Tell the user to run
 \`npx -y ${INSTALL_PACKAGE_SPEC} --host all\`, fully quit and reopen Codex
 Desktop, then start a new thread.
 

package/package.json

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