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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-creative-director/skills/content-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%Scale 1-3

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, containing substantial generic content marketing knowledge that Claude already possesses (metrics to track, common pitfalls, integration points). While the workflow structure is reasonable and script references provide some actionability, the lack of bundle files means none of the referenced scripts or guides can be verified. The skill would benefit greatly from aggressive trimming to focus only on the specific scripts, templates, and workflows that add novel value.

Suggestions

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

Add validation/feedback loops to workflows, e.g., 'If SEO score < 75, review recommendations and re-run optimizer until threshold is met.'

Provide the actual bundle files (scripts, reference guides) or include inline examples of their output so the skill is self-contained and verifiable.

Consolidate the Quick Start and Core Workflows sections — they largely duplicate each other, and merging them would significantly reduce length.

DimensionReasoningScore

Conciseness

Extremely verbose with significant padding. Sections like 'Performance Metrics', 'Integration Points', 'Common Pitfalls to Avoid', and 'Quality Indicators' contain generic marketing knowledge Claude already knows. The keywords section is pure waste. The content is roughly 3-4x longer than needed, with much of it being general content marketing advice rather than skill-specific instructions.

1 / 3

Actionability

References specific scripts (brand_voice_analyzer.py, seo_optimizer.py) with concrete CLI usage and provides structured workflows with numbered steps. However, no bundle files are provided, so the scripts and references are unverifiable. The actual content creation guidance is mostly generic advice (e.g., 'Research before writing', 'Write first draft without editing') rather than executable, copy-paste-ready instructions.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced (brand voice setup, blog creation, social media, calendar planning) with numbered steps. However, there are no validation checkpoints or feedback loops — for example, after running the SEO optimizer, there's no 'if score < 75, iterate' step. The workflows describe what to do but lack explicit verification gates.

2 / 3

Progressive Disclosure

References to external files (references/brand_guidelines.md, references/content_frameworks.md, references/social_media_optimization.md, scripts/) are well-signaled and one level deep. However, no bundle files are provided, so all references are unverifiable. Additionally, significant content that could be in reference files (Performance Metrics, Best Practices, Integration Points) is inlined, bloating the main skill file.

2 / 3

Total

7

/

12

Passed

Description

32%Scale 1-3

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 more like a marketing tagline than a functional skill description. It uses buzzword-heavy language ('professional-grade', 'frameworks') without specifying concrete actions, and critically lacks any 'Use when...' clause to guide skill selection. The three listed areas provide some domain specificity but remain too abstract to reliably distinguish this skill from other content or marketing-related skills.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about brand voice, tone analysis, SEO keywords, meta descriptions, or adapting content for specific social media platforms.'

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

Remove the marketing qualifier 'professional-grade' which adds no functional information and is considered fluff per the rubric.

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 actionable tasks like 'analyze brand tone from sample text' or 'generate meta descriptions'.

2 / 3

Completeness

Provides a partial 'what' but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, which per the rubric should cap completeness at 2, and the 'what' itself is 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 natural variations like 'marketing copy', 'blog post', 'social media', 'keywords', 'tone of voice', or 'content strategy'.

2 / 3

Distinctiveness Conflict Risk

Combines three somewhat distinct areas (brand voice, SEO, platform content) which gives it some identity, but terms like 'content frameworks' and 'optimization' are generic 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.

Validation — 10 / 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
popey/claude-code-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.