@sellable/mcp 0.1.25 → 0.1.27

package/README.md

@@ -83,14 +83,14 @@ The token is provided when you generate it. Use `list_workspaces` +
 For customer/package installs, use the public installer:
 
 ```bash
-npx -y @sellable/install@0.1.25 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
+npx -y @sellable/install@0.1.26 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
 ```
 
 If you already have `~/.sellable/config.json`, rerun/verify without rewriting
 auth:
 
 ```bash
-npx -y @sellable/install@0.1.25 --host codex
+npx -y @sellable/install@0.1.26 --host codex
 sellable --verify-only --host codex
 ```
 

package/dist/server.js

@@ -1,7 +1,7 @@
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { CallToolRequestSchema, GetPromptRequestSchema, ListPromptsRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js";
-import { getSkillByName, listSkills, stripFrontmatter } from "./skills.js";
+import { getSkillByName, listSkills } from "./skills.js";
 import { authToolDefinitions, getAuthStatus } from "./tools/auth.js";
 import { blueprintCommitToolDefinitions, handleAddColumn, handleCommitBlueprint, } from "./tools/blueprint-commit.js";
 import { bootstrapCreateCampaign, bootstrapToolDefinitions, } from "./tools/bootstrap.js";
@@ -67,6 +67,35 @@ const allTools = [
     ...blueprintCommitToolDefinitions,
     ...verifyRowToolDefinitions,
 ];
+function parseOptionalNumber(value) {
+    if (typeof value === "number" && Number.isFinite(value))
+        return value;
+    if (typeof value === "string" && value.trim() !== "") {
+        const parsed = Number(value);
+        if (Number.isFinite(parsed))
+            return parsed;
+    }
+    return undefined;
+}
+function formatSubskillPromptText(result) {
+    const header = result.chunkCount && result.chunkCount > 1
+        ? [
+            `# ${result.name} prompt chunk ${result.chunkIndex} of ${result.chunkCount}`,
+            "",
+            `Prompt length: ${result.promptLength} characters.`,
+            result.chunkingInstructions ?? "",
+            "",
+        ].join("\n")
+        : "";
+    const footer = result.hasMore && result.nextOffset !== null
+        ? [
+            "",
+            "---",
+            `Continue with offset ${result.nextOffset} and limit ${result.limit}.`,
+        ].join("\n")
+        : "";
+    return `${header}${result.prompt}${footer}`;
+}
 server.setRequestHandler(ListToolsRequestSchema, async () => ({
     tools: allTools,
 }));
@@ -447,16 +476,29 @@ server.setRequestHandler(ListPromptsRequestSchema, async () => ({
     prompts: listSkills("public").map((skill) => ({
         name: skill.name,
         description: skill.description,
+        arguments: [
+            {
+                name: "offset",
+                description: "Optional character offset for chunked prompt reads.",
+                required: false,
+            },
+            {
+                name: "limit",
+                description: "Optional max characters to return for chunked prompt reads.",
+                required: false,
+            },
+        ],
     })),
 }));
 // Get prompt content
 server.setRequestHandler(GetPromptRequestSchema, async (request) => {
     const { name } = request.params;
+    const args = request.params.arguments ?? {};
     const skill = getSkillByName(name);
     if (!skill) {
         throw new Error(`Unknown prompt: ${name}`);
     }
-    const content = stripFrontmatter(skill.content);
+    const content = getSubskillPrompt(name, parseOptionalNumber(args.offset), parseOptionalNumber(args.limit));
     return {
         description: skill.description,
         messages: [
@@ -464,7 +506,7 @@ server.setRequestHandler(GetPromptRequestSchema, async (request) => {
                 role: "user",
                 content: {
                     type: "text",
-                    text: content,
+                    text: formatSubskillPromptText(content),
                 },
             },
         ],

package/dist/tools/bootstrap.js

@@ -215,10 +215,10 @@ export async function bootstrapCreateCampaign(input = {}) {
         : "";
     const nextStep = safeToProceed
         ? resumeDetected
-            ? `Bootstrap complete.${workspaceNotice} Resume using campaign context, then load ${createCampaignSubskill?.name ?? "create-campaign"} instructions with get_subskill_prompt({ subskillName: "${createCampaignSubskill?.name ?? "create-campaign"}" }).`
+            ? `Bootstrap complete.${workspaceNotice} Resume using campaign context, then load ${createCampaignSubskill?.name ?? "create-campaign"} instructions with get_subskill_prompt({ subskillName: "${createCampaignSubskill?.name ?? "create-campaign"}" }); if the response has hasMore=true, continue with nextOffset until hasMore=false.`
             : flowVersion === "v2"
-                ? `Bootstrap complete.${workspaceNotice} Load create-campaign-v2 instructions with get_subskill_prompt({ subskillName: "create-campaign-v2" }), then start with the create-campaign-brief interview stage. Do not call create_campaign until the v2 approval gate returns approve.`
-                : `Bootstrap complete.${workspaceNotice} Load ${createCampaignSubskill?.name ?? "create-campaign"} instructions with get_subskill_prompt({ subskillName: "${createCampaignSubskill?.name ?? "create-campaign"}" }) and follow that flow before calling create_campaign.`
+                ? `Bootstrap complete.${workspaceNotice} Load create-campaign-v2 instructions with get_subskill_prompt({ subskillName: "create-campaign-v2" }); if the response has hasMore=true, continue with nextOffset until hasMore=false. Then start with the create-campaign-brief interview stage. Do not call create_campaign until the v2 approval gate returns approve.`
+                : `Bootstrap complete.${workspaceNotice} Load ${createCampaignSubskill?.name ?? "create-campaign"} instructions with get_subskill_prompt({ subskillName: "${createCampaignSubskill?.name ?? "create-campaign"}" }); if the response has hasMore=true, continue with nextOffset until hasMore=false. Follow that flow before calling create_campaign.`
         : "Bootstrap incomplete. Resolve blockingErrors and rerun bootstrap_create_campaign before provider/search/import tools.";
     // Strip prompt body from createCampaignSubskill — it's loaded via the host
     // skill prompt. Only return metadata to save context tokens.

package/dist/tools/prompts.d.ts

@@ -20,6 +20,9 @@ export interface SubskillPromptResponse {
     limit?: number;
     hasMore?: boolean;
     nextOffset?: number | null;
+    chunkIndex?: number;
+    chunkCount?: number;
+    chunkingInstructions?: string;
 }
 export interface ListSubskillPromptsResponse {
     total: number;
@@ -44,6 +47,8 @@ export interface CompleteSenderResearchInput {
     credibilitySignalsFound?: number;
     notes?: string;
 }
+export declare const DEFAULT_SUBSKILL_PROMPT_CHUNK_CHARS = 24000;
+export declare const MAX_SUBSKILL_PROMPT_CHUNK_CHARS = 24000;
 export declare const promptToolDefinitions: ({
     name: string;
     description: string;
@@ -65,6 +70,7 @@ export declare const promptToolDefinitions: ({
         required: never[];
         additionalProperties?: undefined;
     };
+    _meta?: undefined;
 } | {
     name: string;
     description: string;
@@ -95,9 +101,13 @@ export declare const promptToolDefinitions: ({
         required: never[];
         additionalProperties: boolean;
     };
+    _meta?: undefined;
 } | {
     name: string;
     description: string;
+    _meta: {
+        "anthropic/maxResultSizeChars": number;
+    };
     inputSchema: {
         type: string;
         properties: {
@@ -158,6 +168,7 @@ export declare const promptToolDefinitions: ({
         required: string[];
         additionalProperties: boolean;
     };
+    _meta?: undefined;
 } | {
     name: string;
     description: string;
@@ -195,6 +206,7 @@ export declare const promptToolDefinitions: ({
         additionalProperties: boolean;
         required?: undefined;
     };
+    _meta?: undefined;
 })[];
 export declare function getMessagePrompt(): Promise<PromptResponse>;
 export declare function listSubskillPrompts(limit?: number, includePublic?: boolean, includeInternal?: boolean): ListSubskillPromptsResponse;

package/dist/tools/prompts.js

@@ -1,6 +1,8 @@
 import { getApi } from "../api.js";
 import { getSkillByName, listSkills, stripFrontmatter } from "../skills.js";
 import { markCreateCampaignPromptLoaded, markResearchPromptLoaded, markSenderResearchCompleted, } from "./flow-preflight.js";
+export const DEFAULT_SUBSKILL_PROMPT_CHUNK_CHARS = 24_000;
+export const MAX_SUBSKILL_PROMPT_CHUNK_CHARS = 24_000;
 export const promptToolDefinitions = [
     {
         name: "get_message_prompt",
@@ -36,7 +38,10 @@ export const promptToolDefinitions = [
     },
     {
         name: "get_subskill_prompt",
-        description: "Load a Sellable subskill prompt by name. Internal subskills are not listed in prompts/list; use search_subskill_prompts when you are unsure of the exact name.",
+        description: "Load a Sellable subskill prompt by name. Large prompts are returned in portable chunks by default; continue with nextOffset until hasMore is false. Internal subskills are not listed in prompts/list; use search_subskill_prompts when you are unsure of the exact name.",
+        _meta: {
+            "anthropic/maxResultSizeChars": 200_000,
+        },
         inputSchema: {
             type: "object",
             properties: {
@@ -50,7 +55,7 @@ export const promptToolDefinitions = [
                 },
                 limit: {
                     type: "number",
-                    description: "Optional max characters to return for chunked prompt reads. Use a bounded value for very large prompts.",
+                    description: `Optional max characters to return for chunked prompt reads. Defaults to ${DEFAULT_SUBSKILL_PROMPT_CHUNK_CHARS} for large prompts and is capped at ${MAX_SUBSKILL_PROMPT_CHUNK_CHARS}.`,
                 },
             },
             required: ["subskillName"],
@@ -141,11 +146,7 @@ export function listSubskillPrompts(limit, includePublic, includeInternal) {
         })),
     };
 }
-export function getSubskillPrompt(subskillName, offset, limit) {
-    const skill = getSkillByName(subskillName);
-    if (!skill) {
-        throw new Error(`Unknown subskill prompt: ${subskillName}`);
-    }
+function markSubskillPromptLoaded(subskillName) {
     if (subskillName === "create-campaign") {
         markCreateCampaignPromptLoaded();
     }
@@ -158,17 +159,37 @@ export function getSubskillPrompt(subskillName, offset, limit) {
     if (subskillName === "research-prospect") {
         markResearchPromptLoaded("prospect", "research-prospect");
     }
+}
+export function getSubskillPrompt(subskillName, offset, limit) {
+    const skill = getSkillByName(subskillName);
+    if (!skill) {
+        throw new Error(`Unknown subskill prompt: ${subskillName}`);
+    }
+    markSubskillPromptLoaded(subskillName);
     const fullPrompt = stripFrontmatter(skill.content);
     const safeOffset = Math.min(Math.max(Number.isFinite(offset) ? Math.floor(offset ?? 0) : 0, 0), fullPrompt.length);
-    const safeLimit = Number.isFinite(limit) && limit !== undefined
+    const requestedLimit = Number.isFinite(limit) && limit !== undefined
         ? Math.max(Math.floor(limit), 1)
         : null;
+    const defaultChunkLimit = fullPrompt.length > DEFAULT_SUBSKILL_PROMPT_CHUNK_CHARS
+        ? DEFAULT_SUBSKILL_PROMPT_CHUNK_CHARS
+        : null;
+    const safeLimit = requestedLimit === null
+        ? defaultChunkLimit
+        : Math.min(requestedLimit, MAX_SUBSKILL_PROMPT_CHUNK_CHARS);
     const prompt = safeLimit === null
         ? fullPrompt
         : fullPrompt.slice(safeOffset, safeOffset + safeLimit);
     const nextOffset = safeLimit === null
         ? null
         : Math.min(safeOffset + safeLimit, fullPrompt.length);
+    const hasMore = nextOffset !== null && nextOffset < fullPrompt.length;
+    const chunkCount = safeLimit === null
+        ? 1
+        : Math.max(Math.ceil(fullPrompt.length / safeLimit), 1);
+    const chunkIndex = safeLimit === null
+        ? 1
+        : Math.min(Math.floor(safeOffset / safeLimit) + 1, chunkCount);
     return {
         name: skill.name,
         description: skill.description,
@@ -177,8 +198,13 @@ export function getSubskillPrompt(subskillName, offset, limit) {
         promptLength: fullPrompt.length,
         offset: safeOffset,
         limit: safeLimit ?? undefined,
-        hasMore: nextOffset !== null && nextOffset < fullPrompt.length,
-        nextOffset: nextOffset !== null && nextOffset < fullPrompt.length ? nextOffset : null,
+        hasMore,
+        nextOffset: hasMore ? nextOffset : null,
+        chunkIndex,
+        chunkCount,
+        chunkingInstructions: hasMore
+            ? `Continue this same prompt load with get_subskill_prompt({ subskillName: "${skill.name}", offset: ${nextOffset}, limit: ${safeLimit} }) until hasMore is false. Treat all chunks as one prompt load; do not use saved local tool-output files or machine-specific paths.`
+            : undefined,
     };
 }
 export function completeSenderResearch(input) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.25",
+  "version": "0.1.27",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign-brief/references/examples/briefs/clover.md

@@ -1,6 +1,6 @@
 # Clover Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 4
 

package/skills/create-campaign-brief/references/examples/briefs/galley.md

@@ -1,6 +1,6 @@
 # Galley Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 5
 

package/skills/create-campaign-brief/references/examples/briefs/gelee.md

@@ -1,6 +1,6 @@
 # Gelee Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 1
 

package/skills/create-campaign-brief/references/examples/briefs/hey-digital.md

@@ -1,6 +1,6 @@
 # Hey Digital Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 4
 

package/skills/create-campaign-brief/references/examples/briefs/persona.md

@@ -1,6 +1,6 @@
 # Persona Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 3
 

package/skills/create-campaign-brief/references/examples/briefs/revvix.md

@@ -1,6 +1,6 @@
 # Revvix Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 8
 

package/skills/create-campaign-brief/references/examples/briefs/sellable-dev.md

@@ -1,6 +1,6 @@
 # sellable.dev Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 304
 

package/skills/create-campaign-brief/references/examples/briefs/superposition.md

@@ -1,6 +1,6 @@
 # superposition Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 5
 

package/skills/create-campaign-brief/references/examples/briefs/superpower.md

@@ -1,6 +1,6 @@
 # Superpower Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 3
 

package/skills/create-campaign-brief/references/examples/briefs/westpark-villas.md

@@ -1,6 +1,6 @@
 # westpark villas Campaign Brief + Rubric Archive
 
-Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Source: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
 Campaigns captured: 26
 

package/skills/create-campaign-brief/references/phase75-canonical-brief-template.md

@@ -167,7 +167,7 @@ Add only when the campaign truly needs them:
 
 Reference:
 
-- [75-MESSAGE-VARIANT-GENERATION-FLOW.md](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-MESSAGE-VARIANT-GENERATION-FLOW.md)
+- `75-MESSAGE-VARIANT-GENERATION-FLOW.md` in the Phase 75 planning archive.
 
 ## Section Rules
 

package/skills/create-campaign-brief/references/phase75-good-brief-and-messaging-examples.md

@@ -1,10 +1,10 @@
 # Phase 75 Live Brief + Messaging Example Bank
 
-Source of truth: [75-LIVE-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-LIVE-CAMPAIGN-CORPUS.json)
+Source of truth: Phase 75 live campaign corpus used to generate this prompt reference.
 
-Full archive of client campaign briefs: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
+Full archive of client campaign briefs: Phase 75 all-client campaign corpus, copied into this prompt reference archive.
 
-Direct copied archive of full campaign brief content + rubrics: [brief-rubric-archive/INDEX.md](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/brief-rubric-archive/INDEX.md)
+Direct copied archive of full campaign brief content + rubrics: `brief-rubric-archive/INDEX.md` in the Phase 75 planning archive.
 
 This file distills the strongest live campaign briefs currently stored in production. The runtime gold set should stay narrow: active clients only, plus the one Hey Digital campaign that clearly performed and still teaches useful structure. The goal is not to preserve every brief shape forever. The goal is to preserve the patterns that consistently show up in the briefs that are actually usable, persuasive, and close to what Sellable has been shipping manually for clients.
 
@@ -20,7 +20,7 @@ Important note:
 
 Runtime gold pack:
 
-- [75-ACTIVE-RUNTIME-MESSAGE-PACK.md](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ACTIVE-RUNTIME-MESSAGE-PACK.md)
+- `75-ACTIVE-RUNTIME-MESSAGE-PACK.md` in the Phase 75 planning archive.
 
 ## Winning Campaigns In Scope
 

package/skills/create-campaign-v2/SKILL.md

@@ -79,7 +79,11 @@ Validated draft directory:
   `request_user_input` (enabled in Default mode by
   `[features].default_mode_request_user_input = true`, not available in
   `codex exec`). Treat them as equivalent approval/intake gates and persist the
-  same draft artifacts after the user answers. If an interactive
+  same draft artifacts after the user answers. Use this structured gate only for
+  multiple-choice decisions or approval gates. Never use it to collect open text
+  input like LinkedIn URLs, company domains, notes, pasted context, campaign
+  ideas, or feedback. For open text, ask in normal chat and wait for the user to
+  paste the value. If an interactive
   Codex session does not expose `request_user_input`, do not silently degrade to
   a plain chat question; stop and tell the user:
 
@@ -141,10 +145,10 @@ Validated draft directory:
     the campaign subject and sender before continuing.
 - If the user did not provide the launch identity, quietly call `list_senders`
   once if available. This is a shortcut to deduce who the user might be from
-  their Sellable API token and connected LinkedIn accounts. Do not present it as
-  a sender picker yet. If there is one strong likely sender, use `enrich_sender`
-  to infer their current or most recent company, then ask a structured
-  confirmation question:
+  their Sellable API token and connected LinkedIn accounts. Do not ask the user
+  to pick an input type before checking connected senders. If there is any likely
+  connected sender, use `enrich_sender` on the best match to infer their current
+  or most recent company, then ask a structured confirmation question:
 
   ```text
   I’m ready to build this in {workspace}. I found {matched sender} connected here.
@@ -152,25 +156,30 @@ Validated draft directory:
   Is that you, and is this campaign for {company}?
   ```
 
-  The options must be:
+  The structured options must be no more than three choices:
 
-  1. `Yes, that's me and this is for {company}`
-  2. `That's me, but this is for a different company`
-  3. `No, I'll paste my LinkedIn URL so you can look me up`
-  4. `No, I'll paste the company website instead`
-  5. `Other / custom`
+  1. `Yes — use {matched sender} for {company}`
+  2. `No — I'll paste a LinkedIn profile`
+  3. `Use a company domain instead`
 
-  If the user chooses option 2, ask for the company website/domain and call
-  `fetch_company` when possible, otherwise one web lookup. If the user chooses
-  option 3, ask for their LinkedIn URL, call `fetch_linkedin_profile`, infer
-  their current or most recent company, then confirm company and sender again.
-  If the user chooses option 4, ask for the company website/domain, call
-  `fetch_company` when possible, otherwise one web lookup, then ask who the
-  LinkedIn messages should send from.
+  If there are multiple likely connected senders, mention the best one in the
+  question and use option 2 for either a different connected sender or a pasted
+  LinkedIn profile.
+
+  Use the structured question tool only for the choice. Do not use
+  `request_user_input`/`AskUserQuestion` to collect a LinkedIn URL, company
+  domain, or freeform text. If the user chooses option 2, ask in normal chat:
+  `Paste the LinkedIn URL I should use, and I’ll look it up.` Then call
+  `fetch_linkedin_profile`, infer their current or most recent company, and
+  confirm company and sender again. If the user chooses option 3, ask in normal
+  chat: `Paste the company domain, and I’ll do a quick lookup before we keep
+  going.` Then call `fetch_company` when possible, otherwise one web lookup, and
+  ask who the LinkedIn messages should send from.
 
   If `list_senders` returns zero connected senders, avoid the sender-confirmation
-  branch entirely. Ask for the user's LinkedIn URL or the company they want to
-  send on behalf of so you can research context:
+  branch entirely. Do not ask the user to choose an input type with the
+  structured question tool. Ask in normal chat for the user's LinkedIn URL or the
+  company they want to send on behalf of so you can research context:
 
   ```text
   I’m ready to build this in {workspace}.
@@ -180,11 +189,11 @@ Validated draft directory:
   offer, proof, and lead source.
   ```
 
-  If there is no strong sender match, make the first setup choice ask for the
-  user's LinkedIn URL or company website. The point of this gate is not "pick a
-  sender"; it is to learn who the user is, infer the current or most recent
-  company, and then confirm who we are sending from. The customer-facing shape
-  should be:
+  If there is no strong sender match, do not show a structured choice that says
+  "LinkedIn profile" vs "Company website". The point of this gate is not "pick a
+  sender" or "pick an input type"; it is to learn who the user is, infer the
+  current or most recent company, and then confirm who we are sending from. The
+  customer-facing shape should be:
 
   ```text
   I’m ready to build this in {workspace}.
@@ -193,12 +202,7 @@ Validated draft directory:
   the company website instead.
   ```
 
-  The LinkedIn/company identity gate should ask:
-
-  1. `What’s your LinkedIn URL?` Options: `I’ll paste my LinkedIn profile`,
-     `I’ll paste the company website instead`, `Other / custom`.
-
-  After that answer, do the lightweight lookup. For a LinkedIn profile, call
+  After the user pastes a URL/domain, do the lightweight lookup. For a LinkedIn profile, call
   `fetch_linkedin_profile` and infer the user's current or most recent company
   from the profile. For a company website, call `fetch_company` when possible,
   otherwise one web lookup.
@@ -478,7 +482,9 @@ Sellable lead lists in the main three-option first batch; support them through
 custom/freeform input. If the user pastes up to 100 LinkedIn profile URLs or
 company domains, normalize the paste into a temporary local CSV and continue
 through the matching CSV preview path. Mixed, ambiguous, malformed, or oversized
-pastes should ask for a real CSV file instead of guessing.
+pastes should ask for a real CSV file instead of guessing. Uploaded CSV support
+is larger than paste support: LinkedIn profile CSVs can contain up to 7,500
+rows; domain CSVs can contain up to 7,500 rows but only 1,000 unique domains.
 
 Avoid internal wording like `Which proof points should the message be allowed
 to lean on?` because it describes the artifact, not the founder decision.
@@ -551,6 +557,10 @@ usable leads`.
 - supplied LinkedIn profile CSVs call `load_csv_linkedin_leads` in preview mode
   only before approval; do not pass `confirmed: true`, `campaignOfferId`,
   `currentStep`, `leadListId`, `sourceLeadListId`, or provider-import params
+  during the preview. After approval, this branch is a two-stage batch path:
+  materialize the full supplied CSV into a Sellable lead-list table first, then
+  use the returned `leadListId` as `sourceLeadListId` for the bounded campaign
+  review import
 - supplied company/domain CSVs call `load_csv_domains`; pre-approval
   confirmation is allowed only without `campaignOfferId` or `currentStep` and
   only to produce a standalone `domainFilterId` for campaignless
@@ -762,12 +772,13 @@ Run the `generate-messages` skill in caller-declared `DRY MODE`. Its SKILL.md
 holds the full drafting contract (retrieval, proof inventory, candidates,
 finalizer pass, voice rules, safety). This step only covers orchestration.
 This is not optional: before any write to `message-validation.md`,
-`message-review.md`, `approval-packet.md`, or a commit-gate question, the current run must load the
-full `generate-messages` prompt. In hosted/from-scratch runs, load it with
-chunked `get_subskill_prompt({ subskillName: "generate-messages", offset,
-limit })` calls so every tool result stays small enough for the streamed
-harness. Start with `offset: 0, limit: 12000`, then keep calling with
-`offset: nextOffset` until `hasMore` is false.
+`message-review.md`, `approval-packet.md`, or a commit-gate question, the
+current run must load the full `generate-messages` prompt. In hosted/from-
+scratch runs, load it with chunked `get_subskill_prompt({ subskillName:
+"generate-messages", offset, limit })` calls so every tool result stays small
+enough for the streamed harness. Start with `offset: 0`; the MCP will apply a
+portable default limit when omitted. Keep calling with `offset: nextOffset`
+until `hasMore` is false.
 In Codex-hosted runs, this is a quality gate, not just provenance: if the
 model cannot retrieve the complete prompt or cannot follow the required
 gold-standard deliberation flow, stop at `message-review` and ask for
@@ -1644,9 +1655,9 @@ Message` column's http_request writes those cells via the cascade.
 Load `core/auto-execute.yaml` exactly once at the start of Step 13. All
 subsequent steps read the already-parsed config. Do not re-load mid-run.
 Load each subskill prompt (`create-campaign-v2`, `research-sender`,
-`generate-messages`) at most once per run — if a tool result already
-told you to load a prompt, load it and remember; do not re-request the
-same prompt later.
+`generate-messages`) at most once per run. A multi-call chunk sequence counts
+as one load. If a tool result already told you to load a prompt, load all
+chunks once and remember; do not restart the same prompt from offset 0 later.
 
 After every `update_campaign({ currentStep: ... })` in the tail, narrate
 what changed and orient the user to what the watch link will show next —
@@ -1703,10 +1714,12 @@ atomic mint).
    `import_leads({ campaignOfferId, targetLeadCount: importLimit })`.
    If a manifest exists, branch by `sourceType`:
    - `supplied-linkedin-profiles`: revalidate file metadata and confirmation
-     token, confirm `load_csv_linkedin_leads` only after approval, persist the
-     returned `leadListId`, then call
-     `confirm_lead_list({ sourceLeadListId: leadListId, targetLeadCount:
-importLimit })`.
+     token, confirm `load_csv_linkedin_leads` only after approval to batch the
+     supplied CSV into a Sellable lead list, persist the returned `leadListId`,
+     then call `confirm_lead_list({ sourceLeadListId: leadListId,
+targetLeadCount: importLimit })`. Do not call `import_leads` for this
+     branch; the lead list is the source, and `confirm_lead_list` imports the
+     bounded review batch into the campaign table.
    - `existing-lead-list`: revalidate that the lead list still exists in the
      same workspace, reuse it as `sourceLeadListId`, then call
      `confirm_lead_list({ sourceLeadListId, targetLeadCount: importLimit })`.

package/skills/create-campaign-v2/SOUL.md

@@ -146,10 +146,10 @@ brief before anything is created.
 Good identity setup:
 
 ```text
-I’ll check whether you already have a connected LinkedIn account here. If I can’t
-confirm it, I’ll ask for your LinkedIn URL or company website and use that to
-understand the company before we choose the target, offer, proof, and lead
-source.
+I’ll check whether you already have a connected sender here. If I find one, I’ll
+ask whether that’s you and whether this campaign is for that company. If not,
+just paste your LinkedIn URL or company domain and I’ll look it up before we
+keep going.
 ```
 
 Bad:
@@ -167,9 +167,15 @@ First I’ll check whether your Sellable token already tells me who you are.
 Better:
 
 ```text
-I’ll first check whether you already have a connected sender here. If not, I’ll
-ask for your LinkedIn URL or company website and use that to understand the
-campaign before we choose the audience and offer.
+I found Christian Reyes connected here. Is that you, and is this campaign for
+Sellable? If not, choose LinkedIn profile or company domain and I’ll ask you to
+paste it in chat.
+```
+
+Bad:
+
+```text
+What should I use to confirm who this campaign is for?
 ```
 
 Bad:

package/skills/create-campaign-v2/core/flow.v2.json

@@ -345,7 +345,7 @@
       },
       "optionalRequiredArtifacts": ["lead-source-intake.json"],
       "toolRules": {
-        "suppliedLinkedinProfiles": "Preview only before approval: call load_csv_linkedin_leads without confirmed, campaignOfferId, currentStep, leadListId, sourceLeadListId, or provider-import parameters; skip provider discovery.",
+        "suppliedLinkedinProfiles": "Preview only before approval: call load_csv_linkedin_leads without confirmed, campaignOfferId, currentStep, leadListId, sourceLeadListId, or provider-import parameters; skip provider discovery. After approval, batch/materialize the supplied CSV into a Sellable lead list first, then use the returned leadListId as sourceLeadListId for confirm_lead_list.",
         "suppliedDomains": "May confirm load_csv_domains before approval only without campaignOfferId/currentStep to produce a standalone domainFilterId, then run a campaignless Prospeo sample constrained by domainFilterId.",
         "existingLeadList": "Skip provider discovery and sample existing rows before approval; do not clone/import until after approval.",
         "forbiddenPreApproval": [
@@ -1022,7 +1022,7 @@
           "defaultWhenMissing": "discovered-provider-import",
           "branches": {
             "normal-discovery": "import_leads({ campaignOfferId, targetLeadCount: import.importLimit })",
-            "supplied-linkedin-profiles": "confirm load_csv_linkedin_leads after approval, then confirm_lead_list({ sourceLeadListId, targetLeadCount: import.importLimit })",
+            "supplied-linkedin-profiles": "confirm load_csv_linkedin_leads after approval to batch/materialize the CSV into a lead list, persist returned leadListId, then confirm_lead_list({ sourceLeadListId: leadListId, targetLeadCount: import.importLimit }); do not call import_leads for this branch",
             "existing-lead-list": "confirm_lead_list({ sourceLeadListId: existingLeadListId, targetLeadCount: import.importLimit })",
             "supplied-domains": "reuse or confirm load_csv_domains, run campaign-associated search_prospeo({ campaignOfferId, domainFilterId }), then import_leads({ campaignOfferId, targetLeadCount: import.importLimit })"
           },

package/skills/create-campaign-v2/references/step-13-import-leads.md

@@ -23,8 +23,12 @@ Supported branches:
 
 - **No manifest / normal discovery** — use the existing provider import path.
 - **Supplied LinkedIn profile CSV** — confirm `load_csv_linkedin_leads` only
-  after approval, then import into the campaign table with
-  `confirm_lead_list({ sourceLeadListId, targetLeadCount: importLimit })`.
+  after approval to batch/materialize the full uploaded CSV into a Sellable
+  lead-list table. Persist the returned `leadListId`, then import the bounded
+  review batch into the campaign table with
+  `confirm_lead_list({ sourceLeadListId: leadListId, targetLeadCount: importLimit })`.
+  Do not call `import_leads` for this branch; the materialized lead list is the
+  source.
   Do **not** call `wait_for_lead_list_ready` for this branch; there is no
   provider import job to wait on, and probing readiness can leave the campaign
   in an import-failed state before `confirm_lead_list`.