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 generic marketing knowledge (KPIs, best practices, common pitfalls) that Claude already knows, while the actionable core — script usage and workflows — is undermined by the absence of all referenced bundle files. The workflows are reasonably structured but lack validation checkpoints and error recovery loops. The skill would benefit significantly from trimming generic content and actually providing the referenced scripts and reference documents.

Suggestions

Remove generic marketing knowledge sections (Performance Metrics, Integration Points, Common Pitfalls, Quality Indicators, Keywords) — Claude already knows these concepts and they consume significant token budget.

Add validation checkpoints to workflows, e.g., 'If SEO score < 75, review keyword density and heading structure, then re-run optimizer' to create proper feedback loops.

Provide the referenced bundle files (scripts/brand_voice_analyzer.py, references/brand_guidelines.md, references/content_frameworks.md, references/social_media_optimization.md) or remove references to non-existent files.

Replace the nonsensical `grep -f references/brand_guidelines.md content.txt` command with an actual working approach for brand voice checking.

DimensionReasoningScore

Conciseness

Extremely verbose with significant padding. Sections like 'Performance Metrics', 'Integration Points', 'Keywords', and 'Common Pitfalls' explain general marketing concepts Claude already knows. The 'When to Use' section is unnecessary. Much of this content (KPIs, quality indicators, best practices) is generic marketing knowledge that wastes tokens without adding actionable, skill-specific value.

1 / 3

Actionability

References specific scripts with usage syntax and provides structured workflows, which is good. However, no bundle files are provided, so the referenced scripts (brand_voice_analyzer.py, seo_optimizer.py) and reference files (brand_guidelines.md, content_frameworks.md) don't actually exist. The grep command against a markdown file is nonsensical. Much guidance remains at the level of general advice rather than executable instructions.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with numbered steps, which is positive. 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 brand voice workflow mentions 'test consistency using analyzer' but doesn't specify what to do if consistency fails. Missing error recovery paths.

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, none of these files exist in the bundle, making all references dead links. Additionally, the SKILL.md itself is monolithic — sections like Performance Metrics, Integration Points, and Best Practices could be in separate reference files rather than inline.

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 buzzword-heavy language ('professional-grade', 'frameworks') without specifying concrete actions, and completely lacks a 'Use when...' clause to guide skill selection. The three capabilities mentioned are broad enough to overlap with multiple other skills.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks about brand voice, writing tone, SEO keywords, meta descriptions, or creating content for specific social platforms.'

Replace abstract terms with concrete actions, e.g., 'Analyzes and defines brand voice guidelines, optimizes content for search engines with keyword recommendations and meta tags, and adapts content for platforms like Twitter, LinkedIn, and Instagram.'

Remove the marketing qualifier 'Professional-grade' as it adds no functional information for skill selection.

DimensionReasoningScore

Specificity

Names the 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', 'generate meta descriptions', or 'create social media posts'.

2 / 3

Completeness

Provides a partial 'what' (brand voice analysis, SEO optimization, content frameworks) but completely lacks any 'when' clause or explicit trigger guidance. Per rubric guidelines, 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 natural variations like 'marketing copy', 'blog post', 'social media', 'keywords', 'content writing', or 'tone of voice'.

2 / 3

Distinctiveness Conflict Risk

Somewhat specific to marketing/content domain, but 'content frameworks' and 'SEO optimization' are broad enough to overlap with general writing skills, SEO-specific tools, or social media management skills. The combination of three loosely related areas increases conflict risk.

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.