@sellable/mcp 0.1.235 → 0.1.237

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

@@ -0,0 +1,68 @@
+# Hook Research Playbook
+
+Hook research must use current Sellable engagement data before drafting unless the user explicitly asks for `unsaved_preview`.
+
+## Search Inputs
+
+Derive 3-8 keyword searches from:
+
+- the raw idea
+- user-supplied topic
+- proven search terms in engage memory
+- tracked people/inspiration references when relevant
+
+## Default Search
+
+Use `mcp__sellable__search_engagement_posts` with practical constraints:
+
+- recent enough to reflect what is working now
+- high enough engagement to matter
+- narrow enough to match the idea
+
+Record every keyword, filter, and result count.
+
+## Full Text Reality
+
+Search results may only include previews.
+
+When full hook/body text matters:
+
+1. use the result's author/profile URL
+2. call `mcp__sellable__fetch_linkedin_posts`
+3. match recent posts by URL or LinkedIn activity ID
+4. record whether the full text was found
+
+If full text is unavailable, record `full_text_unavailable`. Use only the preview for hook analysis and do not infer missing body details.
+
+## Hook Extraction
+
+Extract structure, not wording.
+
+For each shortlisted source post, record:
+
+- URL
+- author
+- engagement totals
+- visible hook text or preview
+- line count and mobile preview fit
+- hook mechanism
+- internal question created
+- emotional trigger
+- proof/story dependency
+- replicability score
+
+## Blocked States
+
+Local idea capture can still succeed when research fails.
+
+Draft-ready output must block or retry when:
+
+- `unauthenticated`
+- `no_active_workspace`
+- `search_timeout_or_rate_limited`
+- `zero_useful_hook_results`
+- `full_text_unavailable` when the selected hook requires body context
+
+## Save Requirement
+
+Save the research with `mcp__sellable__save_hook_research` before drafting.

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

@@ -0,0 +1,88 @@
+# Post File Contract
+
+The v1 content library is local Markdown under `~/.sellable/content/linkedin/**`.
+
+## Ownership
+
+MCP/package owns:
+
+- tool definitions
+- prompt workflow
+- file schemas
+- validation rules
+- hook research rules
+
+Customer computer owns:
+
+- raw ideas
+- hook research artifacts
+- drafts
+- published post records
+- future comment history
+
+## Layout
+
+```text
+~/.sellable/content/linkedin/
+  ideas/
+    idea_YYYYMMDD_slug.md
+  research/
+    hooks/
+      research_YYYYMMDD_slug.md
+  drafts/
+    draft_YYYYMMDD_slug_v1.md
+  published/
+    YYYY/
+      post_linkedinActivityId.md
+  comments/
+    library/        # reserved only; no v1 comment drafting
+```
+
+## Required Fields
+
+Idea files must preserve:
+
+- `id`
+- `type: idea`
+- `status: captured`
+- `createdAt`
+- `updatedAt`
+- exact raw source between raw-source markers
+- optional distilled brief that does not add new claims
+
+Hook research files must preserve:
+
+- source idea ID
+- keywords searched
+- filters used
+- source post URLs
+- author/profile URLs
+- engagement totals
+- full-text availability
+- extracted hook patterns
+- selected hook basis
+
+Draft files must preserve:
+
+- source idea ID
+- hook research ID
+- draft body
+- validation receipt
+- status: `draft`, `ready`, or `needs_revision`
+
+Published files must preserve:
+
+- source draft ID when available
+- publish URL
+- LinkedIn activity ID when available
+- published date
+- optional future metrics placeholders
+
+## Safety
+
+- Do not write to a repo-local Sellable content directory.
+- Do not append new content to `~/.sellable/configs/content/linkedin-posts-drafts.md`.
+- List operations return metadata and short sanitized previews only.
+- Full raw source requires a single-object get call.
+- Drafts and published posts remain separate files.
+- Comment drafting is out of v1 scope.

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

