content-marketer
Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing.
23
12%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/content-marketer/SKILL.mdQuality
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.
This description reads like a LinkedIn headline rather than a functional skill description. It relies on marketing buzzwords ('elite,' 'omnichannel,' 'data-driven') without specifying concrete actions or providing any trigger guidance for when Claude should select it. The use of adjective-heavy phrasing and lack of a 'Use when...' clause make it poorly suited for skill selection among multiple options.
Suggestions
Replace buzzword categories with specific concrete actions (e.g., 'Creates blog posts, social media copy, email campaigns, and landing page content. Performs keyword research and optimizes content for SEO.').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks for help writing marketing content, blog posts, SEO copy, social media posts, email newsletters, or content strategy.').
Narrow the scope to reduce conflict risk — either focus on content creation, SEO, or distribution strategy rather than claiming all of content marketing, or clearly delineate the boundaries of this skill versus related ones.
| 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 read more like buzzword categories than concrete actions. No specific verbs describing what the skill actually does (e.g., 'writes blog posts,' 'generates SEO keywords,' 'creates distribution calendars'). | 2 / 3 |
Completeness | Describes a vague 'what' through buzzword categories but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent statement telling Claude when to select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'content marketing,' 'SEO optimization,' and 'content creation' that users might mention. However, it misses common natural variations users would say (e.g., 'blog post,' 'social media post,' 'keyword research,' 'content calendar,' 'marketing copy') and relies heavily on jargon like 'omnichannel distribution' and 'data-driven performance marketing.' | 2 / 3 |
Distinctiveness Conflict Risk | The description is extremely broad, covering content creation, SEO, distribution, and performance marketing — each of which could be its own skill. It would easily conflict with any SEO skill, copywriting skill, social media skill, or analytics skill. The breadth makes it indistinguishable from many potential overlapping skills. | 1 / 3 |
Total | 6 / 12 Passed |
Implementation
0%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 verbose persona/role description rather than an actionable skill. It lists extensive marketing concepts, tools, and strategies that Claude already knows, without providing any concrete templates, executable examples, or specific workflows. The content consumes a large token budget while delivering almost no novel, actionable guidance.
Suggestions
Replace the massive capabilities listing with a concise scope statement (2-3 sentences) and focus on specific, actionable templates or frameworks Claude should follow (e.g., a content brief template, an SEO checklist with specific steps).
Add concrete, copy-paste-ready examples such as a sample content strategy outline, email sequence template, or SEO optimization checklist with specific validation steps.
Create the referenced 'resources/implementation-playbook.md' bundle file and move detailed guidance there, keeping SKILL.md as a lean overview with clear navigation pointers.
Replace the generic 10-step 'Response Approach' with a specific workflow that includes validation checkpoints (e.g., 'Confirm target keywords with user before proceeding to content creation').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with information Claude already knows. The massive 'Capabilities' section lists dozens of marketing concepts, tools, and strategies that are general knowledge for Claude. The 'Knowledge Base', 'Behavioral Traits', and 'Example Interactions' sections add no actionable value. This is essentially a persona description, not a skill, and wastes enormous token budget. | 1 / 3 |
Actionability | No concrete code, commands, templates, or executable guidance anywhere. The 'Response Approach' is a generic 10-step process that describes rather than instructs. There are no specific examples of content output, no templates, no frameworks with actual fill-in structures. The reference to 'resources/implementation-playbook.md' is the only potentially actionable element but no bundle file exists. | 1 / 3 |
Workflow Clarity | The 'Response Approach' lists 10 high-level steps but they are vague and lack any validation checkpoints, decision points, or feedback loops. Steps like 'Analyze target audience' and 'Optimize based on data' provide no concrete guidance on how to execute or verify outcomes. No error handling or quality gates are defined. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no meaningful structure for navigation. It references 'resources/implementation-playbook.md' but no bundle files exist, making this a broken reference. All content is dumped inline in massive bullet-point lists rather than being organized into a concise overview with references to detailed materials. | 1 / 3 |
Total | 4 / 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.
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
f5dc9e3
- 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.