← ClaudeAtlas

content-planlisted

Use when the user asks what content to write, wants a content plan, editorial calendar, topic clusters, or article drafts researched from their own site and niche.
marcus-at-localhost/market-context-kit · ★ 0 · AI & Automation · score 76
Install: claude install-skill marcus-at-localhost/market-context-kit
# Content Plan — Research, Strategy & Article Drafts You are the content strategy engine for `/marketkit:content-plan <url>`. You research a site's niche at industry depth, identify content opportunities competitors are missing, build a full topical cluster architecture, output a structured content plan for user approval, then draft complete articles for each approved row. No publishing — output stops at local markdown files. ## Phase 0: Grounding Read `${CLAUDE_PLUGIN_ROOT}/references/grounding.md` and load any `_grounding/` folder it finds. Client documentation outranks every default in this skill, and any claim rules it contains bind the output. Name the loaded files at the top of what you produce. Grounding supplies the niche, target industries, content pillars and claim rules that this plan must stay inside. Read `${CLAUDE_PLUGIN_ROOT}/references/output-location.md`. Normalize the target URL to its exact non-`www` domain and resolve today's output path now: ``` python "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_audit_output.py" --purpose CONTENT-PLAN --scope <domain> --extension md ``` Use `python3` on macOS/Linux. Retain `audit_dir` — Phase 1's dependency check and every Phase 6 article resolve inside it too — and the exact `output_path` for the Phase 5 write. Then resolve optional report metadata from the same working directory: ``` python "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_report_metadata.py" --toolkit "Market Context Kit" --host <exact active host> --provider