cmm-content-planning

星标2

分支0

更新时间2026年7月3日 10:04

Use this CMM skill to score topic candidates, select creator-ready topic cards, diagnose content direction, and turn a selected topic into a standard content plan for downstream writing, visual, video, and publishing workflows. Use when the user wants content-factory planning, topic selection, topic_card to content_plan conversion, platform/form decision, content diagnosis, or a reusable plan before drafting. All planning logic is self-contained in this skill.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

chemny

chemny/cmm-content-factory

打开 GitHub 仓库查看创作者相关仓库

下载

相关职业SOC

基于 SOC 职业分类

市场调研分析师与营销专员商业与金融运营类职业·SOC 13-1161

文件资源管理器

4 个文件

SKILL.md

readonly

同仓库更多 Skills

同仓库

cmm-content-factory

chemny/cmm-content-factory

Use this skill as an independent content factory orchestrator when the user wants to run or design an end-to-end content production workflow across active search, subscription collection, topic planning, platform writing, image/card production, video packaging, and publishing to platform drafts. It can consume a CMM business-blueprint brief, but it is not owned by the CMM business OS. It coordinates content-stage skills (planning, writing, web-search, image, visual, typesetting, video, publishing) plus the bundled remotion render engine. Live auto-publish is an optional plugin.

2026-07-032

cmm-content-writing

chemny/cmm-content-factory

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.

2026-07-032

cmm-image-creator

chemny/cmm-content-factory

Use this CMM module when the CMM content factory needs to generate final image assets through Codex native image generation or configured third-party image APIs for WeChat covers, WeChat body illustrations, Xiaohongshu images, Douyin thumbnails, blog covers, and other platform visuals. This module receives visual_plan asset specs or direct image prompts, chooses a provider, calls the bundled image generation scripts when approved, saves prompt/result metadata, and returns generated_asset records for visual-production and publishing. Image content and text must come from the image-generation backend; local resize/crop/pad is allowed only as recorded platform-size normalization.

2026-07-032

cmm-publishing

chemny/cmm-content-factory

Use this CMM skill to assemble publish packages and prepare platform draft, browser-review, manual-upload, or schedule-planning workflows from content, visual, and video packages. It directly creates CMM publish packages, support checks, metadata, asset mapping, and approval gates. It supports WeChat draft box via built-in scripts/wechat_draft.py plus browser fallback via scripts/wechat_browser_draft.mjs, X/Weibo/Douyin built-in browser publish (fill-only by default), Xiaohongshu/Rednote manual upload, and schedule planning, while marking the Bilibili gap explicitly. By default it fills the draft/composer/creator backend and stops at the publish button — the user clicks the final publish themselves; it never auto-clicks Publish/Post or sends external messages.

2026-07-032

cmm-remotion-video

chemny/cmm-content-factory

The render/execution engine of the CMM video stage — turns an article, idea, topic, research brief, or an upstream cmm-video-production video_package into a Xiaohongshu/Douyin-ready vertical short video via a structured AI-to-Remotion workflow (TTS narration, synced captions, scene visuals, cover, publish copy). Use it to actually render/produce/package the video. When the format is already fixed (e.g. a vertical card/typography video) it can be called directly and self-derives its script in standalone mode; when cmm-video-production has produced a video_package, it consumes that instead of re-scripting. For choosing format/engine first, use cmm-video-production. Especially for 30-130s Chinese social videos.

2026-07-032

cmm-typesetting

chemny/cmm-content-factory

Use this CMM skill to typeset finished article drafts into WeChat-compatible publish HTML (long-form line) OR into XHS card sets (card line). Long-form uses blocks.yaml + render_wechat.py plus CJK punctuation preflight and optional theme-gallery review. Card line uses card_text_map.yaml + render_card.py (3 templates: xhs-quick-knowledge / xhs-checklist / xhs-quote-poster, 9 skins total). Use when the user wants 公众号排版, 图文卡片, 小红书卡片, 卡片模板, or when the pipeline reaches typesetting. Does not write content, generate images, or publish.

2026-07-032

name	cmm-content-planning
description	Use this CMM skill to score topic candidates, select creator-ready topic cards, diagnose content direction, and turn a selected topic into a standard content plan for downstream writing, visual, video, and publishing workflows. Use when the user wants content-factory planning, topic selection, topic_card to content_plan conversion, platform/form decision, content diagnosis, or a reusable plan before drafting. All planning logic is self-contained in this skill.
version	0.1.0

CMM Content Planning

cmm-content-planning is the CMM planning layer between information input and content production.

It can score source/topic candidates into topic_card records, diagnose whether and how a topic should be made, and turn a selected topic_card into a standard content_plan. Downstream writing, visual, video, and publishing skills should consume the content_plan, not a bare topic title.

Boundary

Use this skill for:

Converting topic_card into content_plan.
Scoring source cards or topic candidates.
Producing a short topic board for user selection.
Diagnosing whether a selected topic is worth making.
Choosing platform and format.
Defining angle, evidence, risks, expression strategy, and first action.
Preparing structured input for cmm-content-writing, cmm-visual-production, cmm-video-production, and cmm-publishing.

Do not use this skill to:

Collect information. Use the research step per cmm-content-factory/references/research-policy.md (host-native search → cmm-web-search → guide user for material).
Draft final articles or posts.
Generate images, videos, or platform drafts.

Scope

This skill owns topic scoring, selection, and content diagnosis. All planning logic is internalized in references/planning-method.md and is self-contained; no external skill is required.

Input

Preferred input is one of:

source_card[] from cmm-web-search, subscription adapters, or user material.
topic_candidate[] from a collection system.
topic_card from a previous selection step.
A raw user topic.

When the input is a source or candidate list, score it and produce topic_card records before planning. When the input is already a chosen topic_card, skip pool scoring and continue to diagnosis.

topic_card:
  title: ""
  core_angle: ""
  why_now: ""
  topic_type: ""
  target_audience: []
  target_platform: ""
  recommended_formats: []
  final_score: 0
  score_breakdown: {}
  account_fit_note: ""
  primary_source: {}
  reference_sources: []
  creation_notes: ""
  risks: []

If the user has only a rough topic, build a minimal topic_card first. Do not pretend missing sources or platform choices are known.

Read references/content-plan-contract.md when exact fields are needed. Read references/planning-method.md for scoring, platform fit, and diagnosis rules.

Workflow

Identify the input state:
- source cards
- topic candidates
- full topic_card
- partial topic_card
- raw topic from the user
If there is a pool, score and filter candidates:
- load the user profile (~/.cmm/profile/) first; apply its topic_preferences.avoid and pillar hard rules before scoring, then use the profile-driven score shape with account_fit (falls back to the shipped default-profile.yaml when the user has none)
- reject unsupported, vague, duplicated, or marketing-only items
- keep sources attached to each surviving topic
- produce a compact topic_board when user choice is needed; show each topic's account_fit_note
If there is only one topic, build or normalize a topic_card.
Extract the planning facts:
- topic
- core angle
- why now
- audience
- platform hints
- recommended formats
- supporting sources
- risks and weak assumptions
Decide platform and format.
Select styles: pick one writing/visual/layout template id and the user profile per cmm-content-factory/references/styles/selection-rules.md. Precedence: same-turn user instruction > user profile default_styles (~/.cmm/profile/) > shipped default-profile.yaml default_styles > rules table. If no personal profile exists, load the shipped references/styles/default-profile.yaml (persona-neutral) and remind the user once to create their own. Record style_selection with a one-line selection_reason in the content_plan.
Diagnose the content shape:
- whether the topic is worth making
- what the content should prove
- what evidence is usable
- what should be avoided
- whether the expression is clean, concrete, and platform-fit
- whether visual or video production is needed
Produce a content_plan.
Stop. Do not draft final content unless the user explicitly asks for the next workflow step.

Topic Scoring Rules

Use an explainable score before creative judgment:

final_score =
  0.30 * base_signal
  0.20 * news_value
  0.15 * source_strength
  0.15 * creator_value
  0.10 * platform_fit
  0.10 * freshness
  - noise_penalty

Scores are capped to [0, 1].

Reject candidates that cannot answer both:

What happened or changed?
Why does it matter to the target audience now?

Prefer source-backed substance over polished generated titles. If a title looks templated but the source details are strong, keep the topic and regenerate the angle.

Diagnosis Dimensions

Before producing the final content_plan, diagnose five dimensions:

Dimension	Question	Plan effect
`content_value`	Is there a clear event, change, contrast, or useful problem?	Decides whether to proceed or block.
`format_fit`	Is the recommended format appropriate for the topic and platform?	Sets `platform`, `format`, and downstream needs.
`evidence_strength`	Are claims supported by inspected or credible sources?	Fills `evidence` and `risks`.
`expression_efficiency`	Can the core claim be said in one clear sentence?	Sets `core_claim` and outline direction.
`title_visual_fit`	Does the topic have a cover/title/card angle?	Sets `title_cover_direction` and visual needs.

Planning Rules

platform and format must be concrete. Avoid "all platforms" as the final plan unless the task is explicitly multi-platform.
Evidence must come from topic_card, source cards, or user-provided material. If evidence is weak, write that into risks.
Reject or block topics that are only slogans, empty announcements, vague opinions, marketing CTAs, or unsupported claims.
expression_strategy describes how to say it; it must not become a final article draft.
title_cover_direction gives a direction only. Do not batch-generate titles here.
first_action must be one concrete next step.
Default output status is draft.

Format Routing

Use these defaults unless the user or topic_card says otherwise:

Topic shape	Recommended format
Deep analysis, policy, business implication, long reasoning	`longform_analysis`
Tool list, workflow, tutorial, practical comparison	`visual_note` or `tutorial`
Strong conflict, controversy, before/after, demo story	`short_video_script`
Fast opinion, platform change, developer-facing observation	`thread`
Product/company/creator example	`case_study`

Platform hints:

wechat: long-form analysis, case study, policy/business explanation.
xiaohongshu: visual note, checklist, tool list, practical workflow.
douyin: short-video script, conflict hook, demo story.
bilibili: tutorial, deep-dive video, structured explainer.
x: thread, hot take, developer note.
weibo: short post, commentary, image-text post.

Output

If the input is a candidate pool, output a concise topic_board first and stop for user selection unless the user has already authorized automatic selection.

topic_board:
  selection_status: needs_user_choice
  topics:
    - title: ""
      core_angle: ""
      why_now: ""
      recommended_platforms: []
      recommended_formats: []
      final_score: 0
      score_breakdown: {}
      risks: []
      source_refs: []
  rejected:
    - title: ""
      reason: ""

If the topic is selected, always output a concise diagnosis plus a machine-usable content_plan.

content_plan:
  topic: ""
  audience: ""
  platform: ""
  format: ""
  core_angle: ""
  core_claim: ""
  evidence:
    - title: ""
      source: ""
      url: ""
      usage: ""
  risks: []
  expression_strategy: ""
  title_cover_direction: ""
  outline_direction: []
  first_action: ""
  downstream_needs:
    writing: true
    visual: true
    video: false
    publishing: false
  diagnosis:
    content_value: ""
    format_fit: ""
    evidence_strength: ""
    expression_efficiency: ""
    title_visual_fit: ""
  status: draft

Handoff

After producing content_plan, route only when the user asks for the next step:

Writing: cmm-content-writing
Visuals: cmm-visual-production
Video: cmm-video-production
Publishing: cmm-publishing