@sellable/mcp 0.1.203 → 0.1.204

package/skills/create-campaign-v2/references/gold-standard-runtime-message-pack.md

@@ -0,0 +1,252 @@
+# Gold-Standard Runtime Message Pack
+
+This is the canonical narrow message inspiration pack for `generate-messages`
+and create-campaign-v2 message drafting.
+
+Use this pack at runtime.
+Use the raw archive only for curation and strategy skeletons.
+
+## Scope
+
+Included as primary gold examples:
+
+- `sellable.dev`
+- `Hey Digital` — only `Predictable Paid Growth for B2B SaaS Leaders`
+- `Galley`
+- `Clover`
+- `Persona`
+- `Superpower` — domain-language reference only; use the cleaned low-certainty
+  opener, not retired engagement-source phrasing
+
+Not included in runtime inspiration:
+
+- `Amplify Security` — acceptance fixture only
+- `Gelee` — useful proof stack, but the visible example lacks a strong CTA and
+  can teach landing-page proof without a reply path
+- `Revvix` — useful event fixture, but the CTA is too soft for broad runtime
+  generation; use only when the campaign is explicitly event/logistics-led
+- `superposition` — excellent exact-template lock for its own hiring motion, but
+  dangerous as broad inspiration because it teaches too much sender-first "I"
+  proof stacking; retrieve only for a job-post / founder-hiring motion
+- `westpark villas`
+- any archived old-client examples outside the active set
+
+## Runtime Rules
+
+- Feed only endorsed examples into generation.
+- Keep bad lines only if they are explicitly labeled `BAD` and paired with a `BETTER` version.
+- Treat sellable.dev, Hey Digital, Persona, Galley, and Clover as the primary
+  line-level quality anchors. Superpower is useful for benefits/healthcare
+  mechanism language, but it must not outrank those examples on opener style.
+- Default to one approved message in the generated brief unless the ICP is genuinely broad.
+- A/B CTA is optional. Use it only when the second option is truly strong.
+- If there is a great low-friction proof asset or case study, that is often the best Option B.
+- Never shorten, summarize, or omit the CTA block from a gold example. If an
+  example is included at runtime, preserve the complete ask, option text, proof
+  asset, and URL lines because those are part of the motion.
+- Use the runtime set as a quality bar, not a template fill. The best examples
+  win because they make the buyer care quickly: clear signal or current-state
+  observation, one concrete mechanism, one strongest true proof/asset, and a CTA
+  that offers a useful next step.
+- Before copying any surface trait from a gold example, pass the buyer-role
+  test: as this exact buyer, is the first line relevant, is the product clear,
+  is the sender context useful rather than repetitive, is the proof the
+  strongest safe proof available, and is the CTA the lowest-friction true next
+  step? If not, choose a different shape.
+- Do not copy weak surface traits from an example. Lowercase, ellipses,
+  parentheses, or a PS only matter when they serve the motion. The first
+  selection question is always: "what is the strongest true thing we can say to
+  this buyer?"
+- Extract the job each gold line does before copying any shape. For each
+  candidate example, identify: buyer situation interrupted, why the buyer
+  replies, sender relevance, offer clarity move, mechanism clarity move, proof
+  role, CTA job, and surface traits not to copy blindly.
+- Treat proof, CTA, and PS as elements to test. Customer/result proof belongs
+  in the body, CTA, PS, or nowhere depending on whether it improves clarity,
+  believability, or reply likelihood. Supported proof is not automatically good
+  copy.
+- Metrics and time-window traction must pass the "so what?" test. Use them
+  when the buyer can immediately tell why the number matters. Otherwise
+  translate the number into the human claim it supports, test another
+  placement, or keep it internal.
+- Every selected line needs a prospect-side "so what?" answer. If a line is
+  true but the buyer would not immediately care, it is not gold-standard copy
+  yet.
+- A PS is rare. Use it only when it acts like a natural final aside: lowering
+  commitment, making a new-category preview easier to picture, verifying the
+  core claim with a wink, or carrying one short customer/result proof that
+  would bloat the body. Delete any PS that explains the pitch, patches
+  credibility, or says internal strategy out loud.
+
+## Included Message Examples
+
+### sellable.dev
+
+Why included:
+
+- strongest meta-demo CTA
+- strong product line
+- strong formatting control
+- why it works: the signal is real, the self-aware parenthetical lowers the
+  "creepy signal" risk, the product line is short and bold, and the A/B CTA
+  offers either a direct working session or a proof asset
+
+```md
+hey [name],
+
+saw you raise your hand for claude + gtm (creepy to reach out based on that, i know) - but this felt too on the nose to ignore.
+
+i'm building sellable, the only gtm platform that runs natively on claude code.
+
+we're looking for design partners - and [PERSONALIZED REASON - their team size, role, or why they're a perfect fit].
+
+two options:
+
+a) 15-min call - i'll show you how you could book more meetings with [THEIR ICP - who they want to reach], and if you like it we launch a pilot right there
+
+b) i send you the video of me using sellable to write and send this exact message to you (yes, it's that meta)
+
+p.s. yes, this message was entirely written and sent via claude code 😊
+```
+
+### Hey Digital
+
+Why included:
+
+- strongest scenario-based structure
+- good example of a strong case-study asset as Option B
+- why it works: it starts from a business moment the buyer already understands,
+  uses one peer case study as proof, explains the operating lesson in plain
+  language, and makes the second CTA valuable even without a meeting
+
+```md
+Hey Sarah,
+
+Saw Acme just closed their Series B... usually that's when the board starts asking about paid channels.
+
+We helped PostHog through that exact moment — they had a huge free user base but needed to figure out if paid could actually drive cloud conversions without burning budget. Ended up increasing cloud conversions 18.5%.
+
+The thing that made it work was having a clear system from day one... not just launching ads and hoping.
+
+two options:
+
+a) 15-min call — I walk through how PostHog set it up and what would apply to Acme
+
+b) I send you our B2B Ads Arsenal — ad templates, playbooks, and case studies from 200+ SaaS companies so you can dig in yourself
+```
+
+### Galley
+
+Why included:
+
+- strongest concrete operational offer
+- easy to picture the output
+- why it works: the pain is tactile, the mechanism is easy to visualize, and the
+  CTA lets the buyer test the product with their own real input instead of
+  committing to a generic call
+
+```md
+hey {{first_name}},
+
+this might not apply but if you're still rebuilding menu plans by hand every time a rotation changes, there's a way to skip that whole step.
+
+we built a tool that takes a menu from whatever format it's in and just... builds the whole plan. recipes, purchasing, stations, all connected. no more starting from scratch every cycle.
+
+works best for {{company_team_type}} running rotations across a bunch of locations where every menu change turns into hours of work nobody has time for.
+
+easiest way to see if it's worth a look is to try it with one of your actual menus. happy to set that up or I can send a 2-min video instead.
+```
+
+### Clover
+
+Why included:
+
+- strongest asset-led report offer
+- strongest reply-handling handoff
+- why it works: the message leads with work already done for the buyer, makes
+  the missed opportunity concrete, and asks only for permission to send a useful
+  report
+
+```md
+hey {{firstName}},
+
+we tracked every reddit discussion around {{category/keyword}} and found {{X}} conversations and {{Y}} responses where people are actively comparing tools or asking for recommendations.
+
+{{companyName}} isn't showing up in any of them yet so we put the threads into a short report for you.
+
+thought it could help to see where you can convert more customers from the few million viewers already searching for that on reddit.
+
+can I send it over?
+```
+
+### Persona
+
+Why included:
+
+- strongest proof framing
+- strongest bad-vs-better token discipline
+- why it works: the proof is not just "big number"; it explains why the number
+  matters by tying engagement to ICP alignment, then gives the buyer a choice
+  between a working session and a proof asset
+
+```md
+hey {{first_name}},
+
+not sure if this is relevant but i saw you engaging with some posts about {{founder_led_topic}} on linkedin and thought i'd send you a note.
+
+for context, {{role_group}} i ghostwrite for generated over 350 million impressions in the past 12 months.
+
+but what actually matters is that 85%+ of the engagement is ICP aligned. if there isn't ICP alignment, none of the virality or engagement matters.
+
+two options:
+
+a) in a 15 min call, i can show you a content roadmap and what i'd do for {{company}}
+
+b) i can share a page showing how one founder hit 30 million impressions in a year and another went from 0 to 60k followers in 12 months
+```
+
+Required token example from the same brief:
+
+```md
+BAD: "founders in the generative ai space i ghostwrite for generated over 350 million impressions"
+BETTER: "founders in tech i ghostwrite for generated over 350 million impressions"
+```
+
+### Superpower
+
+Why included:
+
+- simple language in a hard domain
+- useful plain-language healthcare constraint example
+- why it works: it uses a low-certainty signal bridge, explains the mechanism
+  in plain language, and keeps the ask tiny instead of forcing a call
+
+```md
+Hey {{first_name}},
+
+saw you in a few conversations around {{topic}}, so hope this is relevant.
+
+if preventive health is anywhere near the benefits plan at {{company}}, Superpower may be worth a look.
+
+it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
+
+basically your team gets to see what's coming instead of only reacting to it.
+
+should i send over the short version?
+```
+
+Locked production variant from the same Superpower campaign:
+
+```md
+subject: {{company}} + 1,000 biomarkers + 24/7 care team
+
+hey {{first_name}},
+
+curious how you're thinking about preventative health + benefits innovation given your work at {{company}}.
+
+we provide companies direct access to 100+ biomarker lab testing and screen 1,000+ conditions for every employee.
+
+then we drive behaviour change with a 24/7 care team.
+
+open to a 15 min call to learn more, or should i send over a short overview first?
+```

package/skills/create-campaign-v2/references/thomas-revision-filters.md

@@ -77,7 +77,12 @@ Revise or reject the sample when any of these happen.
 - **source-y signal narration** — reject `"saw you on..."`, `"saw you engaging with..."`, `"you commented on..."`, `"your LinkedIn activity..."`, `"you might not remember the thread..."`, `"found you through [source] and your role looked close..."`, or any line that makes the recipient feel watched unless the chosen archived motion is intentionally self-aware about the signal. For LinkedIn-post-sourced campaigns, a topic-level bridge is allowed when it explains why the note exists and stays apologetically uncertain: `"saw you in a few conversations about [topic], so may be off, but this seemed relevant."` or `"saw you in a few conversations around [topic], so hope this is relevant."` Translate the signal into natural buyer context or omit it.
 - **assumptive title-fit opener** — reject `"Your [role] role at [company] looked close to this problem"` or `"looked close to this outbound campaign problem"`. This asserts fit from title/company. Keep the apologetic uncertainty instead: `"may be off, but if [workflow] is anywhere near your lane..."`.
 - **internal-metric flex** — reject compute time, token/cache details, model names, agent-counts, orchestration internals, or similar process metrics unless the brief proves the buyer cares about that exact detail. `~5 min of compute per message` is not buyer value by itself.
