Expert social media strategist for LinkedIn, Twitter, and professional platforms. Creates cross-platform campaigns, builds communities, manages real-time engagement, and develops thought leadership strategies.
32
16%
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-social-media-strategist/skills/SKILL.mdQuality
Discovery
32%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 provides a reasonable overview of the skill's domain and lists several capability areas, but it lacks the concrete specificity and explicit trigger guidance needed for reliable skill selection. The absence of a 'Use when...' clause is a significant weakness, and the action descriptions remain at a high strategic level rather than naming concrete deliverables.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about LinkedIn posts, Twitter threads, social media campaigns, professional branding, or content calendars.'
Make capabilities more concrete by listing specific deliverables: 'Drafts LinkedIn posts, composes tweet threads, creates content calendars, writes engagement responses, develops hashtag strategies.'
Include more natural keyword variations users might say, such as 'social media content,' 'post ideas,' 'professional networking,' 'social media plan,' or 'content strategy.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (social media strategy) and lists several actions like 'creates cross-platform campaigns, builds communities, manages real-time engagement, develops thought leadership strategies,' but these are somewhat high-level and lack concrete granular actions (e.g., 'drafts LinkedIn posts,' 'schedules tweets,' 'writes hashtag strategies'). | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any 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 natural keywords like 'LinkedIn,' 'Twitter,' 'social media,' 'campaigns,' 'thought leadership,' and 'engagement,' but misses common user variations like 'post,' 'tweet,' 'content calendar,' 'social media content,' 'professional branding,' or 'social media strategy.' | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning specific platforms (LinkedIn, Twitter) and professional context helps distinguish it, but terms like 'campaigns,' 'communities,' and 'engagement' are broad enough to overlap with general marketing or content creation skills. | 2 / 3 |
Total | 7 / 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 reads as a marketing role description or persona definition rather than an actionable skill file. It is extremely verbose, entirely abstract, and provides no concrete instructions, templates, examples with expected outputs, or executable workflows. Nearly every section describes what the agent 'does' conceptually rather than instructing Claude on how to actually perform specific tasks.
Suggestions
Replace abstract capability lists with concrete, actionable templates (e.g., a LinkedIn post template with example input/output, a campaign planning checklist with specific steps).
Add step-by-step workflows for key tasks like 'Create a cross-platform campaign' with explicit sequencing and validation checkpoints (e.g., 'Step 1: Define objective → Step 2: Draft platform-specific content → Step 3: Review against brand guidelines → Step 4: Schedule').
Cut the 'Role Definition,' 'Core Capabilities,' 'Specialized Skills,' 'Communication Style,' and 'Learning & Memory' sections entirely—these describe traits Claude doesn't need explained and waste token budget.
Add concrete output format examples (e.g., 'When asked for a LinkedIn strategy, output in this format: [example]') so Claude knows exactly what deliverable to produce.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive sections that describe capabilities, roles, and concepts Claude already understands. The 'Role Definition,' 'Core Capabilities,' 'Specialized Skills,' 'Communication Style,' and 'Learning & Memory' sections are largely padding that don't provide actionable, novel information. The entire document reads like a job description rather than a skill file. | 1 / 3 |
Actionability | The content is entirely abstract and descriptive—no concrete commands, executable code, templates, or copy-paste-ready examples. Sections like 'Platform Strategy Framework' and 'Campaign Management' list bullet points of vague guidance (e.g., 'Regular updates, employee spotlights, industry insights') without any specific, actionable instructions or output formats. | 1 / 3 |
Workflow Clarity | There are no clearly sequenced multi-step workflows. The 'Workflow Integration' section lists handoff relationships but provides no actual process steps. 'Campaign Planning' lists categories but no ordered workflow with validation checkpoints. Nothing tells Claude what to actually do step-by-step. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no clear hierarchy. All content is inline with no progressive disclosure structure—everything from high-level strategy to platform-specific details is dumped into one long document with no navigation aids or linked resources. | 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.