Content Creator
Resolve legacy “content creator” invocations by routing write/SEO tasks to content-production and planning/calendar tasks to content-strategy.
Overview
Content Creator is an agent skill most often used in Grow (also Launch for SEO-oriented writing routes) that redirects legacy requests to content-production or content-strategy instead of handling work itself.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill content-creatorWhat is this skill?
- Deprecated v2.0.0 meta-skill—does not generate content directly
- Intent table: write/brand voice/SEO → content-production; plan/clusters/calendar → content-strategy
- Social posts explicitly routed to social-content
- Documents why the monolithic skill was split for clearer agent handoffs
- MIT-licensed redirect stub in Alireza Rezvani marketing skill pack
- Split into two specialist skills (content-production and content-strategy) in v2.0.0
- Redirect routing table covers write, plan, brand voice, SEO, and social paths
Adoption & trust: 786 installs on skills.sh; 17.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You invoked an outdated “content creator” skill and the agent does not know whether you want drafting, SEO, or editorial planning.
Who is it for?
Workflows, prompts, or team docs that still say “content creator” and need a safe routing layer during migration.
Skip if: New projects that should call content-production, content-strategy, or social-content directly without an extra redirect hop.
When should I use this skill?
User invokes 'content creator', asks for blog/article/guide/brand voice (→ production), or content plan/cluster/calendar (→ strategy).
What do I get? / Deliverables
The agent classifies intent and hands off to content-production, content-strategy, or social-content so the right specialist runs next.
- Clear redirect to the correct specialist skill name
- No standalone article or calendar output from this skill
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow/content because both downstream skills serve audience and organic growth, even though writing also touches Launch SEO. Content subphase fits a router whose only job is to pick the right growth content specialist—not to produce copy itself.
Where it fits
User asks for a quarterly content calendar and gets routed to content-strategy instead of a generic writer.
User wants a long-form guide drafted and SEO-checked via content-production’s optimizer tools.
User asks to optimize existing landing copy and lands on content-production, not planning skills.
User requests social posts and is sent to social-content rather than blog workflows.
How it compares
Meta routing skill—not a replacement for content-production or content-strategy deliverables.
Common Questions / FAQ
Who is content-creator for?
Builders and agents still wired to the deprecated content-creator slug who need automatic routing to the split marketing skills.
When should I use content-creator?
In Grow when planning clusters or calendars (→ content-strategy), when drafting or optimizing posts (→ content-production), or when legacy triggers say “content creator”; use social-content for social-only asks.
Is content-creator safe to install?
Check the Security Audits panel on this Prism page; the skill only redirects and does not run external scripts itself.
Workflow Chain
Then invoke: content production, content strategy
SKILL.md
READMESKILL.md - Content Creator
# 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. # Content Calendar Template - [Month Year] ## Monthly Goals - **Traffic Goal**: - **Lead Generation Goal**: - **Engagement Goal**: - **Key Campaign**: ## Week 1: [Date Range] ### Monday [Date] **Platform**: Blog **Topic**: **Keywords**: **Status**: [ ] Planned [ ] Written [ ] Reviewed [ ] Published **Owner**: **Notes**: **Platform**: LinkedIn **Type**: Article Share **Caption**: **Hashtags**: **Time**: 10:00 AM ### Tuesday [Date] **Platform**: Instagram **Type**: Carousel **Topic**: **Visuals**: [ ] Created [ ] Approved **Caption**: **Hashtags**: **Time**: 12:00 PM ### Wednesday [Date] **Platform**: Email Newsletter **Subject Line**: **Segment**: **CTA**: **Status**: [ ] Drafted [ ] Designed [ ] Scheduled ### Thursday [Date] **Platform**: Twitter/X **Type**: Thread **Topic**: **Thread Length**: **Media**: [ ] Images [ ] GIFs [ ] None **Time**: 2:00 PM ### Friday [Date] **Platform**: Multi-channel **Campaign**: **Assets Needed**: - [ ] Blog post - [ ] Social graphics - [ ] Email - [ ] Video ## Week 2: [Date Range] [Repeat structure] ## Week 3: [Date Range] [Repeat structure] ## Week 4: [Date Range] [Rep