CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

64

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A well-structured, highly actionable skill body with a clear three-mode workflow, executable script commands, and genuine validation feedback loops in the optimization mode. Its main defect is bundle hygiene: a broken template path and two orphaned reference files that are surfaced nowhere in the skill.

Suggestions

Fix or remove the broken reference at line 83 — templates/content-brief-template.md does not exist in the bundle; either add the template file or point to references/content-templates.md.

Surface the two orphaned reference files: content-templates.md (12 templates with selection logic) belongs in Mode 2's outline/drafting guidance, and ai-citation-readiness.md should be linked from the SEO pass or the related 'aeo' skill section.

Trim motivational asides ('If it's done, it's done', the 5-minute stuck rule) to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and threshold-driven ('under 60 characters', '150-160 characters', 'score 70+', '15-20 words', 'no paragraph over 4 sentences') with almost no explanation of concepts Claude already knows. It is not a 5 because of minor editorial padding ('Readers skim. Every section should deliver value on its own.', 'If it's done, it's done.') and the 5-minute rule anecdote that could be trimmed.

4 / 5

Actionability

Guidance is mostly copy-paste executable: four concrete script invocations with flags (`python3 scripts/seo_optimizer.py draft.md --keyword ... --secondary ...`), an explicit intro formula, per-section writing rules, and a gate checklist. It is not a 5 because Mode 1 Step 3 instructs 'Fill in the [Content Brief Template](templates/content-brief-template.md)' — a path that does not exist in the bundle, so that step cannot be executed as written.

4 / 5

Workflow Clarity

Three modes are clearly defined with entry conditions ('You have a topic but no content yet', 'Brief exists', 'Draft exists') and permission to sequence or jump. Mode 3 runs ordered passes with explicit validation and a feedback loop ('A failing gate blocks publish; fix and re-run until clean') plus a checklist, matching the top anchor. Not destructive or batch, so no cap applies.

5 / 5

Progressive Disclosure

The body is well-sectioned and the two references it does use are clearly signaled ([references/content-brief-guide.md] for brief-writing, [references/optimization-checklist.md] for the pre-publish checklist). However, scored against the actual bundle: the linked templates/content-brief-template.md does not exist, and two of the four reference files (ai-citation-readiness.md, content-templates.md) are never mentioned from the body, so navigation to half the bundle is missing — better than anchor 2 but below the 'minor organization gaps' of anchor 4.

3 / 5

Total

16

/

20

Passed

Description

78%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 description with explicit what/when structure, concrete trigger phrases, and well-drawn NOT-for boundaries against sibling skills. The main gaps are a somewhat abstract 'pipeline' framing that hides the research/draft/optimize actions and one over-broad trigger term.

Suggestions

Enumerate the pipeline stages as concrete actions, e.g. 'researches the competitive landscape, produces a content brief, drafts the piece, and runs SEO/readability/quality-gate optimization' instead of the abstract 'full content production pipeline'.

Tighten the 'help me write' trigger to 'help me write a post/article' so it does not collide with copywriting or social-caption requests.

DimensionReasoningScore

Specificity

The description names the domain ('Full content production pipeline') and one concrete action ('write a blog post, article, or guide end-to-end'), but the pipeline stages (research, draft, optimize) are only implied by 'takes a topic from blank page to published-ready piece' rather than explicitly stated as actions. It matches the anchor for naming the domain with 1-2 concrete actions, not the several-specific-actions anchor.

3 / 5

Completeness

It explicitly answers both questions: what ('takes a topic from blank page to published-ready piece... write a blog post, article, or guide end-to-end') and when ('Use when you need to execute content' plus a concrete Triggers list of user phrases). This matches the top anchor with concrete trigger phrases, mirroring the good example structure.

5 / 5

Trigger Term Quality

Five natural user phrases are explicitly listed ('write a post about', 'draft an article', 'create content for', 'help me write', 'I need a blog post'), giving good keyword coverage. Falls short of comprehensive because 'help me write' is generic enough to over-trigger and variations like 'produce content' or 'write a guide' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (end-to-end content execution) reinforced by three explicit NOT-for clauses routing to content-strategy, content-repurposing, and social captions. Not a 5 because the 'help me write' trigger is broad enough to overlap with adjacent skills like copywriting when the request is, e.g., 'help me write a landing page'.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

marketing-skill/skills/content-production/SKILL.md

Reviewed

Table of Contents

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.