@@ -0,0 +1,95 @@
+# Post Validation
+
+Every saved draft needs a validation receipt. A draft without this receipt is not ready.
+
+## Required Receipt Fields
+
+- `sourceIdeaId`
+- `hookResearchId`
+- `candidateHooksConsidered`
+- `selectedHook`
+- `selectedHookWhy`
+- `proofClaimsUsed`
+- `proofClaimSources`
+- `storyFilesConsulted`
+- `voiceRulesApplied`
+- `simplifierConcreteLanguageAudit`
+- `antiAiAudit`
+- `finalizerChanges`
+- `blockedReasons`
+- `retryNeededReasons`
+- `readyStatus`
+
+## Candidate Set
+
+Generate multiple hook candidates before drafting. Do not lock onto the first draft.
+
+Each candidate should include:
+
+- hook text
+- source pattern
+- score
+- proof/story dependency
+- AI-tell risk
+- why it should win or lose
+
+## Finalizer Pass
+
+After the first draft:
+
+1. remove unsupported claims
+2. tighten the hook
+3. simplify abstract phrasing
+4. replace generic language with concrete words only when supported
+5. preserve the user's actual story and point
+6. remove AI tells
+
+## Simplifier / Concrete-Language Audit
+
+Flag and rewrite:
+
+- vague abstraction
+- fake profundity
+- broad claims without proof
+- corporate phrasing
+- lines that sound polished but unsupported
+- needless meta commentary
+
+Do not make language concrete by inventing new facts.
+
+## Anti-AI Audit
+
+Reject or rewrite:
+
+- "game-changing"
+- "leverage"
+- "synergy"
+- "this is key"
+- "let that sink in"
+- "read that again"
+- generic lessons without a story
+- tidy three-part frameworks that were not in the source material
+- fabricated numbers or examples
+
+## Proof And Voice Gates
+
+Every claim must trace to at least one of:
+
+- raw idea
+- current user answer
+- `core/proof-ledger.md`
+- `core/wins-ledger.md`
+- `core/story-bank.md`
+- `core/answer-bank.md`
+- approved reference material
+
+If the necessary proof or story is missing, ask the user or return blocked/retry-needed.
+
+## Ready Status
+
+Use:
+
+- `ready` only when proof, voice, anti-AI, and concrete-language gates pass
+- `needs_revision` when a draft exists but a gate failed
+- `blocked` when required context is missing
+- `retry-needed` when a tool/package/search failure blocked the pipeline

package/skills/generate-messages/SKILL.md

@@ -939,9 +939,34 @@ here`. If sender proof matters, write it as a normal human sentence tied
   concreteness, or believability, keep the
   finalizer winner
 
-Run a `Final Subtraction Pass` after the Optional Simplifier Pass and before
-the Gold-Standard Quality Gate. This is the last copy pass and it optimizes
-for reply likelihood, not constraint coverage.
+Run a `Concrete Language Audit` after the Optional Simplifier Pass and before
+the Gold-Standard Quality Gate. This pass starts from the current selected
+winner and highlights every word, phrase, or sentence that contains:
+
+- abstract verbs
+- abstract nouns
+- abstract adjectives
+- abstract adverbs
+- cliches
+
+For every highlight, write the exact text, category, why it is too abstract or
+stale for this buyer, the concrete replacement, and whether the replacement was
+applied or the line was cut. The replacement must name a buyer-visible action,
+object, workflow, artifact, risk, result, or next step from the brief,
+lead-sample, proof inventory, or approved token rules. Do not replace abstract
+language with a different abstraction. If the concrete replacement would invent
+proof, overclaim intent, or create a safety issue, cut the phrase or route to
+`revise-message` / `revise-filter`.
+
+Use this audit as a rewrite engine, not a style note. The selected winner must
+not carry unresolved abstract or cliche language that can be made concrete from
+available evidence. If an abstract term is intentionally kept because it is the
+buyer-native category noun, document why it is buyer-native and why a concrete
+replacement would be less clear.
+
+Run a `Final Subtraction Pass` after the Concrete Language Audit and before the
+Gold-Standard Quality Gate. This is the last copy pass and it optimizes for
+reply likelihood, not constraint coverage.
 
 Goal: shortest truthful message most likely to earn a reply.
 
@@ -1830,6 +1855,14 @@ side project`, `serious company`, `legit`, or any line that argues with an
   prospect-side answer to "so what?" If a line is true but the prospect
   would not immediately understand why it matters, it is BLOCKED until
   rewritten, moved, or cut.
+- **Concrete language audit:** the selected winner must highlight and resolve
+  every abstract verb, abstract noun, abstract adjective, abstract adverb, and
+  cliche that weakens the message. For each highlighted item, replace it with a
+  buyer-visible action, object, workflow, artifact, risk, result, or next step
+  from available evidence; cut it if no safe concrete replacement exists. If a
+  highlighted item remains, the audit must explain why it is buyer-native and
+  clearer than the concrete alternative. Unresolved abstraction or cliche is
+  BLOCKED.
 - **Skeptical prospect:** the selected winner must survive a skeptical
   prospect who has been prospected on LinkedIn by similar products hundreds
   of times. If that reader would dismiss the note as founder story, vague
@@ -2607,6 +2640,14 @@ hiring for`
 - Robustness check: PASS | BLOCKED — reason
 - Decision: applied | rejected
 
+## Concrete Language Audit
+
+| Location | Highlighted Text | Category (`abstract verb` / `abstract noun` / `abstract adjective` / `abstract adverb` / `cliche`) | Why It Weakens Reply Odds | Concrete Replacement | Decision (`applied` / `cut` / `kept as buyer-native`) |
+| -------- | ---------------- | -------------------------------------------------------------------------------------------------- | ------------------------- | -------------------- | ------------------------------------------------------ |
+
+- Rewrite summary: ...
+- Remaining abstraction/cliche risk: PASS | BLOCKED — reason
+
 ## Gold-Standard Quality Gate
 
 - Believability: PASS | BLOCKED — reason
@@ -2629,6 +2670,7 @@ hiring for`
 - Brief CTA obedience: PASS | BLOCKED | NOT APPLICABLE — reason
 - CTA clarity: PASS | BLOCKED — reason
 - PS restraint: PASS | BLOCKED | OMITTED — reason
+- Concrete language audit: PASS | BLOCKED — reason
 - YC / backing PS: PASS | BLOCKED | OMITTED — reason
 - Hard-to-fake proof used correctly: PASS | BLOCKED | OMITTED — reason
 - Gold-standard match: PASS | BLOCKED — reason

package/skills/interview/SKILL.md

@@ -32,6 +32,25 @@ Load only the references needed for the current run:
   legacy workflow.
   </reference_loading>
 
+<content_bridge>
+This interview owns durable core memory. Keep identity, company truth, proof,
+stories, answer-bank entries, transcript entries, references, anti-AI rules,
+context modes, decision rules, and change-log updates under
+`~/.sellable/configs/core/**` and raw archives under `~/.sellable/interviews/**`.
+
+If the run captures a content-specific LinkedIn post idea, hook/taste
+correction, draft-first post calibration note, or voice-note transcript meant
+as a post idea, offer to bridge that item into the content library with
+`mcp__sellable__capture_post_idea` under
+`~/.sellable/content/linkedin/ideas/**`.
+
+Do not move or mirror core identity/proof/story material into
+`~/.sellable/content/**`. The content bridge is only for post ideas and
+content-specific calibration notes. `story-bank.md`, `proof-ledger.md`,
+`answer-bank.md`, transcripts, references, and raw interview archives remain
+the source of truth for stories and proof.
+</content_bridge>
+
 <modes>
 Choose the lightest mode that can produce useful memory.
 

package/skills/load-voice/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: load-voice
-description: Load Sellable voice/company memory before answering questions, writing posts, applications, replies, or other copy in the user's voice.
-visibility: public
+description: Internal utility for loading Sellable voice/company memory before generic writing tasks that are not covered by create-post or create-campaign.
+visibility: internal
 allowed-tools:
   - Read
   - Glob
@@ -18,6 +18,12 @@ answering, rewriting, reviewing, or calibrating copy in the user's voice.
 This is a read-only usage workflow. Do not interview by default, do not write
 memory files, and do not update `~/.sellable/**` unless the user explicitly
 asks to switch into `$sellable:interview`.
+
+This is no longer a normal public command. Use `$sellable:create-post` for
+LinkedIn posts; that workflow loads voice internally. Use
+`$sellable:create-campaign` for campaign/outbound work; that workflow loads its
+own campaign/sender context. This prompt remains available as a direct MCP
+utility for generic writing and review surfaces.
 </role>
 
 <default_use_cases>