-- **action lines are parallel (same subject, e.g. `It X` / `It Y` / `It Z`) but rendered as one-line paragraphs instead of bullets** — parallel action lines are the bullet case. One-line paragraphs are only for actions that carry a short narrative clause
+- **action lines are parallel and harder to scan as paragraphs** — when 3
+  adjacent product actions repeat the same subject pattern (e.g. `It drafts...`
+  / `It adapts...` / `It helps...`) and none carries narrative proof context,
+  prefer a short bullet stack for mobile readability. Keep one-line paragraphs
+  when there are only 1-2 actions, one line needs narrative context, bullets
+  feel like a landing page, or the paragraph version is clearly more human.
 - **PS carries a second proof beat that doesn't answer a different objection** — the second beat must open a dimension beat #1 didn't address (e.g. technical reliability when beat #1 was operator empathy; named backing when beat #1 was founder track record). Default PS is ONE beat
 - **apologetic source-thread PS** — reject `p.s. if the source thread was just casual reading, ignore me`, `only reaching out where the role and topic looked close`, or any PS that defends why the recipient was sourced. If the source is too weak, omit the personalization line. A relevance-risk PS such as `p.s. if this is nowhere near your outbound workflow, ignore me` is allowed because it lowers pressure without narrating the source.
 - **subject line uses the same banned glue jargon as the body** — any B2B compound noun the buyer wouldn't say naturally in conversation. Subject follows the same jargon rules as the body

package/skills/create-campaign-v2/references/validation-criteria.md

@@ -294,20 +294,23 @@ The sample set must:
   multi-sentence paragraphs. Target 5-8 one-line paragraphs total
 - split sentences that are above ~15 words or carry more than one comma
 - do not stack three workflows into one mechanism line or one comma list.
-  Give each workflow its own one-sentence paragraph, or pick the most
-  painful one and drop the others
+  Give each workflow its own line, use a short bullet stack when the three
+  actions repeat the same subject pattern, or pick the most painful one and
+  drop the others
 - **product clarity is non-negotiable**: a cold reader must be able to state
   in one sentence what the product does. Require a crisp `Product is an X
 that does Y` anchor sentence before any action breakdown, then one action
-  per one-line paragraph. Do not gesture at "that chain" / "the stack" /
-  "that work" in place of naming specific actions
+  per line. Do not gesture at "that chain" / "the stack" / "that work" in
+  place of naming specific actions
 - body flow must follow: opener → pain → what the product IS (one sentence)
   → what it DOES (one action per line, up to three) → deployment ease →
   CTA → optional PS
 - the "what it DOES" action list may render as one-line paragraphs or as a
   bullet list — whichever reads cleaner. Bullets are acceptable here (the
   rule against bullet points applies to feature/benefit marketing lists,
-  not to enumerable product actions). Never comma-stack three actions into
+  not to enumerable product actions). Prefer bullets for 3 repeated-subject
+  product actions; keep paragraphs when one line needs narrative context or the
+  paragraph version is clearly more human. Never comma-stack three actions into
   one glued sentence
 - **opener must use per-lead signal when any is present in `lead-sample.json`**
   (post, hire, visible tool, topic engagement). Category-level openers are

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

