@sellable/mcp 0.1.265 → 0.1.267

package/package.json

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

package/skills/create-post/SKILL.md

@@ -34,6 +34,11 @@ If foundation memory is missing or too thin, ask the user to run
 `$sellable:foundation` or answer the missing foundation questions before
 drafting. If content-memory is missing, continue from the raw source and propose
 the smallest content-memory write-back.
+
+Captured ideas must be matched against transcript-derived content memory before
+premise development. The goal is to find the user's existing worldview, repeated
+phrases, proof, stories, objections, and hot-take ingredients that make the idea
+sound earned instead of newly invented.
 </command_model>
 
 <role>
@@ -156,6 +161,23 @@ post seeds. If the cluster is weak, ask workshop questions before drafting. If
 the seed is mature, use it as the source packet for premise development and
 external LinkedIn research.
 
+For every new captured idea, create a `Transcript Worldview Packet` before hook
+research:
+
+- relevant transcript index rows or content-memory clusters
+- matched story cards, proof cards, question cards, and post seeds
+- repeated user phrasing worth preserving
+- worldview ingredients: what the user seems to believe from lived experience
+- hot-take ingredients: where the user disagrees with common advice
+- proof/story available
+- proof/story missing
+- private or sensitive material to avoid
+
+If no relevant transcript/content-memory material exists, say
+`transcript_memory_match: weak` and continue only from the raw source and core
+memory. Do not fabricate worldview. Ask one or two focused questions when the
+draft would otherwise depend on missing lived proof.
+
 `writing/posts.md` is a post-writing config file, not a draft library. Treat its structure this way:
 
 - Top scratch or `## Draft Rule Candidates` sections are candidate taste notes only.
@@ -223,12 +245,15 @@ Use when the user gives a new rough idea, voice memo transcript, freestyle note,
 
 1. Call `mcp__sellable__capture_post_idea` before transformation.
 2. Preserve the raw source exactly.
-3. Distill only what the user actually said.
-4. Run hook research.
-5. Develop and select a premise card.
-6. Save hook research.
-7. Draft and validate.
-8. Save the draft.
+3. Run the `Transcript Worldview Packet` match against transcript/content-memory
+   clusters before research or hook generation.
+4. Distill only what the user actually said plus source-backed transcript
+   worldview/proof ingredients. Label anything inferred from transcripts.
+5. Run hook research.
+6. Develop and select a premise card.
+7. Save hook research.
+8. Draft and validate.
+9. Save the draft.
 
 ## Ad Hoc Mode
 
@@ -293,6 +318,8 @@ The approved pack is capped at 20 gold standards. If adding new approved example
 
 Use when the user names creators, thought leaders, profile URLs, or says to
 write variants using a specific person's recent best content as inspiration.
+Also use this mode when the user says "use my configured thought leaders",
+"use my influencers", "use the tracked people list", or similar.
 
 This mode does not clone the person's voice. It extracts public, reusable
 mechanics from their recent posts and adapts those mechanics into the user's
@@ -301,12 +328,18 @@ voice, proof, story, and product truth.
 Default workflow:
 
 1. Normalize the requested people into a `thought_leader_list` with name,
-   LinkedIn profile URL or handle, reason, and optional lane.
+   LinkedIn profile URL or handle, reason, and optional lane. If the user asks
+   for the configured list, load it from memory-backed
+   `discovery/influencers.md` and include only rows where
+   `Include in Discovery` is not `false`. Treat the `Reason` column as the
+   person's lane/adaptation brief.
 2. If the user gives only a name and the profile cannot be resolved from
    tracked people or memory, ask for the profile URL or handle before running
    person-specific research.
 3. When the host supports background agents, launch one bounded
    `thought-leader-worker` per person. If not, process each person sequentially.
+   Each configured person must receive full person-specific research; do not
+   collapse the configured list into generic space research.
 4. Each worker fetches that person's recent posts with
    `mcp__sellable__fetch_linkedin_posts`, and fetches profile/follower context
    with `mcp__sellable__fetch_linkedin_profile` when available.
