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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/content-creator/SKILL.md

The canonical home for this skill is content-creator in sickn33/agentic-awesome-skills

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, spending many tokens on general content marketing knowledge that Claude already possesses (KPI lists, common pitfalls, integration points). The core value—specific scripts and reference file pointers—is buried under generic advice. The workflows are reasonably structured but lack validation checkpoints and error recovery steps.

Suggestions

Remove sections Claude already knows: Performance Metrics, Integration Points, Common Pitfalls, and Quality Indicators are generic marketing knowledge that waste tokens. Keep only project-specific configurations.

Add validation checkpoints to workflows: After running seo_optimizer.py, specify what to do if score is below threshold; after brand_voice_analyzer.py, specify how to interpret results and when to re-run.

Move Best Practices and detailed workflow descriptions to a separate reference file, keeping SKILL.md as a concise overview with quick-start commands and pointers to detailed guides.

Remove the Keywords section entirely—it serves no purpose in skill execution and wastes tokens.

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 skill instructions.

1 / 3

Actionability

References specific scripts (brand_voice_analyzer.py, seo_optimizer.py) with concrete CLI usage, which is good. However, much of the guidance is generic marketing advice ('Always start with audience need/pain point', 'Research before writing') rather than executable instructions. The scripts are referenced but we can't verify they exist or what they actually do beyond descriptions.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced (numbered steps with sub-steps), but validation checkpoints are weak. There's no explicit 'verify output before proceeding' step after running scripts, no error handling guidance, and no feedback loops for when SEO scores are below threshold or voice analysis shows inconsistency.

2 / 3

Progressive Disclosure

References external files well (references/brand_guidelines.md, references/content_frameworks.md, references/social_media_optimization.md, scripts/), but the SKILL.md itself is a monolithic wall of text that includes too much inline content that could be in reference files (Performance Metrics, Best Practices, Integration Points sections should be elsewhere).

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 names a marketing/content domain with a few relevant terms but reads more like a tagline than a functional skill description. It lacks concrete actions, explicit trigger guidance ('Use when...'), and natural user-facing keywords. The buzzword-heavy phrasing ('Professional-grade') adds fluff without aiding skill selection.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about brand voice, SEO content, social media copy, or platform-specific writing.'

Replace vague terms like 'professional-grade' and 'frameworks' with concrete actions, e.g., 'Analyzes brand tone, generates SEO-optimized headlines and meta descriptions, adapts content for Twitter, LinkedIn, and blog platforms.'

Include natural keyword variations users would say, such as 'marketing copy', 'blog post', 'social media content', 'keyword optimization', 'tone analysis'.

DimensionReasoningScore

Specificity

Names a domain (content/marketing) and some actions ('brand voice analysis', 'SEO optimization', 'platform-specific content frameworks'), but these are fairly high-level and lack concrete specifics about what operations are actually performed (e.g., 'generates meta descriptions', 'rewrites headlines for SEO').

2 / 3

Completeness

Provides a partial 'what' 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 enough to warrant a score of 1.

1 / 3

Trigger Term Quality

Includes some relevant keywords like 'brand voice', 'SEO optimization', and 'content frameworks' that users might mention, but misses common natural variations like 'blog post', 'social media', 'marketing copy', 'keyword research', 'tone of voice', or 'content strategy'.

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
administrakt0r/AI-Agents-Safe-Coding-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.