content-creator · alirezarezvani — Claude Code skill: what it does, how to install
A deprecated skill routes legacy content requests to the right specialist. Use it when older prompts still invoke “content creator”.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install marketing-skills@claude-code-skillsWhat content-creator does
content-creator does not write content or build a plan itself. It identifies the request and routes blog posts, guides, SEO work, and brand voice analysis to content-production. Topic clusters, content calendars, and other planning requests go to content-strategy, while social media content goes to social-content.
The skill acts as a compatibility layer for the legacy “content creator” invocation. The source points to brand_voice_analyzer.py and seo_optimizer.py within content-production for brand voice and SEO tasks. Install it when an existing workflow still uses the old trigger; choose a specialist skill when you want the task handled directly.
What it helps with
- route article requests to content-production
- separate content planning from content writing
- send brand voice analysis to the right skill
- handle a legacy “content creator” invocation
Example prompts for the agent
- Write a blog post about `topic`
- Create a content calendar for `product`
- Analyze the brand voice of `content.md`
How to install content-creator
1Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install marketing-skills@claude-code-skillsThis installs the whole marketing-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add alirezarezvani/claude-skills --skill content-creator -a claude-code3Manually: put the files in place
~/.claude/skills/content-creator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/content-creator/
Manually: put the files in place
.agents/skills/content-creator/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/content-creator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alirezarezvani/claude-skills content-creator2Manually: put the files in place
.github/skills/content-creator/SKILL.mdPlatform CLI
gemini skills install https://github.com/alirezarezvani/claude-skills --path marketing-skill/skills/content-creatorManually: put the files in place
.devin/skills/content-creator/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set349
The whole set →Other versions of content-creator
Similar
Questions about content-creator
How do I install content-creator in Claude Code?
Add the marketplace with /plugin marketplace add alirezarezvani/claude-skills, then install the package using /plugin install marketing-skills@claude-code-skills.
What does content-creator do?
It is a deprecated redirect skill. It identifies the content request and sends it to content-production, content-strategy, or social-content.
Where does it route an SEO optimization request?
It routes the request to content-production, which includes seo_optimizer.py for this task.
Source text
SKILL.md · MIT
--- 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.
© Alireza Rezvani · MIT · alirezarezvani/claude-skills