@@ -381,6 +414,12 @@ Visible Flow Trace
 - raw source preserved:
 - distilled brief:
 - claims added or avoided:
+- transcript/content-memory matches:
+- worldview ingredients from transcripts:
+- hot-take ingredients from transcripts:
+- proof/story pulled:
+- proof/story gaps:
+- private/sensitive exclusions:
 
 2. Research Search Log
 - search window:
@@ -539,6 +578,8 @@ Quality-break rules:
 3. Load the gold-standard post pack if present.
 4. Verify auth/workspace if hook research will use Sellable search.
 5. Capture or load the source idea.
+6. Run a transcript/content-memory match for the source idea before hook
+   research.
 
 If local idea capture succeeds but auth/workspace is missing, keep the idea and return a typed blocked state for draft readiness:
 
@@ -548,6 +589,35 @@ If local idea capture succeeds but auth/workspace is missing, keep the idea and
 - `zero_useful_hook_results`
 - `full_text_unavailable`
 
+## Step 0.5: Transcript Worldview Packet
+
+After raw capture and before hook research, match the source idea against
+`core/transcripts/INDEX.md`, `core/content-memory/INDEX.md`, relevant cluster
+files, story/proof/question cards, post seeds, and approved core references
+returned by `mcp__sellable__get_engage_memory`.
+
+The packet must answer:
+
+```text
+Transcript Worldview Packet
+- source idea id:
+- matched clusters:
+- matched transcript references:
+- matched cards/seeds:
+- repeated user phrasing:
+- worldview ingredients:
+- hot-take ingredients:
+- proof/story available:
+- proof/story missing:
+- private/sensitive exclusions:
+- confidence: strong | medium | weak
+```
+
+Use this packet to shape premise cards, audience tension, hooks, and body
+expression. Do not treat it as permission to add unsupported claims. If the
+packet is weak, keep the post closer to the raw idea and ask for the missing
+proof/story before marking a draft ready.
+
 ## Step 1: Hook Research
 
 Use `references/hook-research-playbook.md`.
@@ -566,6 +636,9 @@ The research worker must return a compact packet only:
 - audience tension snapshot: resonating ideas, visible tensions, audience wants,
   objections, fears, and credible angles
 - premise inputs: real scenes, observed tensions, reader value openings, and proof gaps
+- transcript worldview packet: matched clusters, transcript references,
+  repeated phrasing, worldview ingredients, hot-take ingredients, proof/story
+  available, proof/story missing
 - exact phrase patterns and sentence shapes
 - post positioning breakdowns that label each meaningful line or phrase by
   narrative job and category
@@ -619,6 +692,7 @@ Record provenance:
 - lead-magnet or engagement-bait penalties
 - story mechanism when relevant
 - full-text match status
+- transcript/content-memory match status and worldview packet
 - source hook preview measurements and whether they came from full text or a search preview
 - selected hook patterns
 - audience tension snapshot and selected angle
