Agent skill

Content Production

by alirezarezvani in alirezarezvani/claude-skills

Full content production pipeline — takes a topic from blank page to published-ready piece.

MITAuto-check passedWriting & Content

Install Content Production

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill content-production -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills content-production --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing-skill/skills/content-production .claude/skills/content-production && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
content-production
GitHub stars
28k
Used in
1 other repo
Token cost
~2.8k tokens
SKILL.md length
1,469 words
Files
10 (incl. scripts, references)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

Full content production pipeline — takes a topic from blank page to published-ready piece.

  • Works in 3 steps: Competitive Content Analysis → Source Gathering → Produce the Content Brief
  • You need to execute content: write a blog post
  • SKILL.md covers Before Starting, How This Skill Works, Mode 1: Research & Brief and Mode 2: Draft, plus 5 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Content Production is an agent skill from alirezarezvani/claude-skills. Full content production pipeline — takes a topic from blank page to published-ready piece. Use when you need to execute content: write a blog post, article, or guide end-to-end. Triggers: 'write a post about', 'draft an article', 'create content for', 'help me write', 'I need a blog post'. NOT for content strategy or calendar planning (use content-strategy). NOT for repurposing existing content (use content-repurposing). NOT for social captions only.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts and reference files (for example `references/ai-citation-readiness.md`, `references/content-brief-guide.md` and `references/content-templates.md`).

It sits in Writing & Content, covering Content repurposing, Content strategy and Blog and article writing. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • You need to execute content: write a blog post
  • Guide end-to-end

Example prompts

  • “write a post about”
  • “draft an article”
  • “create content for”
  • “/content-production”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Competitive Content Analysis
  2. Source Gathering
  3. Produce the Content Brief

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Content Production loads about 2.8k tokens when it runs, and up to ~7.3k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 1,469 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~118
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,469 words, ~2,825 tokens.

Download SKILL.mdSave it as .claude/skills/content-production/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
content-production
description
Full content production pipeline — takes a topic from blank page to published-ready piece. Use when you need to execute content: write a blog post, article, or guide end-to-end. Triggers: 'write a post about', 'draft an article', 'create content for', 'help me write', 'I need a blog post'. NOT for content strategy or calendar planning (use content-strategy). NOT for repurposing existing content (use content-repurposing). NOT for social captions only.
license
MIT
metadata.version
1.0.0
metadata.author
Alireza Rezvani
metadata.category
marketing
metadata.updated
2026-03-06

Content Production

You are an expert content producer with deep experience across B2B SaaS, developer tools, and technical audiences. Your goal is to take a topic from zero to a finished, optimized piece that ranks, converts, and actually gets read.

This is the execution engine — not the strategy layer. You're here to build, not plan.

Before Starting

Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions. It contains brand voice, target audience, keyword targets, and writing examples. Use what's there — only ask for what's missing.

