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.
87
92%
Does it follow best practices?
Impact
82%
1.17xAverage score across 6 eval scenarios
Passed
No known issues
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 |
| Plan what content to create, topic clusters, calendar | content-strategy |
| Analyze brand voice | content-production (includes brand_voice_analyzer.py) |
| Optimize SEO for existing content | content-production (includes seo_optimizer.py) |
| Create social media content | social-content |
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:
| 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) |
This is a redirect skill. Route the user to the correct specialist — don't attempt to handle the request here.
967fe01
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.