Professional-grade brand voice analysis, SEO optimization, and platform-specific content frameworks.
46
33%
Does it follow best practices?
Impact
Pending
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 buzzwords ('professional-grade') without specifying concrete actions, and critically lacks any 'Use when...' guidance to help Claude select this skill appropriately. The domain is identifiable but the boundaries and triggers are too vague for reliable skill selection among many options.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about brand voice, tone guidelines, SEO keyword optimization, or adapting content for specific social media platforms.'
Replace 'professional-grade' (fluff) with concrete actions, e.g., 'Analyzes and defines brand voice guidelines, optimizes content for search engines, and adapts messaging for platforms like LinkedIn, Twitter, and Instagram.'
Include natural user trigger terms such as 'marketing copy', 'social media content', 'blog SEO', 'tone of voice', 'keyword optimization' to improve matching.
| 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 buzzwordy and not concrete enough to understand exactly what the skill does (e.g., does it write content? audit existing content? generate SEO keywords?). | 2 / 3 |
Completeness | Partially addresses 'what' but completely lacks a 'when' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is vague enough that this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'brand voice', 'SEO', and 'content frameworks' that users might mention, but misses common variations like 'marketing copy', 'blog post', 'social media', 'keyword research', 'tone of voice', or 'content strategy'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of brand voice, SEO, and platform-specific frameworks provides some distinctiveness, but terms like 'content frameworks' and 'SEO optimization' 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 suffers from significant verbosity, including many sections of generic marketing knowledge that Claude already possesses (performance metrics, common pitfalls, integration points). While it has some concrete elements like script usage commands and references to external files, much of the content is advisory rather than actionable. The skill would benefit greatly from aggressive trimming to focus only on the unique value it provides: the specific scripts, templates, and reference file navigation.
Suggestions
Remove generic marketing knowledge sections (Performance Metrics, Integration Points, Best Practices, Common Pitfalls) — Claude already knows these concepts and they consume significant token budget.
Remove the Keywords section entirely as it serves no functional purpose for Claude's execution.
Add explicit validation checkpoints to workflows, e.g., 'If SEO score < 75, review recommendations and re-run optimizer before proceeding.'
Consolidate the Quick Start and Core Workflows sections — they largely duplicate each other, and the Quick Start alone with proper detail would suffice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with significant padding. Sections like 'Performance Metrics', 'Integration Points', 'Common Pitfalls to Avoid', and 'Quality Indicators' contain generic marketing knowledge that Claude already knows. The keywords section is unnecessary filler. Much of the content reads like a marketing textbook rather than actionable instructions. | 1 / 3 |
Actionability | The skill references specific scripts (brand_voice_analyzer.py, seo_optimizer.py) with concrete CLI usage, which is good. However, much of the guidance is generic advice ('Research before writing', 'Write first draft without editing') rather than executable instructions. The scripts themselves aren't provided, and many steps are vague checklists rather than concrete actions. | 2 / 3 |
Workflow Clarity | Multi-step workflows are listed with numbered sequences, which is helpful. However, there are no validation checkpoints or feedback loops — for example, after running the SEO optimizer, there's no explicit 'if score < 75, iterate' step. The workflows describe what to do but lack error recovery or verification gates. | 2 / 3 |
Progressive Disclosure | The skill references external files (references/brand_guidelines.md, references/content_frameworks.md, references/social_media_optimization.md) which is good progressive disclosure. However, the main file itself is bloated with content that should either be in those reference files or omitted entirely (Performance Metrics, Integration Points, Best Practices sections). The overview is not concise enough to serve as a true entry point. | 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 | |
93c57b2
Table of Contents
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.