Home / All Skills / Content & Media Creation / content-creator
English (EN)简体中文 (ZH)日本語 (JA)
Content & Media Creation · alirezarezvani/claude-skills

content-creator

Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing/SEO/brand-voice tasks or content-strategy for planning tasks.

L1 Basic · Source registration onlyV1 Commit-PinnedDual-pass Audit
Author alirezarezvaniGitHub alirezarezvani/claude-skills ↗Stars 25977License MIT（SKILL.md frontmatter `license: MIT`；仓库根 LICENSE：'MIT License / Copyright (c) 2025 Alireza Rezvani'；GitHub API spdx_id=MIT）Commit 19392f7a08
Control levels describe skill capabilities and suggested control measures; they do not represent quality or safety certifications, nor do they dictate usability. Usage decisions rest entirely with users and administrators. Different agent hosts apply varying constraints; do not assume hosts provide automatic protection. Third-party skill copyrights belong to their original authors. Use at your own risk.

1How It Works & Mechanism

This is not an operational skill, but a deprecation routing table: aside from a deprecation notice, the body consists entirely of 'You want X → Use Y' mappings and explicitly forbids processing requests in place.

marketing-skill/skills/content-creator/SKILL.md
## Communication This is a redirect skill. Route the user to the correct specialist — don't attempt to handle the request here.
What it is doing: Preserving the decommissioned slug as a 'tombstone router' so legacy invocations (e.g., users saying 'content creator' or old documentation pointing to this skill) do not fail, but are instead handed off to the split specialist skills. For an agent, it represents pure decision logic: identify intent → name the successor → halt.

The rationale for deprecation is documented directly in the body of SKILL.md (not just in the changelog): the original skill tried to do too much (covering planning/writing/SEO/social/brand voice all at once), resulting in mediocre outputs across the board, which led to splitting it into two specialists: content-production and content-strategy.

marketing-skill/skills/content-creator/SKILL.md
## Why the Change The original `content-creator` tried to do everything: planning, writing, SEO, social, brand voice. That made it a jack of all trades. The specialist skills do each job better: - **content-production** — Full pipeline: research → brief → draft → optimize → publish. Includes all Python tools from the original content-creator. - **content-strategy** — Strategic planning: topic clusters, keyword research, content calendars, prioritization frameworks.
This section also serves as migration instructions: it clarifies the ownership of Python tools from the original skill (all moved to content-production) so users know capabilities were not lost. Verification confirmed that the successor directories and scripts indeed exist in the same repository.

The routing decision table maps five categories of intent ('write / plan / brand voice / SEO / social') across four different successors, and trigger phrases are documented in the frontmatter description (for host auto-matching).

marketing-skill/skills/content-creator/SKILL.md
| **Write** a blog post, article, or guide | [content-production](../content-production/) | | **Plan** what content to create, topic clusters, calendar | [content-strategy](../content-strategy/) | | **Analyze brand voice** | [content-production](../content-production/) (includes `brand_voice_analyzer.py`) | | **Optimize SEO** for existing content | [content-production](../content-production/) (includes `seo_optimizer.py`) | | **Create social media content** | [social-content](../social-content/) |
Note that links use relative paths like ../content-production/—this requires host support for resolving relative links within skills; the Skill Map in marketing-skill/CLAUDE.md also reflects this mapping using directory names ('content-production/ — Write content (blog posts, articles, guides)').

It includes two 'active triggers': if a user simply says 'content creator', it defaults to writing intent and routes to content-production; saying 'content plan / what should I write' routes to content-strategy.

marketing-skill/skills/content-creator/SKILL.md
## Proactive Triggers - **User asks "content creator"** → Route to content-production (most likely intent is writing). - **User asks "content plan" or "what should I write"** → Route to content-strategy.
This provides fallback handling for ambiguous intent: hardcoding the most common default preference (writing) reduces clarification back-and-forth, representing a thoughtful design rarely seen in deprecation routers.

