SKILL.md
file-level
1
files
1
commits
0
hotspots
0
🧊 dead
0
💥 blast risk
| 1 | --- |
| 2 | name: marketing-distribution |
| 3 | description: Plan and track multi-channel distribution—social, email, partnerships—using vault notes, MCP prompts, and Hub APIs where gated writes apply. |
| 4 | compatibility: |
| 5 | - Cursor |
| 6 | - Claude Code |
| 7 | - Any runtime that can run a CLI and read this skill |
| 8 | allowed-tools: [] |
| 9 | --- |
| 10 | |
| 11 | # Marketing Distribution |
| 12 | |
| 13 | ## When to use this skill |
| 14 | |
| 15 | - User is ready to **schedule**, **sequence**, and **track** content across channels after drafts exist in `drafts/`. |
| 16 | - User needs a **single plan** that links assets, copy variants, owners, and publish dates. |
| 17 | - Vault uses **`content-creation`** folders: `drafts/`, `outlines/`, `published/`, `research/`. |
| 18 | - User is coordinating **paid + organic** and needs one table showing **asset**, **copy**, and **landing** dependencies. |
| 19 | - User wants **go/no-go** criteria per channel before spend (approvals, disclaimers, locale). |
| 20 | - User needs to confirm **what shipped**: `knowtation list-notes --folder published --order date --limit 30`. |
| 21 | |
| 22 | ## Role and responsibilities |
| 23 | |
| 24 | - Build **channel plans** with dependencies (legal hold, editor sign-off, asset delivery). |
| 25 | - Reflect **reality**: only mark “shipped” when `published/` note or external tracker confirms; vault is source of narrative, not always the cron system. |
| 26 | - Capture **UTM and tracking** parameters in a repeatable table without leaking secrets (tokens stay out of vault). |
| 27 | - Use MCP **`meeting-notes`** after syncs with partners; file under `meetings/` when that folder exists, else `outlines/distribution-*-log.md`. |
| 28 | - Run `knowtation list-notes --folder published --since <date>` to backfill distribution status accurately. |
| 29 | |
| 30 | ## Workflow |
| 31 | |
| 32 | 1. **Inputs:** `knowtation get-note outlines/campaign-*.md`; list ready drafts `knowtation list-notes --folder drafts --order date --limit 40`. |
| 33 | 2. **Window scan:** MCP **`temporal-summary`** for “what launches this week”; MCP **`daily-brief`** for last-minute vault changes affecting schedule. |
| 34 | 3. **Channel fit:** MCP **`content-plan`** repurposing pass: “turn this draft into channel-specific hooks” (store results in distribution note, not always in canonical draft). |
| 35 | 4. **Checklist note:** `knowtation write outlines/distribution-<campaign>-<phase>.md` with tables: **Channel**, **Asset brief path**, **Draft path**, **Owner**, **Date**, **Status**. |
| 36 | 5. **Partnerships:** `knowtation search "partner OR co-marketing" --folder research --limit 15`; link obligations and talking points. |
| 37 | 6. **Post-publish log:** On ship, add row + move or copy summary to `published/YYYY-MM-DD-<slug>.md` with **URLs** (user-supplied) and **metrics placeholder** for analytics agent. |
| 38 | 7. **Gates:** If schedule changes canonical copy, use **`POST /api/v1/proposals`**; quick captures from the field go to **`POST /api/v1/capture`** then you file under `outlines/` or `published/`. |
| 39 | 8. **Entity clarity:** MCP **`extract-entities`** on partner agreements pasted into `research/` to ensure channel owners and handles are correct in the plan. |
| 40 | 9. **Search:** `knowtation search "launch OR embargo OR hold" --folder outlines --limit 15` before publishing dates. |
| 41 | 10. **Resume:** MCP **`resume-session`** for multi-week launches; MCP **`daily-brief`** for schedule drift detection. |
| 42 | |
| 43 | ## Output conventions |
| 44 | |
| 45 | - **Plan:** `outlines/distribution-*.md` frontmatter `tags: [distribution, campaign]`, `project`, `status: planned|active|complete`. |
| 46 | - **Published index:** `published/` entries with **Canonical URL**, **Syndications** list, **Related drafts/** paths. |
| 47 | - **Social batch:** Reference `drafts/social-*` files; do not duplicate full thread text—link instead. |
| 48 | - **UTM table:** Columns **Channel**, **Source**, **Medium**, **Campaign**, **Content**; use placeholders like `{INSERT_TOKEN}` for secrets configured outside the vault. |
| 49 | - **Risk column:** In the main table, add **Blockers** (legal, brand, tech) with owner initials. |
| 50 | |
| 51 | ## Handoff patterns |
| 52 | |
| 53 | - **From marketing-strategy:** Campaign priorities and **non-goals**; from **writer/editor:** final `drafts/` paths and approval state. |
| 54 | - **To marketing-analytics:** Hand off `published/` URLs + campaign IDs (non-secret) for KPI tracking; include **`temporal-summary`** snapshot date range. |
| 55 | - **From marketing-visual:** Embed asset brief paths in the distribution table; block channel rows until **brief status: ready**. |
| 56 | - **Imports:** `knowtation import markdown <scheduling-export.md>` → triage into `outlines/` → `knowtation index`. |
| 57 | - **Notes API:** Prefer proposals for schedule tables that others rely on; **`POST /api/v1/notes`** only if your Hub treats schedules as non-gated. |
| 58 | - **Field updates:** Mobile **`POST /api/v1/capture`** for “delayed 2d” notes; you reconcile the master `outlines/distribution-*.md` table. |
| 59 | - **Strategy sync:** When channels change, `knowtation get-note outlines/campaign-*.md` and adjust the distribution plan in the same edit batch (via proposal). |
| 60 | - **Snippet pass:** `knowtation search "UTM OR tracking" --folder outlines --limit 15` to align tables across distribution docs. |