content-marketer

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

Quality

16%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/content-marketer/SKILL.md

Quality

Content

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

This skill is essentially a persona description masquerading as actionable instructions. It exhaustively lists capabilities, tools, and behavioral traits that Claude already knows, without providing any concrete templates, code, commands, or specific workflows. The content would need a fundamental restructuring to become a useful skill—replacing abstract capability lists with specific, actionable playbooks and examples.

Suggestions

Replace the extensive capability lists with 2-3 concrete, actionable workflow templates (e.g., a specific content brief template, an SEO optimization checklist with exact steps, or an email sequence structure with example copy).

Add concrete output formats and examples—show what a completed content strategy document looks like, what an optimized blog post outline contains, or what specific metrics to track with exact GA4 report configurations.

Remove the 'Behavioral Traits', 'Knowledge Base', and 'Capabilities' sections entirely—these describe what Claude already knows and waste tokens. Focus only on project-specific constraints, decision frameworks, and validation criteria.

Move detailed reference material (tool comparisons, platform-specific guidelines) into the referenced 'resources/implementation-playbook.md' bundle file and keep SKILL.md as a concise overview with clear pointers.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and padded with extensive lists of capabilities, tools, and concepts that Claude already knows. The content reads like a marketing persona description rather than actionable instructions. Massive sections like 'Capabilities', 'Behavioral Traits', and 'Knowledge Base' are essentially lists of things Claude already understands, wasting significant token budget.	1 / 3
Actionability	No concrete code, commands, templates, or executable examples anywhere. The entire skill is abstract descriptions and vague bullet points like 'Advanced keyword research and semantic SEO implementation' without any specific steps, formats, or outputs. The 'Response Approach' section lists generic high-level steps without actionable detail.	1 / 3
Workflow Clarity	The 'Response Approach' provides a 10-step sequence but it's entirely abstract with no validation checkpoints, no concrete outputs at each step, and no feedback loops. Steps like 'Analyze target audience' and 'Research competition' lack any specificity about how to perform them or verify results.	1 / 3
Progressive Disclosure	There is a reference to 'resources/implementation-playbook.md' for detailed examples, which shows some attempt at progressive disclosure. However, no bundle files exist to support this reference, and the main file itself is a monolithic wall of bullet-pointed lists that should have been split into separate reference files rather than inlined.	2 / 3
	Total	5 / 12 Passed

Description

25%

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. It also uses first/third-person role framing ('strategist specializing in') rather than describing capabilities, and completely lacks trigger guidance for when Claude should select this skill.

Suggestions

Replace buzzword categories with specific concrete actions, e.g., 'Writes blog posts, creates social media copy, generates email campaigns, builds content calendars, and produces SEO-optimized articles.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for blog content, social media posts, SEO writing, content strategy, editorial calendars, or marketing copy.'

Narrow the scope to reduce conflict risk — either split into separate skills (e.g., SEO skill vs. content creation skill vs. analytics skill) or clearly define the boundaries of what this single skill covers versus adjacent skills.

Dimension	Reasoning	Score
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 categories 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 several broad 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 too vague to merit even a 2.	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 description is extremely broad, covering content creation, SEO, distribution, and performance marketing — four potentially separate skill domains. It would easily conflict with any SEO-specific skill, content writing skill, analytics skill, or marketing strategy skill.	1 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 88d1e11

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.