Expert content strategist and creator for multi-platform campaigns. Develops editorial calendars, creates compelling copy, manages brand storytelling, and optimizes content for engagement across all digital channels.
28
12%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./marketing-content-creator/skills/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.
The description reads more like a job title or resume summary than a skill description for Claude's skill selection. While it lists some actions, the language is padded with marketing buzzwords ('compelling', 'brand storytelling', 'engagement') and lacks the explicit trigger guidance ('Use when...') that is critical for skill disambiguation. The extremely broad scope ('all digital channels') makes it highly likely to conflict with more specific content-related skills.
Suggestions
Add an explicit 'Use when...' clause with concrete trigger scenarios, e.g., 'Use when the user asks for help creating editorial calendars, writing marketing copy, planning content campaigns, or developing social media content strategies.'
Narrow the scope or enumerate specific deliverables instead of 'all digital channels' — e.g., 'blog posts, social media captions, email newsletters, landing page copy'.
Replace vague buzzwords like 'compelling copy' and 'brand storytelling' with concrete actions like 'writes blog posts, drafts social media captions, plans weekly/monthly content schedules'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (content strategy) and lists several actions like 'develops editorial calendars', 'creates compelling copy', 'manages brand storytelling', and 'optimizes content for engagement', but uses somewhat buzzwordy language ('compelling copy', 'brand storytelling') that reduces concreteness. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent (not even implied well), this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'editorial calendars', 'copy', 'brand storytelling', and 'digital channels', but misses many natural user terms like 'blog post', 'social media post', 'content calendar', 'SEO', 'newsletter', 'marketing copy'. The phrase 'multi-platform campaigns' is more jargon than natural user language. | 2 / 3 |
Distinctiveness Conflict Risk | The description is extremely broad — 'all digital channels', 'multi-platform campaigns', 'content for engagement' — and could easily overlap with social media skills, copywriting skills, SEO skills, marketing skills, or any content-related skill. There is no clear niche or distinct trigger. | 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 content reads like a job description or marketing brochure rather than an actionable skill file. It lists capabilities and metrics but provides zero concrete instructions, templates, examples, or workflows that Claude could follow to actually create content. Every section describes what the agent does rather than teaching how to do it.
Suggestions
Replace the 'Core Capabilities' and 'Specialized Skills' lists with concrete workflows — e.g., a step-by-step process for creating a blog post including outline template, SEO checklist, and example output format.
Add executable templates and examples: provide a sample editorial calendar structure, a blog post outline template, a social media post format with before/after examples showing brand voice application.
Include specific decision trees or checklists for common tasks like 'choosing content format based on platform' or 'adapting long-form content for social media' with concrete transformation examples.
Remove the 'Success Metrics' section entirely (arbitrary benchmarks Claude can't act on) and the 'Role Definition' (Claude doesn't need to be told what a content strategist is), replacing them with actionable content creation procedures.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with information Claude already knows. It lists generic marketing concepts, vague capability descriptions, and arbitrary success metrics without providing any actionable instructions. The 'Role Definition' and 'Core Capabilities' sections explain concepts Claude inherently understands. | 1 / 3 |
Actionability | There is no concrete, executable guidance anywhere in the skill. No templates, no example outputs, no specific commands or formats, no step-by-step processes. It describes what the agent can do rather than instructing how to do it — entirely abstract and descriptive. | 1 / 3 |
Workflow Clarity | There are no workflows, sequences, or processes defined. The 'Decision Framework' is just a list of when to use the agent, not how to execute any task. No validation steps, no feedback loops, no ordered procedures for any content creation task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic list of bullet points with no references to external files, no navigation structure, and no layered information architecture. All sections are at the same shallow depth with no way to drill into specifics. | 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 | |
09aef5d
Table of Contents
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.