content-creator

Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing/SEO/brand-voice tasks or content-strategy for planning tasks.

1.17x

Quality

71%

Does it follow best practices?

Impact

82%

1.17x

Average score across 6 eval scenarios

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./marketing-skill/skills/content-creator/SKILL.md

Quality

Content

66%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 skill body is a concise, well-structured redirect map that clearly tells Claude where to route each intent. Its weakness is progressive disclosure: the included reference/asset files are not surfaced or navigated from the body, and the assets are largely unrelated to a pure redirect skill.

Suggestions

Add a short section that explicitly references the relevant bundle files (e.g. content_calendar_template.md for content-strategy routing, brand_guidelines.md and content_frameworks.md for content-production) so the present references are discoverable and one level deep.

Remove or repurpose bundle files that are irrelevant to a deprecated redirect skill (e.g. analytics_guide.md, social_media_optimization.md) to align the bundle with the skill's actual purpose.

Specify the concrete handoff action (e.g. 'load the named specialist skill and continue the user's request there') so the routing workflow is fully executable rather than implied.

Dimension	Reasoning	Score
Conciseness	The body is lean, table-driven, and free of padding or explanations of concepts Claude already knows; only minor redundancy (the routing table and the Output Artifacts table repeat similar mappings) keeps it from a 5.	4 / 5
Actionability	It gives concrete, executable routing directives (explicit relative links to each specialist and named tool files like brand_voice_analyzer.py) that Claude can follow immediately, with only minor gaps such as not specifying exactly how to hand off the request.	4 / 5
Workflow Clarity	The single routing action is unambiguous with a clear mapping table and explicit 'Proactive Triggers', and the simple-skill exception applies; it is not a 5 only because the actual handoff step is implied rather than spelled out.	4 / 5
Progressive Disclosure	The body references sibling skills and tool files (brand_voice_analyzer.py, seo_optimizer.py) that live outside this bundle, while the present references/, scripts/, and assets/ files (analytics_guide.md, brand_guidelines.md, content_frameworks.md, social_media_optimization.md, content_calendar_template.md) are never referenced from the body, so navigation to the bundle is poor.	2 / 5
	Total	14 / 20 Passed

Description

76%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.

The description is specific, third-person, and explicitly covers both what the skill does and when to use it, with strong natural trigger phrases. Its main weakness is that it describes a deprecated router whose broad trigger list overlaps with the successor skills it points to.

Suggestions

Tighten the trigger list to only the legacy 'content creator' invocation plus a single example per intent, since routing breadth increases conflict risk with the successor skills.

Lead the description with the deprecation/routing intent and drop redundant clause restatements to reduce verbosity while preserving the 'when' guidance.

Clarify that Claude should not self-select this skill for new work but only when the user explicitly invokes the legacy name, sharpening distinctiveness.

Dimension	Reasoning	Score
Specificity	Names concrete routing actions ('routes to content-production for writing/SEO/brand-voice tasks', 'routes to content-strategy for planning tasks') and lists specific request types, though the actions are routing rather than a broad suite of capabilities, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (a redirect skill that identifies intent and routes to specialists) and 'when' ('Use when a user invokes content creator...'), but the deprecated/redirect nature adds slight ambiguity about whether Claude should still select it.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('write a blog post, article, guide', 'brand voice analysis', 'content calendar', 'topic cluster') with good synonym coverage; a few natural variants are absent so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche as a deprecated router with explicit destinations, though the broad trigger list (writing, planning, SEO, brand voice) creates minor overlap risk with the very specialists it routes to.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 5 suspicious	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: marketing-skill/skills/content-creator/SKILL.md
Commit: 19392f7

Reviewed: 31 minutes 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.