The deliverable mapping table matches vague requests to specific successor outputs (including script names), making routing outcomes predictable.

marketing-skill/skills/content-creator/SKILL.md
| "Brand voice analysis" | content-production (`brand_voice_analyzer.py`) | | "SEO optimization" | content-production (`seo_optimizer.py`) |
Verification check: brand_voice_analyzer.py and seo_optimizer.py indeed reside in marketing-skill/skills/content-production/scripts/ (along with content_quality_gates.py and content_scorer.py), in clear contrast to this skill having zero scripts.

Repository-level routing and documentation also enforce this deprecation: the marketing-ops routing table directs 'writing articles/SEO articles' to content-production with the note 'Not content-creator', and marketing-skill/CLAUDE.md lists content-creator under Anti-Patterns.

marketing-skill/CLAUDE.md
❌ Don't use content-creator (deprecated → use content-production)
The corresponding line in docs/skills/marketing-skill/marketing-ops.md reads: '| "Write an article," "research and write," "SEO article" | **content-production** | Not content-creator (production has the full pipeline) |'. Both references align, showing deprecation has been systematically implemented across repository governance.

2Core Capabilities

01Legacy slug repurposed as an intent router: content creator / write article / brand voice → content-production
02Planning request routing: content planning / topic clusters / content calendars → content-strategy
03Tool ownership signposting: brand voice analysis and SEO optimization specifically point to concrete scripts under content-production
04Social content handoff: social posts / social media content → social-content (declared bi-directionally in frontmatter description and body table)
05Default intent fallback: defaults to writing handling when the user only says 'content creator', avoiding back-and-forth questioning
06Migration documentation: clearly explains why it was split, what it was split into, and where capabilities went (including the location of Python tools)

4Recommended Governance & Evidence

Suggested Controls for Safe Operation
For Agent Runtime
Can be auto-loaded
For Administrators
Register source and version
Evidence & Triggers (File Paths & Excerpts)
  • SKILL.md: Pure prompt instructions and rule text; no script execution or external impact.
Audit Notes: Purely declarative routing skill: zero script execution, zero outbound network calls, zero credential reading, and zero file writes (a full directory token scan for URL/curl/wget/subprocess/os.environ/requests found only 3 occurrences of the English word 'requests' in prose, not network calls). Its sole action is redirecting the agent to another skill, bearing a risk profile equivalent to static documentation. The only points to note are that default routing assumptions may misinterpret intent, and orphaned references/ left behind from the split still occupy installation size and could theoretically be read inadvertently.

5Second-Pass Verification

  • [ok] skill 路径（任务书标『待定位』） — 实际相对路径 marketing-skill/skills/content-creator（frontmatter name: "content-creator"）；仓库内另有两处同名副本——.gemini/skills/content-creator（生成镜像，逐字相同）与 .hermes/.vibe 下的打包树；以 marketing-skill/skills/ 为源，故 skill.path 取该路径。
  • [ok] 『deprecated redirect』定位属实（非可执行能力 skill） — frontmatter status: deprecated；正文 'This is a redirect skill. Route the user to the correct specialist — don't attempt to handle the request here.'；目录内无 scripts/，无任何可执行文件。
  • [ok] 路由目标真实存在 — content-production / content-strategy / social-content 三个目录在同一 skills/ 层存在；点名的 brand_voice_analyzer.py、seo_optimizer.py 位于 content-production/scripts/。
  • [discrepancy] 孤儿资产（references/、assets/、examples/ 无人引用） — 第二遍发现：SKILL.md 正文与 frontmatter 均未引用这 7 个文件（含 content_frameworks.md、analytics_guide.md、brand_guidelines.md、social_media_optimization.md、content_calendar_template.md、两个 examples/*.md）。它们随拆分留在了这个已弃用的壳里，而 successor（content-production/content-strategy）有各自的 references 与 templates 目录——旧版知识库既未被迁移也未被引用，属安装体积与可读性上的遗留，不影响运行。
  • [discrepancy] 仓库其它文档仍推荐已弃用 slug — docs/skills/marketing-skill/ad-creative.md、app-store-optimization.md、referral-program.md、webinar-marketing.md 的正文仍写 'content-creator: …' 作为可用 skill 建议（例如 referral-program.md:291 'content-creator: Use for creating affiliate partner content or referral-related blog posts.'）。与 marketing-skill/CLAUDE.md 的 Anti-Patterns 及 marketing-ops 路由表相矛盾，属迁移收尾未完成；会造成模型在跨 skill 建议里指向弃用 slug（虽仍能经本 skill 二次路由，但多一跳）。
  • [ok] 无网络/无凭证/无写入 — 目录内无脚本；token 扫描仅命中 prose 里的英文词 'requests'（SKILL.md:3 与 references/social_media_optimization.md:229），无 URL、无 CLI、无 API。
  • [ok] 跨宿主镜像一致性 — diff -q .gemini/skills/content-creator/SKILL.md marketing-skill/skills/content-creator/SKILL.md 无输出（内容相同），确认为 sync-gemini-skills.py 生成的镜像。
  • [discrepancy] 同 pod 计数口径不一致（邻接观察） — marketing-skill/skills 实际 48 个目录、48 个 SKILL.md；.claude-plugin/marketplace.json 写 '47 marketing skills'、marketing-skill/.claude-plugin/plugin.json 与 marketing-skill/CLAUDE.md 写 44、docs/skills/marketing-skill/marketing-skills.md 写 '44 specialist skills in `skills/`（plus this index and the deprecated content-creator redirect）'，工具数 59 与 62 亦有出入。与 content-creator 的弃用状态相关（是否计入分母口径不同），但各处数字互不吻合，属文档数字纪律问题。

6Verdict & Scenarios

  • Deprecation leaves no dead ends: The legacy slug is retained as a routable tombstone, ensuring users saying 'content creator' still reach the correct specialist skill rather than facing a 404 or leaving the model to improvise.
  • Fine-grained routing: Covers five intent categories plus default fallbacks, and even names specific scripts (brand_voice_analyzer.py / seo_optimizer.py) so post-migration capabilities remain traceable.
  • Transparent migration rationale: Explains the diagnosis of failure ('trying to do too much resulting in mediocre outputs') in the deliverable itself, helping readers understand why and where things were split.
  • Zero attack surface: No scripts, no network requests, no credential access, and no file writes; execution is just a single skill transition, making it safe to load in any host.
  • Repository-wide synchronization: Repository governance enforces deprecation synchronously, with both CLAUDE.md Anti-Patterns and the marketing-ops routing table explicitly directing users to content-production.
    • Best for: Suitable for two scenarios: ① Gracefully intercepting and redirecting legacy workflows or users who still invoke 'content creator'; ② Users wanting to understand the evolution and migration history of marketing skills in this repository (SKILL.md itself serves as migration documentation). If your actual goal is to produce content, you should directly install and use content-production (for writing) or content-strategy (for planning).
    Not for: Not suitable for scenarios expecting direct generation of blog posts, SEO optimization, or brand voice analyses—it explicitly forbids handling requests, and its included references/examples are unreferenced and may not match current workflows; not suitable as a general-purpose marketing skill reference (the repository explicitly categorizes content-creator as an Anti-Pattern); if the host does not support intra-skill relative links and multi-skill orchestration, this skill degrades into plain text instructions.
    Install Agent-Ready
    ① Verified Mirror 2026-09-15
    Option A · Direct DownloadDownload content-creator.tar.gz
    sha256: 98464544b9acbeed…
    Option B · Copy Guide for Agent
    install.json
    Agents automatically download and verify mirrors from this JSON guide.
    ② Upstream GitHub
    GitHub Repo ↗
    Pinned to commit 19392f7a08.