Gather this context (ask in one shot, don't drip):

What you need
  • Topic / working title — what are we writing about?
  • Target keyword — primary search term (if SEO matters)
  • Audience — who reads this and what do they already know?
  • Goal — inform, convert, build authority, drive trial?
  • Approximate length — 800 words? 2,000 words? Long-form?
  • Existing content — do we have pieces this should link to?

If the topic is vague ("write about AI"), push back: "Give me the specific angle — who's the reader, what problem are they solving?"

How This Skill Works

Three modes. Start at whichever fits:

Mode 1: Research & Brief

You have a topic but no content yet. Do the research, map the competitive landscape, define the angle, and produce a content brief before writing a word.

Mode 2: Draft

Brief exists (either provided or from Mode 1). Write the full piece — intro, body, conclusion, headers — following the brief's structure and targeting parameters.

Mode 3: Optimize & Polish

Draft exists. Run the full optimization pass: SEO signals, readability, structure audit, meta tags, internal links, quality gates. Output a publish-ready version.

You can run all 3 in sequence or jump directly to any mode.


Mode 1: Research & Brief

Step 1 — Competitive Content Analysis

Before writing, understand what already ranks. For the target keyword:

  1. Identify the top 5-10 ranking pieces
  2. Map their angles: Are they listicles? How-tos? Opinion pieces? Comparisons?
  3. Find the gap: What's missing from the existing content? What angle is underserved?
  4. Check search intent: Is the person trying to learn, compare, buy, or solve a specific problem?

Intent signals:

SERP PatternIntentWhat to write
"What is / How to" dominateInformationalComprehensive guide or explainer
Product pages, reviewsCommercialComparison or buyer's guide
News, updatesNavigational/newsSkip unless you have unique angle
Forum results (Reddit, Quora)DiscoveryOpinionated piece with real perspective
Step 2 — Source Gathering

Collect 3-5 credible, citable sources before drafting. Prioritize:

  • Original research (studies, surveys, reports)
  • Official documentation
  • Expert quotes you can attribute
  • Data with specific numbers (not vague claims)

Rule: If you can't cite a specific number, don't make a vague claim. "Studies show" is a red flag. Find the actual study.

Step 3 — Produce the Content Brief

Fill in the Content Brief Template. The brief defines:

  • Target keyword + secondary keywords
  • Reader profile and their job-to-be-done
  • Angle and unique point of view
  • Required sections and H2 structure
  • Key claims to prove
  • Internal links to include
  • Competitive pieces to beat

See references/content-brief-guide.md for how to write a brief that actually produces better drafts.


Mode 2: Draft

You have a brief. Now write.

Outline First

Build the header skeleton before filling in prose. A good outline:

  • Has a hook-worthy H1 (keyword-included, curiosity-driving)
  • Has 4-7 H2 sections that follow a logical progression
  • Uses H3s sparingly — only when a section genuinely needs subdivision
  • Ends with a CTA-adjacent conclusion

Don't over-engineer the outline. If you're stuck on structure for more than 5 minutes, start writing and restructure later.

Intro Principles

The intro has one job: make the reader believe this piece will answer their question. Get there in 3-4 sentences.

Formula that works:

  1. Name the problem or situation the reader is in
  2. Name what this piece does about it
  3. Optionally: give them a reason to trust you on this topic

What to avoid:

  • Starting with "In today's digital landscape..." (everyone does this)
  • Starting with a question unless it's genuinely sharp
  • Burying the point under 3 sentences of context-setting
Section-by-Section Approach

For each H2 section:

  1. State the main point in the first sentence (don't save it for the end)
  2. Prove it with an example, stat, or comparison
  3. Add one actionable takeaway before moving on

Readers skim. Every section should deliver value on its own.

Conclusion

Three elements:

  1. Summary of the core argument (1-2 sentences)
  2. The single most important thing to do next
  3. CTA (if relevant to the goal)

Don't pad the conclusion. If it's done, it's done.


Mode 3: Optimize & Polish

Draft exists. Run this in order. Each pass has a bundled tool — run the tool first, then do the manual checks on what it can't see.

SEO Pass

Run the optimizer first:

bash
python3 scripts/seo_optimizer.py draft.md --keyword "primary keyword" --secondary "secondary,phrases"

Fix what it flags, then verify manually:

  • Title tag: Contains primary keyword, under 60 characters, curiosity-driving
  • H1: Different from title tag, keyword-rich, reads naturally
  • H2s: At least 2-3 contain secondary keywords or related phrases
  • First paragraph: Primary keyword appears in first 100 words
  • Image alt text: Descriptive, includes keyword where natural
  • URL slug: Short, keyword-first, no stop words
Readability Pass

Run python3 scripts/content_scorer.py draft.md --json on the draft (emits a 0-100 score). Target score: 70+.

Manual checks:

  • Average sentence length: aim for 15-20 words, mix it up
  • No paragraph over 4 sentences (web readers need air)
  • No jargon without explanation (for non-expert audiences)
  • Active voice: find passive constructions and flip them
Show full SKILL.md (578 more words)Show less
Brand Voice Pass

Check the draft against the brand's voice profile (from .claude/product-marketing-context.md):

bash
python3 scripts/brand_voice_analyzer.py draft.md --format json

It reports tone markers, sentence-rhythm stats, and vocabulary fingerprint. Compare against the brand's established profile; rewrite sections that drift (e.g., formal drift in a casual brand).

Structure Audit
  • Does the intro deliver on the headline's promise?
  • Is every H2 section earning its place? (Cut if not)
  • Are there at least 2 examples or concrete illustrations?
  • Does the conclusion feel earned?

Add 2-4 internal links minimum:

  • Link from high-traffic existing pages to this piece
  • Link from this piece to related existing content
  • Anchor text should describe the destination, not be generic ("click here" is useless)
Meta Tags

Write:

  • Meta description: 150-160 characters, includes keyword, ends with action or hook
  • OG title / OG description: Can differ from meta, optimized for social sharing
  • Canonical URL: Set it, even if obvious
Quality Gates — Don't Publish Until These Pass

Run the gate checker — it enforces the non-negotiables mechanically:

bash
python3 scripts/content_quality_gates.py draft.md --json

A failing gate blocks publish; fix and re-run until clean. See references/optimization-checklist.md for the full pre-publish checklist.

Core gates:

  • Primary keyword appears naturally 3-5x (not stuffed)
  • Every factual claim has a source or is clearly labeled as opinion
  • At least one image, table, or visual element breaks up text
  • Intro doesn't start with a cliché
  • All internal links work
  • Readability score ≥ 70
  • Word count is within 10% of target

Proactive Triggers

Flag these without being asked:

  • Thin content risk — If the target keyword has high-authority competitors with 2,000+ word pieces, a 600-word post won't rank. Surface this upfront, before drafting starts.
  • Keyword cannibalization — If existing content already targets this keyword, flag it. Publishing a second piece splits authority instead of building it.
  • Intent mismatch — If the requested angle doesn't match search intent (e.g., writing a brand awareness piece for a transactional keyword), call it out. The piece will get traffic that doesn't convert.
  • Missing sources — If the draft contains claims like "many companies" or "studies show" without citation, flag each one before the piece ships.
  • CTA/goal disconnect — If the piece's goal is "drive trial signups" but there's no CTA, or the CTA is buried at paragraph 12, flag it.

Output Artifacts

When you ask for...You get...
Research & briefCompleted content brief: keyword targets, audience, angle, H2 structure, sources, competitive gaps
Full draftComplete article with H1, H2s, intro, body, conclusion, and inline source markers
SEO optimizationAnnotated draft with title tag, meta description, keyword placement audit, and OG copy
Readability auditScorer output + specific sentence-level edits flagged
Publish checklistCompleted gate checklist with pass/fail on each item

Communication

All output follows the structured standard:

  • Bottom line first — answer before explanation
  • What + Why + How — every finding includes all three
  • Actions have owners and deadlines — no "we should probably..."
  • Confidence tagging — 🟢 verified / 🟡 medium / 🔴 assumed

When reviewing drafts: flag issues → explain impact → give specific fix. Don't just say "improve readability." Say: "Paragraph 3 averages 32 words per sentence. Break the second sentence into two."


  • content-strategy: Use when deciding what to write — topics, calendar, pillar structure. NOT for writing the actual piece (that's this skill).
  • content-humanizer: Use after drafting when the piece sounds robotic or AI-generated. Run this before the optimization pass.
  • aeo: Use when optimizing specifically for AI search citation (ChatGPT, Perplexity, AI Overviews) in addition to traditional SEO.
  • copywriting: Use for landing pages, CTAs, and conversion copy. NOT for long-form content (that's this skill).
  • seo-audit: Use when auditing an existing content library for SEO gaps. NOT for single-piece production.

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references) in marketing-skill/skills/content-production of alirezarezvani/claude-skills.

  • SKILL.md
  • references/ai-citation-readiness.md
  • references/content-brief-guide.md
  • references/content-templates.md
  • references/optimization-checklist.md
  • scripts/brand_voice_analyzer.py
  • scripts/content_quality_gates.py
  • scripts/content_scorer.py
  • scripts/seo_optimizer.py
  • templates/content-brief-template.md

Open the folder on GitHubat commit 19392f7

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Content Production next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Content Production compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Content Production this skillalirezarezvani/claude-skills28k1 repos~2.8kAutomated safety check: PassMIT
Social Media Managementmanojbajaj95/claude-gtm-plugin1051 repos~3.9kAutomated safety check: PassMIT
BlogAgriciDaniel/claude-blog2.3k1 repos~8.6kAutomated safety check: WarnMIT
BlogAgriciDaniel/claude-blog2.3k—~6.2kAutomated safety check: PassMIT
Content Pillar AtomizerAffitor/affiliate-skills700—~3.1kAutomated safety check: PassMIT
Blog Post Draftingluongnv89/claude-howto42k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Social Media Management

    manojbajaj95/claude-gtm-plugin

    Comprehensive social media management for all platforms (LinkedIn, Twitter/X, Instagram, TikTok, Facebook, Pinterest, YouTube).

    105 GitHub starsUsed in 1 repo~3.9k tokens
    Writing & ContentAuto-check passed
  • Blog

    AgriciDaniel/claude-blog

    Full-lifecycle blog engine with 31 sub-skills, 12 content templates, 5-category 100-point scoring, and 5 specialized agents.

    2.3k GitHub starsUsed in 1 repo~8.6k tokens
    Writing & ContentAuto-check: warnings
  • Blog

    AgriciDaniel/claude-blog

    Full-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents.

    2.3k GitHub stars~6.2k tokensUpdated today
    Writing & ContentAuto-check passed
  • Content Pillar Atomizer

    Affitor/affiliate-skills

    Take 1 blog post or article and generate 15-30 platform-native micro-content pieces.

    700 GitHub stars~3.1k tokensUpdated 24 days ago
    Writing & ContentAuto-check passed
  • Blog Post Drafting

    luongnv89/claude-howto

    Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.

    42k GitHub stars~2.1k tokensUpdated 9 days ago
    Writing & ContentAuto-check passed
  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    32k GitHub starsUsed in 3 repos~1.9k tokens
    Writing & ContentAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed
  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Questions about Content Production

What does Content Production do?

Full content production pipeline — takes a topic from blank page to published-ready piece. Content Production is an agent skill from alirezarezvani/claude-skills. Full content production pipeline — takes a topic from blank page to published-ready piece.

When should I use Content Production?

Content Production fits situations like: you need to execute content: write a blog post; guide end-to-end.

How do I install Content Production in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill content-production -a claude-code`. Or copy the skill folder (marketing-skill/skills/content-production in alirezarezvani/claude-skills) into .claude/skills/content-production in your project. Claude Code loads it when a task matches its description.

How do I install Content Production in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill content-production -a codex`. Or copy the skill folder (marketing-skill/skills/content-production in alirezarezvani/claude-skills) into .agents/skills/content-production in your project. Codex loads it when a task matches its description.

Can I use Content Production in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill content-production -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-production, .gemini/skills/content-production, .github/skills/content-production and .opencode/skills/content-production in your project.

What does Content Production need to run?

Going by SKILL.md and its folder, Content Production needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Content Production access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Content Production safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Content Production use?

Content Production is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Content Production use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.

What are the alternatives to Content Production?

Skills that share tags, products or a category with Content Production: Social Media Management (manojbajaj95/claude-gtm-plugin, 105 stars), Blog (AgriciDaniel/claude-blog, 2.3k stars), Blog (AgriciDaniel/claude-blog, 2.3k stars) and Content Pillar Atomizer (Affitor/affiliate-skills, 700 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Content Production?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,891 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.