content-creator

Overview of content-creator skill

What content-creator is now

content-creator is a deprecated redirect skill in alirezarezvani/claude-skills, kept for legacy prompts that ask for “content creator” help. It does not directly write posts, build calendars, or run optimization scripts. Instead, the content-creator skill classifies the user’s marketing intent and routes the request to a more specific skill: content-production, content-strategy, or social-content.

Best fit for Content Marketing teams

This skill is useful if your workspace, agents, or saved prompts still refer to “content creator” as a broad Content Marketing capability. It helps prevent vague content requests from being handled by a one-size-fits-all workflow. Install it when you want a compatibility layer that turns broad requests like “write a guide,” “analyze our brand voice,” or “plan next month’s content” into the right specialist path.

What makes the skill different

The main differentiator is intent routing, not generation depth. The upstream SKILL.md explicitly explains that the old all-purpose content workflow was split because planning, writing, SEO, social content, and brand voice analysis need different execution rules. The repository still includes helpful supporting material, including a content calendar template and reference guides for analytics, brand voice, content frameworks, and social media optimization.

When this is not the right install

Do not install content-creator if you expect one skill to directly produce finished blog posts, run SEO analysis, or generate a complete editorial strategy. For direct writing and optimization, use content-production. For topic clusters, calendars, and planning, use content-strategy. For platform-specific posts, use social-content.

How to Use content-creator skill

content-creator install context

Install the skill from the repository path if your agent environment supports GitHub skill installation:

npx skills add alirezarezvani/claude-skills --skill content-creator

Because the skill is deprecated, treat the content-creator install as a routing shim. After installation, verify that the adjacent specialist skills are also available in your environment, especially content-production, content-strategy, and social-content. If they are not installed or discoverable, the redirect logic may identify the right destination but fail to complete the actual work.

Inputs that help the redirect work

The skill needs a clear task type more than a long brief. Include the desired output, content stage, audience, and channel. Weak prompt: “Help with content.” Stronger prompt: “Use content-creator to route this request: I need a 1,500-word SEO blog post for B2B SaaS buyers targeting ‘customer onboarding software,’ with a professional but practical tone.”

For planning, say so directly: “Use content-creator to route a content strategy request: create a four-week topic calendar for a cybersecurity startup targeting CISOs.” For social, name the platform: “Create LinkedIn and X posts from this blog outline.” This reduces the chance that a writing task is mistaken for strategy, or that social distribution is treated as long-form content.

Practical content-creator usage workflow

Start by reading SKILL.md; it contains the routing table and the reason the skill was split. Then inspect the support files based on your goal:

• assets/content_calendar_template.md for planning and publishing cadence
• references/content_frameworks.md for blog, email, video, and repurposing structures
• references/brand_guidelines.md for tone, personality, and style inputs
• references/analytics_guide.md for performance metrics and reporting
• references/social_media_optimization.md for platform-specific social guidance
• examples/brand_voice_analysis_example.md and examples/seo_optimization_example.md to understand expected specialist outputs

The examples mention tools such as brand_voice_analyzer.py and seo_optimizer.py, but those scripts are not part of this folder’s file tree. Use the examples as output-shape guidance, then rely on the specialist skill that actually owns the operation.

Prompt pattern for better routing

Use this compact structure:

Use content-creator to route this marketing request.

Goal: [write / plan / analyze / optimize / create social posts]
Asset: [blog post, article, guide, calendar, topic cluster, LinkedIn post]
Audience: [persona and market]
Channel: [blog, email, LinkedIn, X, Instagram, multi-channel]
Inputs: [draft, keywords, brand rules, campaign notes]
Success criteria: [SEO score, publish-ready draft, 4-week calendar, voice consistency]

This pattern makes content-creator usage predictable because the routing decision is based on intent, not on guessing from scattered context.

content-creator skill FAQ

Is content-creator still worth installing?

Yes, if you have legacy workflows or users who naturally ask for “content creator” instead of naming a specialist skill. It is less useful for new setups where users can directly call content-production, content-strategy, or social-content.

Does content-creator create final content?

No. The content-creator skill is explicitly a redirect skill. It can identify whether a request belongs to writing, strategy, brand voice, SEO, or social content, but the direct work should happen in the matching specialist skill.

How is this better than an ordinary prompt?

An ordinary prompt may mix strategy, drafting, SEO, and social repurposing in one response. content-creator reduces that ambiguity by enforcing a decision point first. That is valuable in team environments where repeatability matters more than improvisation.

Is content-creator beginner-friendly?

Yes, as a router. Beginners can say what they are trying to do in plain language, and the skill maps the request to the right content workflow. However, beginners should still provide audience, channel, keywords, and desired output format if they want high-quality results from the downstream specialist.

How to Improve content-creator skill

Improve content-creator results with clearer intent

The most common failure mode is an underspecified request. “Make content for our product” could mean a launch blog, a campaign calendar, a LinkedIn sequence, or an SEO refresh. Improve the result by naming the job: write, plan, analyze, optimize, or repurpose. Then add constraints such as word count, market, funnel stage, publication channel, and deadline.

Add source material before asking for output

For writing and brand voice, provide existing articles, brand guidelines, example copy, prohibited claims, and preferred tone attributes. For strategy, provide business goals, target segments, current content inventory, priority keywords, and campaign dates. For SEO, include the draft, primary keyword, secondary keywords, search intent, competitors, and internal links. These inputs let the routed specialist produce work that is closer to publishable.

Use repository references as checklists

The reference files are useful as quality gates even though content-creator itself redirects. Use brand_guidelines.md to define voice before drafting. Use content_frameworks.md to choose a structure before asking for a blog or email. Use analytics_guide.md to define how success will be measured. Use social_media_optimization.md when the output must be adapted to LinkedIn, X, Instagram, Facebook, or TikTok.

Iterate after the first routed answer

After the first response, do not simply ask “make it better.” Ask for a specific second pass: “tighten the introduction for search intent,” “convert this plan into the calendar template,” “adapt the post to a more authoritative brand voice,” or “turn this blog into five LinkedIn posts with platform-appropriate hooks.” content-creator works best when the initial routing is followed by focused revision in the specialist workflow.