@@ -651,6 +725,7 @@ The `Research Learning Report` must include:
 ```text
 Research status:
 - idea/topic:
+- transcript worldview packet:
 - research artifact:
 - search window:
 - keywords:
@@ -993,6 +1068,7 @@ mechanics as inspiration, in Christian/Sellable voice."
 Draft from:
 
 - exact raw idea
+- transcript worldview packet
 - selected premise card
 - selected hook
 - approved or latest `Pre-Draft Narrative Outline`
@@ -1019,6 +1095,7 @@ Every saved draft needs a validation receipt with:
 
 - source idea ID
 - hook research ID
+- transcript worldview packet
 - iteration metadata: version, priorDraftId, changeIntent, what changed,
   what improved, what got worse, score, and verdict
 - selected premise card

package/skills/create-post/references/hook-research-playbook.md

@@ -232,6 +232,8 @@ Record:
 
 - real story or scene candidates from the raw idea, memory, transcript, or
   current-session context
+- transcript worldview packet matches: clusters, transcript references, cards,
+  repeated phrasing, worldview ingredients, and hot-take ingredients
 - observed pattern candidates when no first-person story is available
 - visible tension: the uncomfortable gap, cost, contradiction, or tradeoff
 - common belief: what the audience probably believes right now
@@ -239,6 +241,7 @@ Record:
 - reader value: what the reader learns, sees differently, or can do
 - proof available: what can be safely used
 - proof missing: what cannot be claimed without user confirmation
+- private/sensitive transcript material to exclude
 
 If this section is weak, say so. Do not let the hook lab proceed as if a clever
 opening can create value that the premise does not have.
@@ -696,8 +699,12 @@ best source" tension. Do not borrow the source's dinner/community proof.
 ## Thought Leader Inspiration Workers
 
 When the user supplies a list of thought leaders, creators, profile URLs, or
-handles, run a separate inspiration analysis per person. This is different from
-general search: the source set is the person's own recent content.
+handles, run a separate inspiration analysis per person. Also do this when the
+user asks for configured thought leaders, influencers, or tracked people. The
+configured source is memory-backed `discovery/influencers.md`; include only
+rows where `Include in Discovery` is not `false`, and treat each row's `Reason`
+as that person's lane/adaptation brief. This is different from general search:
+the source set is the person's own recent content.
 
 Use one bounded background worker per person when the host supports background
 agents. If not, process the list sequentially. Each worker must keep its output
@@ -706,7 +713,8 @@ compact and must not return a full corpus dump.
 Worker steps:
 
 1. Resolve the person's profile URL or handle from the user input, tracked
-   people, or memory. If unresolved, ask for the URL/handle.
+   people, or memory. If the user asked for the configured list, resolve from
+   `discovery/influencers.md` first. If unresolved, ask for the URL/handle.
 2. Fetch recent posts with `mcp__sellable__fetch_linkedin_posts`.
 3. Fetch profile/follower context with `mcp__sellable__fetch_linkedin_profile`
    when available.
@@ -728,6 +736,12 @@ Worker steps:
 8. Create one adapted direction for the user's selected premise in
    Christian/Sellable voice.
 
+Each configured person must receive a full person-specific packet. Do not
+summarize the group as a single "GTM influencers" research pass. The later
+drafting stage should be able to compare how Alex, Zayd, Tas, Anthony, or any
+other configured person would structurally pressure-test the same Christian
+idea without copying their voice, proof, jokes, or persona.
+
 Worker output:
 
 ```text

package/skills/create-post/references/post-file-contract.md

@@ -50,10 +50,13 @@ Idea files must preserve:
 - `updatedAt`
 - exact raw source between raw-source markers
 - optional distilled brief that does not add new claims
+- transcript worldview packet when create-post has mined relevant
+  transcript/content-memory material for this idea
 
 Hook research files must preserve:
 
 - source idea ID
+- transcript/content-memory match status and transcript worldview packet
 - keywords searched
 - filters used
 - source post URLs
@@ -86,6 +89,8 @@ Draft files must preserve:
 
 - source idea ID
 - hook research ID
+- transcript worldview packet used to build the premise, worldview, and hot
+  take
 - versioned draft ID, normally ending in `_v1`, `_v2`, `_v3`, etc.
 - iteration metadata when there is a prior or baseline draft:
   - `version`

package/skills/create-post/references/post-validation.md

@@ -6,6 +6,7 @@ Every saved draft needs a validation receipt. A draft without this receipt is no
 
 - `sourceIdeaId`
 - `hookResearchId`
+- `transcriptWorldviewPacket`
 - `iteration`
 - `selectedPremiseCard`
 - `candidateHooksConsidered`
