@sellable/install 0.1.804 → 0.1.806

package/lib/sellable-agent/public-skills.mjs

@@ -6,6 +6,7 @@ import {
   mkdirSync,
   readFileSync,
   renameSync,
+  rmdirSync,
   rmSync,
   writeFileSync,
 } from "node:fs";
@@ -35,6 +36,37 @@ const bundleDigest = createHash("sha256")
   .update(JSON.stringify(bundledFiles))
   .digest("hex");
 
+// Skill files this image owned under an earlier name. A renamed skill must not
+// linger beside its replacement, so each is removed when it is a plain file
+// inside plain directories; anything else is left alone.
+const retiredFiles = Object.freeze([
+  // Renamed to sellable-draft-message on 2026-10-05.
+  "skills/sellable/sellable-conversation-chess/SKILL.md",
+]);
+
+function isPlainDirectory(path) {
+  const stat = lstatSync(path, { throwIfNoEntry: false });
+  return Boolean(stat?.isDirectory() && !stat.isSymbolicLink());
+}
+
+function removeRetiredFile(profileRoot, path) {
+  let directory = profileRoot;
+  for (const name of path.split("/").slice(0, -1)) {
+    directory = join(directory, name);
+    if (!isPlainDirectory(directory)) return false;
+  }
+  const target = join(profileRoot, path);
+  const stat = lstatSync(target, { throwIfNoEntry: false });
+  if (!stat?.isFile() || stat.isSymbolicLink()) return false;
+  rmSync(target);
+  try {
+    rmdirSync(directory);
+  } catch {
+    // The directory still holds something else; keep it.
+  }
+  return true;
+}
+
 function assertDirectory(path) {
   const stat = lstatSync(path, { throwIfNoEntry: false });
   if (!stat) return;
@@ -80,6 +112,9 @@ export function reconcilePublicHermesSkills({
         }
       }
       let changed = false;
+      for (const path of retiredFiles) {
+        if (removeRetiredFile(profileRoot, path)) changed = true;
+      }
       for (const file of bundledFiles) {
         const target = join(profileRoot, file.path);
         if (

package/package.json

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

package/skill-templates/create-campaign.md

@@ -216,8 +216,8 @@ preparation, the target is wrong, or status shows the wrong campaign/table, call
 `cancel_campaign_message_preparation`; otherwise do not cancel a healthy prepare
 run. Never call `start_campaign` from message preparation; final launch remains
 a separate explicit user greenlight.
-Use Template is the default message path; AI Generated is only an explicit
-opt-out.
+First messages use Conversations or Message Testing; name the one you pick
+as create-campaign-v2 `references/message-approach.md` says.
 
 ## DNC And Blocklist Handling
 
@@ -598,7 +598,7 @@ Drafting finishes or the recommendation is reviewed. If the user skips filters,
 first, then move to Messages/message review after it has started or returned a
 ready recommendation. `update_campaign({ currentStep: "messages" })` is not
 proof of kickoff. Enrichment/filtering and Generate Message cells wait for
-message approval. AI Generated is an explicit opt-out from the template path.
+message approval (Message Testing only; Conversations has no template).
 
 The Message Drafting handoff must stay lean. Include only `campaignId`,
 `workflowTableId`, a concise brief summary, concise source summary/source-use

package/skill-templates/{conversation-chess.md → draft-message.md}

@@ -1,19 +1,20 @@
 ---
-name: conversation-chess
-description: Draft an opener, reply or follow-up from the current sender, offer and conversation. Start with the Sellable get_subskill_prompt tool for subskillName conversation-chess.
+name: draft-message
+description: Draft one opener, reply or follow-up as the current sender, from their offer and the conversation. Nothing is sent. Start with the Sellable get_subskill_prompt tool for subskillName draft-message.
 ---
 
-# Sellable Conversation Chess
+# Sellable Draft Message
 
-Use this skill for one conversational draft. It does not send messages, schedule,
+Use this skill for one message draft, in either campaign approach
+(Conversations or Message Testing). It does not send messages, schedule,
 book, approve templates, enroll prospects or change stored sender context.
 Campaign creation and row persistence remain with their existing owners.
 
-1. Load `mcp__sellable__get_subskill_prompt({ subskillName: "conversation-chess" })`.
+1. Load `mcp__sellable__get_subskill_prompt({ subskillName: "draft-message" })`.
    Read every page using its `nextOffset` until `hasMore` is false. Do not
    reconstruct the prompt from memory, a repository or a plugin-cache path.
 2. Load `core/input-contract.md` through
-   `mcp__sellable__get_subskill_asset({ subskillName: "conversation-chess", assetPath: "..." })`.
+   `mcp__sellable__get_subskill_asset({ subskillName: "draft-message", assetPath: "..." })`.
    Then load the selected guide and examples from the root prompt:
    OPENER uses `modes/opener.md` + `references/openers.md` + `references/rapport.md` +
    `references/opener-editor.md`; REPLY uses

package/skill-templates/first-campaign-onboarding.md

@@ -245,8 +245,8 @@ continue in the same conversation; do not ask the user to run another command.
    sending account: the latter belongs at Settings, not before the draft.
    The flow's order and state gates still hold: the campaign exists before
    anyone is imported, the source is chosen before the import, sample rows
-   exist before filters and messages run, and the template is saved before
-   anything is queued. Who decides each one is set by the next section. Offer
+   exist before filters and messages run, and in Message Testing the template
+   is saved before anything is queued. Who decides each one is set by the next section. Offer
    CRM or meeting integrations only as optional context when helpful.
 4. Reuse an existing draft for the same goal. Never create a duplicate because
    onboarding resumed in a new session.
@@ -304,11 +304,12 @@ for the message template: those are yours to decide and report.
 **How the first message is written.** The first campaign uses the
 Conversations approach from the workflow's `references/message-approach.md`:
 create it with `messageApproach: "conversation"`, write no message template,
-and let Sellable's writer write each first message for the person. Use Message
-Lab (`"message_test"`, one approved message to everyone) only when the
-customer asks to send the same message to everyone, to test copy, or to
-approve exact wording; then the template steps of the workflow apply and you
-approve the template yourself as before.
+and let Sellable write each first message for the person. Use Message Testing
+(`"message_test"`, one approved message to everyone) only when the customer
+asks to send the same message to everyone, to test copy, or to approve exact
+wording; then the template steps of the workflow apply and you approve the
+template yourself as before. Name the approach to the customer with the
+one-line descriptions in `references/message-approach.md`.
 
 **Approval 1: direction.** After research, write the brief, create the
 campaign with it (`create_campaign`), and post one message in this shape. The