cmm-content-factorylisted

# Content Factory `cmm-content-factory` is the orchestration layer for automated content production. It does not collect sources, write every format, generate every asset, or publish by itself. It chooses the right content-stage skills, keeps the workflow state coherent, and enforces handoff contracts between stages. ## Cross-Platform Runtime Resolve the Python launcher before running a documented command: on Windows try `py -3`, then `python`; on macOS/Linux try `python3`, then `python`. Treat `python3` shown in command examples as the resolved launcher, not as a literal Windows command. Use `pathlib`/native path APIs and quote every user or task path. Never translate a Windows path by manually replacing slash characters. ## Boundary Use this skill for: - Building an end-to-end content workflow. - Turning searched or subscribed information into selected topics. - Choosing platform-specific content formats. - Coordinating article, image, video, and publishing skills. - Keeping draft packages auditable before publication. - Creating a content task record so source, planning, writing, visual, and publish artifacts can be reviewed and traced (agent-written convention, not a replay engine). Do not use this skill as: - A web-search backend. Use `cmm-web-search`. - A subscription/news collector. Daily source-pool collection is a separate, optional channel. - A final publishing approval bypass. Publishing still needs an explicit user gate. - A replacement for the specializ