CtrlK
BlogDocsLog inGet started
Tessl Logo

content-creator

Professional-grade brand voice analysis, SEO optimization, and platform-specific content frameworks.

36

Quality

33%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/content-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 it provides some concrete script commands and structured workflows, the referenced scripts and files don't exist in the bundle, undermining actionability. The content would benefit significantly from cutting 50-60% of the text and focusing only on what's unique and executable.

Suggestions

Remove sections Claude already knows: Performance Metrics, Integration Points, Common Pitfalls, Quality Indicators, and the Keywords block — these are generic marketing knowledge that waste tokens.

Provide the actual bundle files (scripts, references, assets) or remove references to them — currently all file paths are broken, making the workflows non-executable.

Add explicit validation checkpoints to workflows, e.g., 'If SEO score < 75, revise keyword placement and re-run optimizer before proceeding.'

Replace the nonsensical grep command with an actual validation step, and ensure all Quick Commands are functional and meaningful.

DimensionReasoningScore

Conciseness

Extremely verbose with significant padding. Sections like 'Performance Metrics', 'Integration Points', 'Common Pitfalls to Avoid', and 'Quality Indicators' explain general content marketing concepts Claude already knows. The keywords section is pure waste. Much of this reads like a content marketing textbook rather than actionable instructions for Claude.

1 / 3

Actionability

References specific scripts (brand_voice_analyzer.py, seo_optimizer.py) with concrete CLI usage, which is good. However, no bundle files are provided, so these scripts don't actually exist. Many instructions are vague marketing advice ('Research before writing', 'Identify primary keyword with search volume 500-5000/month') rather than executable steps Claude can perform. The grep command against brand_guidelines.md is nonsensical.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced (brand voice setup, blog creation, social media). However, there are no validation checkpoints or feedback loops — no step says 'verify the output before proceeding' or 'if the SEO score is below X, iterate.' The content calendar workflow lacks any verification. Steps reference files that don't exist in the bundle.

2 / 3

Progressive Disclosure

The skill references multiple external files (references/brand_guidelines.md, references/content_frameworks.md, references/social_media_optimization.md, scripts/, assets/) with clear navigation signals. However, no bundle files are provided, so all references are broken. The SKILL.md itself is monolithic — the Performance Metrics, Integration Points, and Best Practices sections bloat the main file when they could be separate or omitted entirely.

2 / 3

Total

7

/

12

Passed

Description

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', 'frameworks') without specifying concrete actions, and critically lacks any 'Use when...' guidance to help Claude know when to select this skill. The combination of three broad domains (brand voice, SEO, platform content) without specifics makes it both vague and potentially conflicting with other skills.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'brand voice', 'SEO', 'content calendar', 'social media post', 'blog optimization', 'tone analysis'.

Replace abstract terms like 'professional-grade frameworks' with concrete actions such as 'Analyzes writing samples to define brand tone, generates SEO-optimized titles and meta descriptions, adapts content for Twitter/LinkedIn/Instagram formats'.

Narrow the scope or clearly delineate the three sub-capabilities to reduce overlap risk with general writing or SEO-only skills.

DimensionReasoningScore

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' is also vague enough to warrant a 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', 'keywords', 'content strategy', or 'tone of voice'.

2 / 3

Distinctiveness Conflict Risk

Combines brand voice, SEO, and content frameworks which gives it 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

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
sickn33/antigravity-awesome-skills
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.