Name: content-production
Rating: 69.6 (1 reviews)
Author: alirezarezvani

content-production

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is content-production in alirezarezvani/claude-skills

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced, actionable production playbook with strong workflow clarity and a real validation feedback loop. Its main weakness is progressive disclosure: the skill points to numerous scripts, templates, and reference files that are not actually bundled, so the disclosure structure is signaled but unfulfilled.

Suggestions

Bundle the referenced files the body depends on — at minimum scripts/seo_optimizer.py, scripts/content_scorer.py, scripts/brand_voice_analyzer.py, scripts/content_quality_gates.py, templates/content-brief-template.md, references/content-brief-guide.md, and references/optimization-checklist.md — or remove the invocations and inline the essential checks so no command points at a missing file.

Trim the opening persona line ('You are an expert content producer with deep experience across B2B SaaS, developer tools, and technical audiences.') and a few motivational asides; the directive guidance already carries the intent without them.

Tighten qualitative checks like 'Does the conclusion feel earned?' into concrete, testable criteria so every manual check is as actionable as the numeric ones.

Dimension	Reasoning	Score
Conciseness	Mostly lean and directive ('Don't pad the conclusion. If it's done, it's done.'), with minimal explaining of concepts Claude already knows, but it opens with a persona preamble ('You are an expert content producer with deep experience...') and a few motivational asides that could be trimmed.	4 / 5
Actionability	Provides concrete commands with arguments and specific numeric targets ('python3 scripts/seo_optimizer.py draft.md --keyword ...', meta description 150-160 chars, sentence length 15-20 words, readability ≥ 70), but some checks are qualitative ('Does the conclusion feel earned?') and the referenced tool scripts are not bundled with the skill.	4 / 5
Workflow Clarity	Three modes are clearly sequenced, Mode 3 runs an ordered pass sequence (SEO → Readability → Brand Voice → Structure → Links → Meta → Quality Gates), and the quality-gate step includes an explicit feedback loop ('A failing gate blocks publish; fix and re-run until clean') with concrete validation thresholds.	5 / 5
Progressive Disclosure	In-document structure is well organized and references are clearly signaled via markdown links, but every referenced bundle path (scripts/*.py, templates/content-brief-template.md, references/content-brief-guide.md, references/optimization-checklist.md, .claude/product-marketing-context.md) is absent from disk, so the one-level-deep references resolve to dead ends rather than actual supporting material.	3 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states what the skill does, when to use it via natural trigger phrases, and where its boundaries lie relative to related skills. The only mild weakness is that the concrete production actions are described at a summary level rather than enumerated comprehensively.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('write a blog post, article, or guide end-to-end', 'takes a topic from blank page to published-ready piece'), but the production stages (research, brief, draft, optimize) are only abstractly implied rather than enumerated, so it stops short of comprehensive coverage.	4 / 5
Completeness	Explicitly answers both what ('Full content production pipeline — takes a topic from blank page to published-ready piece') and when ('Use when you need to execute content... Triggers: ...') with concrete trigger phrases and negative-boundary guidance.	5 / 5
Trigger Term Quality	Lists comprehensive, natural trigger phrases users would actually say — 'write a post about', 'draft an article', 'create content for', 'help me write', 'I need a blog post' — including synonyms and phrasings across the intent space.	5 / 5
Distinctiveness Conflict Risk	Clear niche with explicit NOT-for clauses distinguishing it from content-strategy, content-repurposing, and social-caption-only work, minimizing trigger overlap with sibling skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing	Warning
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	14 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/content-production/SKILL.md
Commit: 19392f7

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.