@@ -28,7 +28,7 @@ Each step writes its own artifact into the draft directory. The original
 Validated draft directory:
 
 ```text
-.sellable/create-campaign-v2/drafts/{workspace-slug}/{campaign-slug}/
+~/.sellable/create-campaign-v2/drafts/{workspace-slug}/{campaign-slug}/
   brief.md
   lead-review.md
   lead-sample.json

package/skills/create-post/SKILL.md

@@ -52,21 +52,21 @@ Core principle: Find what's ALREADY working on LinkedIn → deeply autopsy the H
 
 3. Load memory (single call):
 
-   - Call `get_engage_memory()` to read composed core identity/company memory, proven searches, tracked people, and legacy compatibility memory from `.sellable/configs/`.
+   - Call `get_engage_memory()` to read composed core identity/company memory, proven searches, tracked people, and legacy compatibility memory from `~/.sellable/configs/`.
    - Treat `memory.styleGuide.markdown` as composed engage memory: core identity/company memory first, legacy files as fallback.
    - If both core memory and compatibility voice memory are missing, inform the user they need to run the new core `interview` flow first.
 
 4. Read core and sender voice-specific configs (built-in Read tool):
 
-   - `.sellable/configs/core/about-me.md` and `.sellable/configs/core/context-modes.md` (identity + context modes for post stance)
-   - `.sellable/configs/core/story-bank.md` and `.sellable/configs/core/answer-bank.md` (real stories and reusable answers)
-   - `.sellable/configs/core/proof-ledger.md` and `.sellable/configs/core/wins-ledger.md` (safe proof and social proof)
-   - `.sellable/configs/core/anti-ai-writing-style.md` (anti-AI audit)
-   - `.sellable/configs/core/references/linkedin-posts/INDEX.md` and copied files under `core/references/linkedin-posts/`
-   - `.sellable/configs/core/references/inspiration/INDEX.md` (structural inspiration and anti-pattern references)
-   - `.sellable/configs/writing/christian-reyes-linkedin-viral.md` (post-specific voice analysis)
-   - `.sellable/configs/content/linkedin-posts-drafts.md` (existing drafts + hook bank)
-   - `.sellable/configs/discovery/post-filters.md` (exclusion rules)
+   - `~/.sellable/configs/core/about-me.md` and `~/.sellable/configs/core/context-modes.md` (identity + context modes for post stance)
+   - `~/.sellable/configs/core/story-bank.md` and `~/.sellable/configs/core/answer-bank.md` (real stories and reusable answers)
+   - `~/.sellable/configs/core/proof-ledger.md` and `~/.sellable/configs/core/wins-ledger.md` (safe proof and social proof)
+   - `~/.sellable/configs/core/anti-ai-writing-style.md` (anti-AI audit)
+   - `~/.sellable/configs/core/references/linkedin-posts/INDEX.md` and copied files under `core/references/linkedin-posts/`
+   - `~/.sellable/configs/core/references/inspiration/INDEX.md` (structural inspiration and anti-pattern references)
+   - `~/.sellable/configs/writing/christian-reyes-linkedin-viral.md` (post-specific voice analysis)
+   - `~/.sellable/configs/content/linkedin-posts-drafts.md` (existing drafts + hook bank)
+   - `~/.sellable/configs/discovery/post-filters.md` (exclusion rules)
 
 5. Use `memory.provenSearches` to prioritize high hit-rate keywords in discovery.
    </bootstrap>
@@ -76,18 +76,18 @@ Core principle: Find what's ALREADY working on LinkedIn → deeply autopsy the H
 ## MCP Tools
 
 - `mcp__sellable__get_auth_status` - Verify token + workspace context
-- `mcp__sellable__get_engage_memory` - Read all memory from `.sellable/configs/` (style guide, proven searches, tracked people)
+- `mcp__sellable__get_engage_memory` - Read all memory from `~/.sellable/configs/` (style guide, proven searches, tracked people)
 - `mcp__sellable__search_engagement_posts` - Wide post discovery by keyword
 - `mcp__sellable__fetch_linkedin_posts` - Fetch recent posts for any LinkedIn profile
 - `mcp__sellable__fetch_linkedin_profile` - Get LinkedIn profile details
-- `mcp__sellable__record_engage_proven_search` - Update keyword stats in `.sellable/configs/discovery/proven-searches.md`
+- `mcp__sellable__record_engage_proven_search` - Update keyword stats in `~/.sellable/configs/discovery/proven-searches.md`
 
 ## Built-in Tools
 
 - Task - Agent teams for parallel hook generation, drafting, and optimization
 - AskUserQuestion - Interviewer and approval gates
-- Read - Load voice configs, post drafts, and cross-skill insights from `.sellable/configs/` and `.sellable/insights/`
-- Write - Save approved posts to `.sellable/configs/content/linkedin-posts-drafts.md` and session insights to `.sellable/insights/`
+- Read - Load voice configs, post drafts, and cross-skill insights from `~/.sellable/configs/` and `~/.sellable/insights/`
+- Write - Save approved posts to `~/.sellable/configs/content/linkedin-posts-drafts.md` and session insights to `~/.sellable/insights/`
 
 </tools>
 
@@ -317,19 +317,19 @@ Thresholds: 8.0+ = ship it | 6.5-7.9 = strong | 5.0-6.4 = needs rewrite | below
 1. Run `get_auth_status`. If not OK, stop.
 2. Call `get_engage_memory()` to load style guide, proven searches, tracked people.
 3. Read voice-specific configs:
-   - `.sellable/configs/writing/christian-reyes-linkedin-viral.md`
-   - `.sellable/configs/content/linkedin-posts-drafts.md`
-   - `.sellable/configs/discovery/post-filters.md`
+   - `~/.sellable/configs/writing/christian-reyes-linkedin-viral.md`
+   - `~/.sellable/configs/content/linkedin-posts-drafts.md`
+   - `~/.sellable/configs/discovery/post-filters.md`
 4. If style guide is missing, tell user to run `/interview` first.
 5. **Fetch sender's last 20 posts** via `fetch_linkedin_posts` (lightweight voice reference — NOT a deep analysis agent, just a quick fetch):
    - Store the top 10 by engagement as voice calibration samples
    - Note the hooks, lengths, and endings that got the most engagement
    - These are used later for voice-matching drafts, not as the primary inspiration
 6. **Read cross-skill context** (lightweight — local files only, no API calls):
-   - `./.sellable/configs/audience/icp.md` (ensure posts attract the right audience)
-   - `./.sellable/configs/writing/comments.md` (comment angles that resonate → inform post topic selection)
-   - `./.sellable/insights/cross-skill.md` (learnings from engage sessions — trending topics, what angles got approved)
-   - `./.sellable/insights/engage-sessions.md` (**skim latest entry only** — topics getting engagement in comments, keyword performance, audience reactions)
+   - `~/.sellable/configs/audience/icp.md` (ensure posts attract the right audience)
+   - `~/.sellable/configs/writing/comments.md` (comment angles that resonate → inform post topic selection)
+   - `~/.sellable/insights/cross-skill.md` (learnings from engage sessions — trending topics, what angles got approved)
+   - `~/.sellable/insights/engage-sessions.md` (**skim latest entry only** — topics getting engagement in comments, keyword performance, audience reactions)
    - If any insight file doesn't exist yet, skip it silently — the system builds up over time.
 7. Ask the sender for their topic area / keywords (or "find what's hot").
 
@@ -949,7 +949,7 @@ Ask: "Which posts do you want to publish? Any edits?"
 2. Apply edits while maintaining voice fidelity and mobile optimization.
 3. Re-present edited posts.
 4. Repeat until sender approves.
-5. On final approval, offer to save to `.sellable/configs/content/linkedin-posts-drafts.md`.
+5. On final approval, offer to save to `~/.sellable/configs/content/linkedin-posts-drafts.md`.
 
 ### Memory Candidate Review
 
@@ -978,7 +978,7 @@ For each keyword used in discovery, call `record_engage_proven_search({ keyword,
 
 ### 10B: Save Winning Hooks + Body Patterns
 
-Append to `.sellable/configs/content/linkedin-posts-drafts.md`:
+Append to `~/.sellable/configs/content/linkedin-posts-drafts.md`:
 
 ```markdown
 ## Session [date]
@@ -997,7 +997,7 @@ Append to `.sellable/configs/content/linkedin-posts-drafts.md`:
 
 ### 10C: Save What Worked to Writing Config
 
-Update `.sellable/configs/writing/christian-reyes-linkedin-viral.md` by appending a new section:
+Update `~/.sellable/configs/writing/christian-reyes-linkedin-viral.md` by appending a new section:
 
 ```markdown
 ## Session Insights — [date]
@@ -1039,7 +1039,7 @@ Update `.sellable/configs/writing/christian-reyes-linkedin-viral.md` by appendin
 
 ### 10D: Save Unused Angles for Next Time (Top 9-10 Only)
 
-If the interview surfaced stories or angles that weren't used in this session's posts, save **only the top 9-10 strongest** to `.sellable/configs/content/linkedin-posts-drafts.md` under a "Queued Ideas" section. Don't hoard weak angles — if it's not worth posting next week, don't save it.
+If the interview surfaced stories or angles that weren't used in this session's posts, save **only the top 9-10 strongest** to `~/.sellable/configs/content/linkedin-posts-drafts.md` under a "Queued Ideas" section. Don't hoard weak angles — if it's not worth posting next week, don't save it.
 
 ```markdown
 ## Queued Ideas (from [date] session)
@@ -1064,7 +1064,7 @@ If any viral post authors from this session are worth tracking for future discov
 
 ### 10F: Update Cross-Skill Insights
 
-**Append** a session summary to `.sellable/insights/post-sessions.md` using the built-in Write tool:
+**Append** a session summary to `~/.sellable/insights/post-sessions.md` using the built-in Write tool:
 
 ```markdown
 ## Session — [date]
@@ -1090,7 +1090,7 @@ If any viral post authors from this session are worth tracking for future discov
 [1-2 sentence synthesis]
 ```
 
-**If any insight from this session would help engage or campaigns**, also append to `.sellable/insights/cross-skill.md`:
+**If any insight from this session would help engage or campaigns**, also append to `~/.sellable/insights/cross-skill.md`:
 
 - Format: `## From create-post ([date])` with bullet points
 - e.g., "Bold reframe hooks scored 9+ — counter-intuitive numbers in line 1 force scroll-stop"

package/skills/engage/SKILL.md

@@ -59,7 +59,7 @@ Then proceed directly to Pre-Phase (Mode Detection). All auth, memory, and confi
 - `mcp__sellable__get_auth_status` - Verify token + workspace context
 - `mcp__sellable__bootstrap_engage` - Single-sender resolve + ensure comment campaign table + fetch engaged post URLs; persists defaults
 - `mcp__sellable__bootstrap_engage_multi` - Multi-sender resolve: parallel per-sender table creation + engaged post fetch + globalEngagedPostUrls union
-- `mcp__sellable__get_engage_memory` - Read backward-compatible engage memory plus optional core identity/company memory from `.sellable/configs/core/`. The `memory.styleGuide.markdown` blob is composed engage memory: core identity/company files first, then legacy comment/sender overrides. Accepts optional `senderId`.
+- `mcp__sellable__get_engage_memory` - Read backward-compatible engage memory plus optional core identity/company memory from `~/.sellable/configs/core/`. The `memory.styleGuide.markdown` blob is composed engage memory: core identity/company files first, then legacy comment/sender overrides. Accepts optional `senderId`.
 - `mcp__sellable__set_engage_style_guide` - Write a legacy compatibility style override. Accepts optional `senderId`; it does not replace core identity memory.
 - `mcp__sellable__record_engage_proven_search` - Update keyword stats. Accepts optional `senderId` for per-sender configs.
 - `mcp__sellable__upsert_engage_tracked_person` - Add/update tracked person. Accepts optional `senderId` for per-sender configs.
@@ -75,8 +75,8 @@ Then proceed directly to Pre-Phase (Mode Detection). All auth, memory, and confi
 
 - Task - Parallel discovery agents (fresh-scanner + deep-scanner)
 - AskUserQuestion - Optional interview + approvals
-- Read - Load voice configs, post filters, and cross-skill insights from `.sellable/configs/` and `.sellable/insights/`
-- Write - Save session insights to `.sellable/insights/`
+- Read - Load voice configs, post filters, and cross-skill insights from `~/.sellable/configs/` and `~/.sellable/insights/`
+- Write - Save session insights to `~/.sellable/insights/`
 
 </tools>
 
@@ -169,7 +169,7 @@ For EACH sender, call `fetch_linkedin_posts({ linkedinUrl: sender.senderLinkedin
 For EACH sender, call `get_engage_memory({ senderId })`:
 
 - Treat `memory.styleGuide.markdown` as composed engage memory, not a flat-only style file.
-- Primary memory comes from `.sellable/configs/core/about-me.md`, `my-company.md`, `anti-ai-writing-style.md`, `proof-ledger.md`, `wins-ledger.md`, `story-bank.md`, `answer-bank.md`, `context-modes.md`, and `decision-rules.md` when present.
+- Primary memory comes from `~/.sellable/configs/core/about-me.md`, `my-company.md`, `anti-ai-writing-style.md`, `proof-ledger.md`, `wins-ledger.md`, `story-bank.md`, `answer-bank.md`, `context-modes.md`, and `decision-rules.md` when present.
 - Legacy sender files under `senders/{senderId}/` and flat `writing/*`, `audience/*`, and `faqs/*` are compatibility fallbacks and overrides.
 - If core identity/company memory and legacy voice memory are both missing, tell the user to run the new core `interview` flow before drafting.
 
@@ -177,17 +177,17 @@ For EACH sender, call `get_engage_memory({ senderId })`:
 
 Read (built-in Read tool):
 
-- `./.sellable/configs/writing/comments.md` (comment-specific rules, quality gate, approved examples)
+- `~/.sellable/configs/writing/comments.md` (comment-specific rules, quality gate, approved examples)
 - The composed engage memory is already loaded via `get_engage_memory` above. Treat the legacy writing style guide as fallback/source material, not as the primary voice source.
-- If present and useful for final gates, skim `./.sellable/configs/core/anti-ai-writing-style.md` and `./.sellable/configs/core/proof-ledger.md`.
+- If present and useful for final gates, skim `~/.sellable/configs/core/anti-ai-writing-style.md` and `~/.sellable/configs/core/proof-ledger.md`.
 
 ### Step 0.6: Read cross-skill context [OPTIONAL]
 
 Read (lightweight — local files only, no API calls):
 
-- `./.sellable/configs/audience/icp.md` (for relevance scoring in Phase 2)
-- `./.sellable/insights/cross-skill.md` (learnings from other skills)
-- `./.sellable/insights/post-sessions.md` (**skim latest entry only** — trending topics)
+- `~/.sellable/configs/audience/icp.md` (for relevance scoring in Phase 2)
+- `~/.sellable/insights/cross-skill.md` (learnings from other skills)
+- `~/.sellable/insights/post-sessions.md` (**skim latest entry only** — trending topics)
 - If any file doesn't exist, skip silently.
 
 ### Step 0.7: Build keyword strategy [REQUIRED]
@@ -365,7 +365,7 @@ Write-backs must be idempotent: use stable source keys such as `engage-session:{
 
 ### Mode: Full Interview (no core or compatibility memory for any sender — required, cannot skip)
 
-Run the new core `interview` flow. Its output should populate `.sellable/configs/core/**` first, then engage can keep legacy compatibility overrides where needed.
+Run the new core `interview` flow. Its output should populate `~/.sellable/configs/core/**` first, then engage can keep legacy compatibility overrides where needed.
 
 ## Phase 4: Draft Comments Per Sender [REQUIRED]
 
@@ -463,7 +463,7 @@ Only keep the strongest unused angles for next session.
 
 ### 6E: Update Cross-Skill Insights (shared)
 
-**Append** to `.sellable/insights/engage-sessions.md`:
+**Append** to `~/.sellable/insights/engage-sessions.md`:
 
 ```markdown
 ## Session — [date]
@@ -486,7 +486,7 @@ Only keep the strongest unused angles for next session.
 - **Try next**: [new keywords from trends]
 ```
 
-**If cross-skill insights found**, append to `.sellable/insights/cross-skill.md`:
+**If cross-skill insights found**, append to `~/.sellable/insights/cross-skill.md`:
 
 - Format: `## From engage ([date])` with bullet points
 

package/skills/engage/core/README.md

@@ -2,22 +2,22 @@
 
 ## Where Data Lives
 
-Engage memory lives in `.sellable/configs/` at the project root. The primary identity/company layer is now `.sellable/configs/core/`; legacy writing, discovery, audience, FAQ, and sender files remain compatibility layers and fallbacks.
+Engage memory lives in the home-level `~/.sellable/configs/` source of truth. The primary identity/company layer is now `~/.sellable/configs/core/`; legacy writing, discovery, audience, FAQ, and sender files remain compatibility layers and fallbacks.
 
 | Data            | Config File                                                                       | MCP Tool                                             |
 | --------------- | --------------------------------------------------------------------------------- | ---------------------------------------------------- |
-| Core identity   | `.sellable/configs/core/about-me.md`                                              | `get_engage_memory`                                  |
-| Company truth   | `.sellable/configs/core/my-company.md`                                            | `get_engage_memory`                                  |
-| Anti-AI rules   | `.sellable/configs/core/anti-ai-writing-style.md`                                 | `get_engage_memory`                                  |
-| Proof/wins      | `.sellable/configs/core/proof-ledger.md`, `.sellable/configs/core/wins-ledger.md` | `get_engage_memory`                                  |
-| Stories/answers | `.sellable/configs/core/story-bank.md`, `.sellable/configs/core/answer-bank.md`   | `get_engage_memory`                                  |
-| Context modes   | `.sellable/configs/core/context-modes.md`                                         | `get_engage_memory`                                  |
-| Style override  | `.sellable/configs/writing/styleguide-core.md` or sender override                 | `get_engage_memory` / `set_engage_style_guide`       |
-| Comment rules   | `.sellable/configs/writing/comments.md`                                           | (read via `get_engage_memory`)                       |
-| Proven searches | `.sellable/configs/discovery/proven-searches.md`                                  | `get_engage_memory` / `record_engage_proven_search`  |
-| Tracked people  | `.sellable/configs/discovery/influencers.md`                                      | `get_engage_memory` / `upsert_engage_tracked_person` |
-| Post filters    | `.sellable/configs/discovery/post-filters.md`                                     | (read by skill via Read tool)                        |
-| ICP             | `.sellable/configs/audience/icp.md`                                               | (read by skill via Read tool)                        |
+| Core identity   | `~/.sellable/configs/core/about-me.md`                                              | `get_engage_memory`                                  |
+| Company truth   | `~/.sellable/configs/core/my-company.md`                                            | `get_engage_memory`                                  |
+| Anti-AI rules   | `~/.sellable/configs/core/anti-ai-writing-style.md`                                 | `get_engage_memory`                                  |
+| Proof/wins      | `~/.sellable/configs/core/proof-ledger.md`, `~/.sellable/configs/core/wins-ledger.md` | `get_engage_memory`                                  |
+| Stories/answers | `~/.sellable/configs/core/story-bank.md`, `~/.sellable/configs/core/answer-bank.md`   | `get_engage_memory`                                  |
+| Context modes   | `~/.sellable/configs/core/context-modes.md`                                         | `get_engage_memory`                                  |
+| Style override  | `~/.sellable/configs/writing/styleguide-core.md` or sender override                 | `get_engage_memory` / `set_engage_style_guide`       |
+| Comment rules   | `~/.sellable/configs/writing/comments.md`                                           | (read via `get_engage_memory`)                       |
+| Proven searches | `~/.sellable/configs/discovery/proven-searches.md`                                  | `get_engage_memory` / `record_engage_proven_search`  |
+| Tracked people  | `~/.sellable/configs/discovery/influencers.md`                                      | `get_engage_memory` / `upsert_engage_tracked_person` |
+| Post filters    | `~/.sellable/configs/discovery/post-filters.md`                                     | (read by skill via Read tool)                        |
+| ICP             | `~/.sellable/configs/audience/icp.md`                                               | (read by skill via Read tool)                        |
 
 ## How Skills Update Configs
 
@@ -26,4 +26,4 @@ Engage memory lives in `.sellable/configs/` at the project root. The primary ide
 
 ## Migration from JSON
 
-The old `proven-searches.json`, `tracked-people.json`, and `style-guide.template.md` files have been replaced. All data now lives as readable markdown in `.sellable/configs/`. Legacy `writing/*`, `audience/*`, `faqs/*`, and `content/*` files are preserved as fallback/source material while downstream prompts move to core memory.
+The old `proven-searches.json`, `tracked-people.json`, and `style-guide.template.md` files have been replaced. All data now lives as readable markdown in `~/.sellable/configs/`. Legacy `writing/*`, `audience/*`, `faqs/*`, and `content/*` files are preserved as fallback/source material while downstream prompts move to core memory.

package/skills/find-leads/SKILL.md

@@ -47,7 +47,7 @@ If a transcript is provided, mine it before asking live questions.
 
 Create or update:
 
-`./.sellable/gtm-kickoffs/{client-slug}-{date}.md`
+`~/.sellable/gtm-kickoffs/{client-slug}-{date}.md`
 
 Minimum sections: