content-creator
$
npx mdskill add alirezarezvani/claude-skills/content-creatorRoutes legacy content creator tasks to the correct specialist skill
- Solves the problem of ambiguous content creation requests by redirecting to appropriate skills
- Depends on content-production and content-strategy skills for execution
- Analyzes user intent based on request type and keywords
- Redirects users to the most relevant skill for their specific content needs
SKILL.md
.github/skills/content-creatorView on GitHub ↗
--- name: "content-creator" description: "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." license: MIT metadata: version: 2.0.0 author: Alireza Rezvani category: marketing updated: 2026-03-06 status: deprecated --- # Content Creator → Redirected > **This skill has been split into two specialist skills.** Use the one that matches your intent: | You want to... | Use this instead | |----------------|-----------------| | **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/) | ## 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. ## 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. ## Output Artifacts | When you ask for... | Routed to... | |---------------------|-------------| | "Write a blog post" | content-production | | "Content calendar" | content-strategy | | "Brand voice analysis" | content-production (`brand_voice_analyzer.py`) | | "SEO optimization" | content-production (`seo_optimizer.py`) | ## Communication This is a redirect skill. Route the user to the correct specialist — don't attempt to handle the request here. ## Related Skills - **content-production**: Full content execution pipeline (successor). - **content-strategy**: Content planning and topic selection (successor). - **content-humanizer**: Post-processing AI content to sound authentic. - **marketing-context**: Foundation context that both successors read.
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.