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.
87
92%
Does it follow best practices?
Impact
82%
1.17xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description that clearly communicates its role as a routing/redirect skill for legacy requests. It excels at listing specific trigger terms users would naturally say, explicitly defines both what it does and when to use it, and clearly distinguishes itself from the downstream skills it routes to. The description is thorough without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: routing legacy 'content creator' requests, identifying user intent, redirecting to content-production for writing/SEO/brand-voice tasks, and redirecting to content-strategy for planning tasks. Also specifies what it does NOT do (handle requests directly). | 3 / 3 |
Completeness | Clearly answers both 'what' (a redirect skill that routes requests to specialist skills) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like invoking 'content creator', asking to write blog posts, or planning content). Also clarifies routing destinations. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'content creator', 'blog post', 'article', 'guide', 'brand voice analysis', 'plan content', 'topic cluster', 'content calendar'. These are all terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche as a deprecated redirect/routing skill. Clearly differentiates itself from the actual content-production and content-strategy skills by stating it 'does not handle requests directly' and only redirects. The legacy/deprecated framing further reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured redirect skill that clearly maps user intents to successor skills. Its main weakness is some redundancy — the routing table, proactive triggers, and output artifacts sections all convey overlapping information, and the 'Why the Change' section provides rationale that Claude doesn't need. The core routing logic is excellent and immediately actionable.
Suggestions
Remove the 'Why the Change' section — Claude doesn't need to know the historical rationale for the skill split.
Consolidate the 'Proactive Triggers' and 'Output Artifacts' sections into the main routing table to eliminate redundancy and save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections. The 'Why the Change' section explains rationale Claude doesn't need, and the 'Output Artifacts' table largely duplicates the routing table at the top. The 'Proactive Triggers' section also overlaps with the main table. | 2 / 3 |
Actionability | For a redirect skill, actionability means clearly mapping user intent to the correct destination. The routing table is concrete and specific, with clear intent-to-skill mappings and even references to specific Python tools. This is as actionable as a redirect skill can be. | 3 / 3 |
Workflow Clarity | This is a simple single-purpose skill (redirect/routing) with an unambiguous single action: identify intent and route. The routing logic is clearly presented in a table format with no multi-step process needed. The 'Communication' section explicitly states not to handle requests here. | 3 / 3 |
Progressive Disclosure | The skill is well-organized with clear navigation. It uses relative links to point to the correct specialist skills one level deep. The table format makes discovery easy, and the Related Skills section provides additional context without nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- alirezarezvani/claude-skills
- Commit
f567c61
- 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.