@@ -25,6 +26,8 @@ Every saved draft needs a validation receipt. A draft without this receipt is no
   step-by-step mode
 - `proofClaimsUsed`
 - `proofClaimSources`
+- `worldviewSource`
+- `hotTakeSource`
 - `storyFilesConsulted`
 - `goldStandardsConsulted`
 - `voiceRulesApplied`
@@ -172,6 +175,12 @@ Record:
 - `readerValue`: what the reader learns, sees differently, or can do
 - `proofAvailable`: source-backed proof used
 - `proofMissing`: claims intentionally avoided or requiring user input
+- `transcriptWorldviewPacket`: clusters, transcript references, cards, repeated
+  phrasing, worldview ingredients, hot-take ingredients, proof/story available,
+  proof/story missing, private exclusions, and confidence
+- `worldviewSource`: the source-backed belief that makes the post feel earned
+- `hotTakeSource`: the source-backed disagreement or operating lesson behind
+  the hook/premise
 - `sourceMessageOutline`: source post decomposition in original order, with
   paragraph/line/phrase branches, high-level goal of each branch, reader effect,
   reusable move, and adaptation guard
@@ -192,6 +201,10 @@ If the draft has no specific scene or observed pattern, no visible tension, or
 no reader value beyond "this is interesting," save as `needs_revision`. Do not
 mark it `ready` because the hook passes preview limits.
 
+Save as `needs_revision` when the post claims a worldview or hot take but the
+receipt cannot trace it to raw source, transcript/content-memory, core memory,
+or a current user answer.
+
 ## Pre-Draft Narrative Outline Audit
 
 Before a draft can be `ready`, validate that the narrative outline was locked

package/skills/create-post/references/premise-development.md

@@ -61,10 +61,14 @@ Before writing premise cards, search the available source material:
 
 - raw idea text
 - voice memo or transcript if provided
+- `Transcript Worldview Packet` from create-post capture
 - `core/story-bank.md`
 - `core/answer-bank.md`
 - `core/proof-ledger.md`
 - `core/wins-ledger.md`
+- `core/transcripts/INDEX.md`
+- `core/content-memory/INDEX.md`, relevant clusters, cards, questions, and
+  post seeds
 - approved references and gold standards
 - current-session user corrections or rejections
 
@@ -76,11 +80,37 @@ Look for:
 - a before/after: what changed in the user's belief
 - a specific object: Slack note, customer call, campaign table, reply, list,
   demo, failed draft, stale idea, messy workflow
+- repeated worldview: the user's recurring operating belief behind the idea
+- hot-take ingredient: the specific advice, default behavior, or market cliche
+  the user is pushing against
 
 If no real story is present, use an observed pattern only if it is traceable to
 the raw source or memory. Mark the gap in the premise card. Do not fabricate a
 customer, call, outcome, date, metric, or private scene.
 
+## Worldview And Hot-Take Extraction
+
+Before scoring premise cards, extract the user's source-backed worldview from
+the transcript packet:
+
+```text
+Worldview extraction:
+- worldview claim:
+- source transcript/cluster/card:
+- repeated phrase or language pattern:
+- lived proof behind it:
+- common advice it challenges:
+- hot take version:
+- public-safe version:
+- private/sensitive material to avoid:
+- confidence: strong | medium | weak
+```
+
+A good hot take is not just a contrarian sentence. It must trace to something
+the user has said, seen, shipped, sold, or learned repeatedly. If the hot take
+only exists because an outside creator framed it well, mark it as borrowed and
+do not use it as the user's premise.
+
 ## Premise Cards
 
 Generate 3-5 premise cards before hooks. Each card must use this shape:
@@ -121,6 +151,12 @@ proof available:
 proof missing:
 <claims that cannot be made yet>
 
+worldview source:
+<transcript/cluster/card/source-backed belief used>
+
+hot take:
+<public-safe sharp version of the user's source-backed disagreement>
+
 best frame:
 story | contrarian take | teardown | founder confession | future thesis | lesson