CtrlK
BlogDocsLog inGet started
Tessl Logo

content-marketer

Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing.

46

1.15x
Quality

20%

Does it follow best practices?

Impact

91%

1.15x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/content-marketer/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

7%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 reads as a persona/role description rather than an actionable skill file. It extensively lists capabilities, tools, and behavioral traits that Claude already understands, consuming significant token budget without providing any concrete, executable guidance. The content would benefit from being drastically reduced to a concise overview with specific templates, examples, and workflows linked from separate files.

Suggestions

Replace the extensive capability lists with 2-3 concrete, executable workflow templates (e.g., a specific blog post creation workflow with actual prompts, SEO checklist items, and output format examples)

Remove the 'Behavioral Traits', 'Knowledge Base', and 'Capabilities' catalog sections entirely—Claude already knows these concepts and they waste token budget

Add concrete examples with input/output pairs, such as a sample content brief template, an actual editorial calendar structure, or a specific SEO optimization checklist with measurable criteria

Move detailed guidance for each sub-domain (email marketing, social media, SEO, etc.) into separate referenced files and keep SKILL.md as a lean routing document

DimensionReasoningScore

Conciseness

Extremely verbose with extensive lists of capabilities, tools, behavioral traits, and knowledge areas that Claude already knows. The content reads like a job description or persona prompt rather than a skill file. Almost every section explains concepts Claude is already familiar with (e.g., what SEO is, what email marketing involves, what GA4 does).

1 / 3

Actionability

No concrete code, commands, templates, or executable guidance anywhere. The entire skill is abstract descriptions of capabilities and vague process steps like 'Analyze target audience' and 'Research competition' without any specific instructions on how to actually do these things. The 'Example Interactions' are just prompts, not worked examples with outputs.

1 / 3

Workflow Clarity

The 'Response Approach' section lists 10 high-level steps but they are generic and lack any validation checkpoints, specific tools/commands, or feedback loops. There is no clear workflow for any specific content marketing task—just abstract process descriptions that could apply to any marketing activity.

1 / 3

Progressive Disclosure

There is a single reference to 'resources/implementation-playbook.md' for detailed examples, which shows some awareness of progressive disclosure. However, the main file is a monolithic wall of text with 10+ capability sections that should be split into separate reference files. The structure exists (headers, sections) but the content is poorly organized for discovery.

2 / 3

Total

5

/

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 LinkedIn headline than a functional skill description. It relies heavily on marketing buzzwords ('elite,' 'AI-powered,' 'omnichannel,' 'data-driven') without specifying concrete actions the skill performs or when it should be selected. The absence of a 'Use when...' clause and the use of vague category labels rather than specific capabilities make it difficult for Claude to reliably choose this skill from a large pool.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms like 'blog post,' 'content calendar,' 'SEO keywords,' 'social media copy,' 'marketing strategy.'

Replace buzzword categories with concrete actions using third-person verbs, e.g., 'Creates blog posts, generates content calendars, performs keyword research, writes social media copy, analyzes content performance metrics.'

Remove subjective qualifiers like 'Elite' which add no functional information and reduce credibility of the description.

DimensionReasoningScore

Specificity

Names the domain (content marketing) and lists some areas like 'AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing,' but these are broad category labels rather than concrete actions. No specific verbs describing what the skill actually does (e.g., 'writes blog posts,' 'generates keyword reports').

2 / 3

Completeness

Describes a vague 'what' (specializing in various marketing areas) 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 weak enough to warrant a 1.

1 / 3

Trigger Term Quality

Includes some relevant keywords like 'content marketing,' 'SEO optimization,' and 'content creation' that users might mention, but uses buzzwordy phrases like 'omnichannel distribution' and 'data-driven performance marketing' that users are unlikely to naturally say. Missing common variations like 'blog posts,' 'social media content,' 'keyword research,' etc.

2 / 3

Distinctiveness Conflict Risk

The content marketing focus provides some specificity, but the broad scope covering SEO, content creation, distribution, and performance marketing could easily overlap with dedicated SEO skills, social media skills, or general writing 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.