@sellable/mcp 0.1.205 → 0.1.206

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

@@ -294,23 +294,20 @@ 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 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
+  Give each workflow its own one-sentence paragraph, 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 line. Do not gesture at "that chain" / "the stack" / "that work" in
-  place of naming specific actions
+  per one-line paragraph. 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). 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
+  not to enumerable product actions). 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/references/watch-guide-narration.md

@@ -173,7 +173,7 @@ Review/process sample:
 }
 ```
 
-Source approved and import starting:
+Start Import approved and import starting:
 
 ```json
 {
@@ -211,7 +211,7 @@ saved. The filter recommendation must be row-specific: say why filters are
 recommended from the sample counts and examples, or say filtering may not be
 needed when the visible review rows already look clean. This is a user decision
 gate, not active filtering; do not say filtering the batch before rubrics are
-saved. The Message Draft Builder should start after the filter-choice answer;
+saved. Message Drafting should start after the filter-choice answer;
 mark it running only when that branch actually started.
 When the user chooses filters, immediately persist `enableICPFilters: true` and
 move to `create-icp-rubric` so the watched app shows Filter Rules while Codex

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

@@ -26,8 +26,8 @@ Do NOT manually run rubric-check, enrich, or message-generation
 tools — the cascade already does them.
 
 ```text
-Step 13 — materialize source list + confirm initial campaign slice
-  materialize/reuse approved source with campaignOfferId
+Step 13 — Start Import + confirm initial campaign slice
+  materialize/reuse the approved source with campaignOfferId
   import_leads(source-list target; SalesNav/Prospeo default ~1000, Signal Discovery default ~1500 engagers)
   wait_for_lead_list_ready
   confirm_lead_list(reviewBatchLimit=15)  # compact reviewBatch metadata is stored on the campaign table
@@ -35,11 +35,11 @@ Step 13 — materialize source list + confirm initial campaign slice
   update_campaign(currentStep=filter-choice)
 
 Post-import main thread
-  launch Message Draft Builder after the filter-choice answer
-  launch Lead Fit Builder only after user chooses filters
+  launch Message Drafting after the filter-choice answer
+  launch Prospect Filters only after user chooses filters
   save_rubrics({ campaignOfferId, leadScoringRubrics }) after the campaign table exists
   keep the watched app on Filter Leads after rubrics are saved
-  while on Filter Leads, show the message template recommendation from the background Message Draft Builder
+  while on Filter Leads, show the message template recommendation from background Message Drafting
   after approve-message, update_campaign_brief writes `## Approved Message Template` with `{{...}}` tokens
   only then start the initial-slice cascade
 
@@ -187,7 +187,7 @@ import milestone.
    `messaging.critique.enabled`, `handoff.autoStart`,
    `handoff.orientation`, `retry.sameToolSameError`,
    `logging.logEveryThresholdTrip`.
-2. Resolve and materialize the approved source before importing. Load
+2. Resolve and materialize the approved source after Start Import approval. Load
    `references/post-mint-source-materialization.md` when the source is normal
    discovery or when a legacy no-shell approval fixture must be replayed. If
    CampaignOffer state already attached searches/selections to this campaign,
@@ -237,7 +237,7 @@ headlineICPCriteria })` ->
      re-run a narrow campaign-scoped `search_signals` call to recover current
      post rows, or ask the user to promote the desired posts in the UI and then
      retry `import_leads`.
-     Source approval is the explicit confirmation for this selected-post
+	     Start Import approval is the explicit confirmation for this selected-post
      scrape; do not ask for a second yes/no gate between
      `select_promising_posts` and `import_leads`.
    - Sales Nav: `get_provider_prompt({ provider: "sales-nav", campaignOfferId,
@@ -352,7 +352,7 @@ Entered on `CampaignOffer.currentStep === "auto-execute-messaging"`.
 **Messages are produced by the `Generate Message` column cascade, not
 by a separate tool.** Do NOT call a `generate_messages` MCP tool —
 that tool does not exist; the full `generate-messages` subskill prompt is the
-Message Draft Builder contract for the approved template. In the autonomous tail, messages
+Message Drafting contract for the approved template. In the autonomous tail, messages
 flow through the column pipeline: `Enrich Prospect` →
 `DNC Check` → `ICP Score` → `Passes Rubric` → `Generate Message`.
 Each column's http_request auto-fires when its upstream dependency
@@ -525,7 +525,7 @@ runs.
 
 - Source-list materialization and initial-slice confirmation happen in Step 13,
   not during atomic mint.
-- Step 13 materializes/reuses the approved source with `campaignOfferId` before
+- Step 13 materializes/reuses the approved source with `campaignOfferId` after Start Import approval and before
   import. Do not import a legacy campaignless Signal source until selected posts
   exist on the campaign.
 - Full-list expansion happens only after the initial campaign setup proves out.

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 append
 
 ### 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 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.
+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.
 
 | 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 the home-level `~/.sellable/configs/` source of truth. Th
 
 ## 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: