Content Creator

**Judgement:** This skill is a deprecated redirect shim, not a content generator. It is well-scoped and appropriate only as a compatibility layer to route old `content-creator` calls to newer specialist skills. **What it actually does:** - Inspects user intent around "content creator"/content tasks. - Routes writing, SEO, and brand voice work to `content-production`. - Routes planning/ideation (content plans, calendars, topic clusters) to `content-strategy`. - Delegates social content to `social-content`. - Explicitly **does not** perform content creation or strategy itself. **Risks / Limitations:** - Provides no direct content outputs; if used as a primary content skill, it will under-deliver versus expectations. - Depends on the availability and correct configuration of successor skills (`content-production`, `content-strategy`, `social-content`). - Routing is rule-based and may misclassify edge-case or highly mixed requests. - Being deprecated, it may receive less future maintenance than the successor skills. **Recommended scenarios:** - You already have agents, workflows, or external clients that call `content-creator` and you want them to keep working while you migrate. - You need a short-term compatibility layer in a larger system while you refactor calls to `content-production` and `content-strategy` directly. **Not recommended for:** - New projects that can integrate directly with `content-production` / `content-strategy`. - Situations where you expect rich, end-to-end content handling from this skill alone (it only routes).