← ClaudeAtlas

cmm-content-writinglisted

Use this CMM skill to turn a content_plan into platform-specific draft content packages for WeChat, X, Weibo, Xiaohongshu, blog, newsletter, or script-style outputs. It directly creates CMM draft packages using internalized research, blog, social, and script writing patterns while defaulting to local draft-only output. This new CMM layer does not modify legacy writing skills and never publishes, schedules, or writes to external systems unless the user explicitly asks for a later publishing workflow.
chemny/cmm-content-factory · ★ 2 · AI & Automation · score 76
Install: claude install-skill chemny/cmm-content-factory
# CMM Content Writing `cmm-content-writing` is the writing layer in the CMM content factory. It consumes a `content_plan` from `cmm-content-planning` and produces a `content_package` for downstream visual, video, and publishing workflows. ## Cross-Platform Runtime For bundled Python validators, Windows resolves `py -3` then `python`; macOS/Linux resolves `python3` then `python`. A `python3` command shown below means the resolved launcher. Pass paths as separate quoted arguments and use native path APIs so spaces, non-ASCII names, and Windows drive letters survive. ## Boundary Use this skill for: - Turning a `content_plan` into a draft article, post, thread, note, or script. - Choosing the right writing pattern for the target platform. - Producing structured `content_package` output. - Repurposing one plan into multiple platform drafts when requested. - Preserving source discipline, claim caution, and platform-specific structure. Do not use this skill for: - Selecting topics. Use `cmm-content-planning` only after topic selection. - Generating images or video. - Publishing, scheduling, posting, or writing to Notion. ## Legacy Boundary Do not invoke or modify legacy writing skills by default. Their useful patterns are internalized here as CMM writing methods. If a legacy skill exposes a useful edge case, record it as `legacy_gap` and update this CMM skill, its references, or its contract. ## Input Preferred input is a `content_plan`: ```yaml content_plan: topic: