content-marketer
Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing. Masters modern content tools, social media automation, and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive content marketing.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill content-marketerActivation
42%The description suffers from marketing-speak and buzzwords ('Elite', 'Masters', '2024/2025 best practices') rather than concrete, actionable capabilities. It covers too broad a domain without clear boundaries, and the trigger guidance is essentially useless for skill selection. The first-person framing ('Elite content marketing strategist') violates the third-person voice requirement.
Suggestions
Replace vague trigger guidance with specific scenarios: 'Use when user asks to write blog posts, create social media content, optimize content for SEO, or develop content calendars'
Narrow the scope or clearly delineate sub-capabilities to reduce conflict with other marketing/writing skills
Remove self-promotional language ('Elite', 'Masters') and rewrite in third person with concrete actions: 'Creates blog posts, social media content, and email campaigns. Optimizes content for SEO and analyzes performance metrics.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (content marketing) and lists several areas like 'AI-powered content creation, omnichannel distribution, SEO optimization' but these are broad categories rather than concrete actions. Phrases like 'Masters modern content tools' are vague claims rather than specific capabilities. | 2 / 3 |
Completeness | The 'what' is partially addressed through listed capabilities, but the 'when' clause ('Use PROACTIVELY for comprehensive content marketing') is extremely vague and doesn't provide explicit trigger guidance. It fails to specify concrete scenarios when this skill should be selected. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'content marketing', 'SEO optimization', 'social media automation', and 'conversion optimization' that users might mention. However, missing common variations and natural phrases users would say like 'blog post', 'write content', 'marketing copy', 'social posts'. | 2 / 3 |
Distinctiveness Conflict Risk | Very broad scope covering content creation, SEO, social media, and conversion optimization could easily conflict with dedicated skills for any of these individual areas. The description doesn't carve out a clear niche that distinguishes it from other marketing or writing skills. | 1 / 3 |
Total | 7 / 12 Passed |
Implementation
20%This skill reads like a job description or persona prompt rather than actionable guidance. It extensively lists capabilities and concepts Claude already understands while providing zero concrete examples, code, templates, or specific workflows. The content would benefit from dramatic reduction and replacement with actual executable guidance.
Suggestions
Replace capability lists with 2-3 concrete, copy-paste-ready templates (e.g., a blog post outline template, an email sequence structure, a social media post format)
Add specific tool commands or API examples for the AI tools mentioned (Agility Writer, Buffer, etc.) rather than just listing tool names
Transform the vague 'Response Approach' into a concrete workflow with validation steps, such as 'Before publishing, verify: [ ] keyword density 1-2%, [ ] meta description under 160 chars, [ ] all images have alt text'
Remove the 'Capabilities', 'Behavioral Traits', and 'Knowledge Base' sections entirely - Claude doesn't need to be told what content marketing is or that it should be 'data-driven'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of concepts Claude already knows (what AI tools are, what SEO is, basic marketing concepts). The massive capability lists, behavioral traits, and knowledge base sections add little actionable value and consume significant tokens explaining obvious concepts. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. The content describes capabilities and lists tools but never shows how to actually do anything. 'Example Interactions' are just prompts, not demonstrations of outputs or workflows. | 1 / 3 |
Workflow Clarity | The 'Response Approach' section provides a 10-step sequence, but steps are vague ('Analyze target audience', 'Research competition') with no validation checkpoints, specific tools to use, or feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | References `resources/implementation-playbook.md` for detailed examples, which is good progressive disclosure. However, the main file is a monolithic wall of text with poor organization - capability lists could be separate reference files rather than inline. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
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.