CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-creator

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

Quality

67%

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

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, genuinely actionable skill body: concrete commands, numeric guidance, clear per-workflow sequencing, and clean one-level-deep disclosure into real reference/script/asset files. Its weaknesses are ~25% of the body restating generic marketing knowledge Claude already has, internal duplication between Quick Start and Core Workflows, and one broken grep command.

Suggestions

Remove or relocate the generic "Performance Metrics", "Integration Points", and "Content Creation Process" sections — they restate knowledge Claude already has and inflate the token cost of loading the skill.

Fix or delete "grep -f references/brand_guidelines.md content.txt": grep -f treats each line of the file as a literal pattern, which fails against a prose guidelines document.

Deduplicate Quick Start against Core Workflows — the brand-voice and blog paths repeat the same steps twice; keep Quick Start as one-line pointers into the detailed workflows.

DimensionReasoningScore

Conciseness

The workflow sections are tight and specific ("Adjust keyword density to 1-3%", "Follow 40/25/25/10 content pillar ratio"), but "Performance Metrics", "Integration Points", and the 9-step "Content Creation Process" restate marketing knowledge Claude already has, and Quick Start largely duplicates Core Workflows. Mostly efficient with some unnecessary explanation — anchor 3; not anchor 2 because padding is a minority of the body and the core guidance is lean.

3 / 5

Actionability

Commands are copy-paste ready ("python scripts/seo_optimizer.py blog_post.md \"primary keyword\" \"secondary,keywords,list\"", "cp assets/content_calendar_template.md this_month_calendar.md") with concrete parameters (500-5000/month search volume, 1,500-2,500 words). One command is broken: "grep -f references/brand_guidelines.md content.txt" uses -f (one pattern per line) against a prose document, so it will not work as intended — a minor gap placing this at anchor 4 rather than 5.

4 / 5

Workflow Clarity

All four workflows are clearly numbered with a script-based feedback loop ("Run scripts/seo_optimizer.py ... Apply recommendations", "Test consistency using analyzer / Refine based on results") plus optimization checklists. It stops short of anchor 5 because there is no explicit gate (e.g. "only proceed when SEO score > 75") and the SEO loop lacks a re-check after applying fixes.

4 / 5

Progressive Disclosure

The body is an overview that points to all six bundle files by real, verified paths, includes a dedicated "When to Use Each Reference" section, and the references are exactly one level deep (bundle files contain no further references). Not anchor 5 because generic content (Performance Metrics, Best Practices) is inlined in SKILL.md rather than split into the reference files.

4 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 coherent niche (brand voice, SEO, content frameworks) but reads as a capability list rather than a trigger-ready description: no 'Use when...' guidance, a buzzword lead ("Professional-grade"), and missing the natural trigger terms (blog posts, social media, marketing copy) the body itself lists under Keywords.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing blog posts, creating social media content, establishing brand voice, optimizing content for SEO, or planning content calendars."

Replace the buzzword lead "Professional-grade" with concrete verbs describing what the skill actually does (analyzes voice, optimizes posts, applies templates).

Include the natural synonyms users would say — "blog posts", "social media", "content calendar", "marketing copy" — so the description, not just the body's Keywords section, carries them.

DimensionReasoningScore

Specificity

"brand voice analysis, SEO optimization" names the domain with a couple of action-like phrases, but they are nominal and generic — no concrete operations like 'analyze', 'rewrite', or 'generate' are spelled out. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") and falls short of anchor 4 because it does not list several specific concrete actions.

3 / 5

Completeness

The 'what' is stated ("brand voice analysis, SEO optimization, and platform-specific content frameworks") but there is no 'Use when...' clause or any equivalent trigger guidance — the judging guidelines explicitly cap completeness at 3 in that case. Matches anchor 3 ("clear 'what' but 'when' is missing").

3 / 5

Trigger Term Quality

Terms "brand voice", "SEO", and "content" are natural user phrases, but common variations users would actually say ("blog posts", "social media", "marketing copy", "content calendar") are absent, and "platform-specific content frameworks" is jargon no user would utter. Fits anchor 3 ("Some relevant keywords but missing common variations or synonyms"); not anchor 4 because keyword coverage is too thin.

3 / 5

Distinctiveness Conflict Risk

The marketing/content niche signaled by "brand voice analysis, SEO optimization" is mostly distinct with only minor overlap risk against generic writing/copywriting skills — anchor 4. Not anchor 5 because "content" and "SEO" are broad enough to collide with general writing skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/content-creator/SKILL.md

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.