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

Pending

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

Discovery

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 completely lacks trigger guidance ('Use when...') and is too broad to be distinguishable from other marketing-related skills.

Suggestions

Add an explicit 'Use when...' clause listing specific trigger scenarios, e.g., 'Use when the user asks for blog posts, social media copy, content calendars, SEO keyword analysis, or marketing campaign plans.'

Replace vague category labels with concrete actions using third-person verbs, e.g., 'Creates blog posts and articles, generates SEO keyword strategies, builds content calendars, drafts social media copy.'

Narrow the scope or clearly delineate sub-capabilities to reduce conflict risk with other marketing-related skills — currently it spans content creation, SEO, distribution, and analytics which could each be separate 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 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' (content marketing strategy) 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 are less likely to match natural user queries. 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 dedicated SEO skills, content writing skills, analytics skills, or social media skills.	1 / 3
	Total	6 / 12 Passed

Implementation

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 worked examples. The content would need a fundamental restructuring to be useful—replacing abstract capability lists with specific, executable guidance for key content marketing tasks.

Suggestions

Replace the extensive 'Capabilities' bullet lists with 2-3 concrete, worked examples showing actual content marketing outputs (e.g., a sample blog outline template, an email sequence structure, a content calendar format).

Add specific, actionable workflows for the most common tasks—e.g., step-by-step process for creating an SEO-optimized blog post with validation checkpoints like 'verify keyword density is 1-2%' or 'confirm meta description is under 160 characters'.

Move the detailed capability lists and knowledge base sections into a separate reference file and keep SKILL.md focused on quick-start instructions and decision trees for common scenarios.

Remove the 'Behavioral Traits' and 'Knowledge Base' sections entirely—these describe what Claude should be rather than what Claude should do, and Claude already possesses this knowledge.

Dimension	Reasoning	Score
Conciseness	Extremely verbose 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' with 10+ subsections of bullet points add little value and waste tokens on things Claude inherently understands.	1 / 3
Actionability	No concrete code, commands, templates, or executable examples anywhere. The entire skill is abstract descriptions of capabilities and vague behavioral traits. The 'Response Approach' section lists high-level steps like 'Analyze target audience' without any specific methods, tools usage, or concrete outputs. The 'Example Interactions' are just prompt suggestions, not worked examples.	1 / 3
Workflow Clarity	The 'Response Approach' lists 10 generic steps without any validation checkpoints, specific outputs, or feedback loops. Steps like 'Create optimized content using AI tools and SEO best practices' provide no actionable sequence. There is no clear workflow for any specific content marketing task despite the skill covering many complex multi-step processes.	1 / 3
Progressive Disclosure	There is a single reference to 'resources/implementation-playbook.md' for detailed examples, which is a good signal of progressive disclosure. However, the main file itself is a monolithic wall of bullet-pointed lists that should have been split into separate reference files. The massive capabilities section could easily be offloaded.	2 / 3
	Total	5 / 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: 93c57b2

Reviewed: 6 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.