content-creator
Professional-grade brand voice analysis, SEO optimization, and platform-specific content frameworks.
36
33%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/content-creator/SKILL.mdQuality
Discovery
32%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 reads like a marketing tagline rather than a functional skill description. It uses buzzword-heavy language ('professional-grade', 'frameworks') without specifying concrete actions, and critically lacks any 'Use when...' guidance to help Claude know when to select this skill. The terms are somewhat relevant but too abstract to reliably distinguish this skill from other content or marketing-related skills.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about brand voice, SEO keywords, meta descriptions, social media copy, or content optimization.'
Replace abstract terms with concrete actions, e.g., 'Analyzes text samples to define brand voice guidelines, generates SEO-optimized titles and meta descriptions, adapts content for Twitter, LinkedIn, Instagram, and blog platforms.'
Remove the marketing qualifier 'Professional-grade' which adds no functional information and is considered fluff per the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a domain (content/marketing) and some actions ('brand voice analysis', 'SEO optimization', 'platform-specific content frameworks'), but these are somewhat abstract and buzzword-heavy rather than concrete actions like 'analyze brand tone from sample text' or 'generate meta descriptions'. | 2 / 3 |
Completeness | Provides a partial 'what' (analysis, optimization, frameworks) but completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also vague, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'brand voice', 'SEO', and 'content frameworks' that users might mention, but misses common natural variations like 'marketing copy', 'blog post', 'social media', 'keywords', 'tone of voice', or 'content strategy'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of brand voice, SEO, and platform-specific content provides some specificity, but 'SEO optimization' and 'content frameworks' are broad enough to overlap with general writing, marketing, or SEO-specific skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is overly verbose, spending many tokens on general content marketing knowledge that Claude already possesses (KPIs, common pitfalls, integration points). While the workflow structure is reasonable and references to external files are well-organized, the absence of any bundle files means the referenced scripts and guides don't exist, undermining actionability. The skill would benefit significantly from trimming generic advice and ensuring referenced resources actually exist.
Suggestions
Remove sections that teach Claude general knowledge it already has: Performance Metrics, Integration Points, Keywords list, Common Pitfalls, and Quality Indicators. These waste tokens on marketing fundamentals.
Provide the actual bundle files (scripts and reference docs) that are referenced throughout, or remove references to non-existent files and replace with inline executable guidance.
Add explicit validation checkpoints and feedback loops to workflows—e.g., after brand voice creation, specify what 'consistency' means concretely and how to verify it before proceeding.
Replace vague instructions like 'Research keywords for topic' with concrete actions Claude can actually perform (e.g., specific prompts, analysis techniques, or tool commands).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with significant padding. Sections like 'Performance Metrics', 'Integration Points', 'Keywords', and 'Common Pitfalls' explain general content marketing concepts Claude already knows. The 'When to Use' section is unnecessary. Much of this is generic marketing advice rather than skill-specific instruction. | 1 / 3 |
Actionability | References scripts like `brand_voice_analyzer.py` and `seo_optimizer.py` with usage examples, which is good. However, no bundle files are provided, so these scripts don't actually exist. The guidance is largely procedural checklists rather than executable instructions—e.g., 'Research keywords for topic' and 'Identify primary keyword (search volume 500-5000/month)' are vague directions, not concrete actions Claude can take. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced (numbered steps with sub-steps), but validation checkpoints are weak. The SEO workflow has an optimization check step, but there's no feedback loop for brand voice creation beyond 'refine based on results.' No explicit error recovery or validation gates before proceeding to next steps in most workflows. | 2 / 3 |
Progressive Disclosure | References to external files (references/brand_guidelines.md, references/content_frameworks.md, etc.) are well-signaled and one level deep, which is good structure. However, no bundle files are provided, meaning all references point to non-existent files. Additionally, the SKILL.md itself is monolithic with substantial content that could be split out (e.g., Performance Metrics, Best Practices sections). | 2 / 3 |
Total | 7 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
f5dc9e3
- 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.