CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

marketing-skills

Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill — it does not execute marketing work itself.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary index skill: the entire body is a lean, categorized route table with exact paths, an unambiguous entry decision flow, and clean delegation of all detail to the specialist skills. The only flaws are minor token redundancies — the stdlib/no-pip constraint stated three times and a couple of chatty asides.

Suggestions

State the stdlib/no-pip constraint once (e.g., keep only the Rules bullet) instead of three times across the intro, Python Tools section, and Rules.

Trim chatty phrasing like 'kept honest' and 'then get out of the way' — the counts and routing behavior are already clear without them.

DimensionReasoningScore

Conciseness

The route table is dense and every row earns its place, with no concept explanations Claude already knows. It is not a 5 because the stdlib/no-pip point is repeated three times ('No pip installs needed', 'All 59 scripts are stdlib-only', 'Don't pip-install anything') and a few chatty asides ('kept honest', 'get out of the way') could be trimmed.

4 / 5

Actionability

Fully actionable for a router: exact relative paths for every skill, a runnable command template ('python3 skills/<skill>/scripts/<tool>.py --help'), a concrete first-run artifact ('.claude/product-marketing-context.md'), and an explicit deprecation redirect ('content-creator' → 'skills/content-production/'). The placeholder in the command template is justified because it indexes 59 tools across 44 skills.

5 / 5

Workflow Clarity

A single-purpose routing skill with an unambiguous three-branch entry flow ('First run ever?', 'Know your task?', 'Ambiguous request?') where each branch names the exact skill to load. No validation checkpoints are needed since routing involves no destructive or batch operations, so the cap does not apply.

5 / 5

Progressive Disclosure

The body is essentially a well-signaled, one-level-deep reference index: 44 exact skill paths organized into 7 labeled category tables with the path base stated ('All paths are relative to marketing-skill/'), plus pointers to the canonical router and the sibling video plugin. All detail lives in the specialist skills, which is exactly the right split; not a 4 because navigation and organization have no real gaps.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong router description: it names its role precisely, includes an explicit 'Use when' clause with three concrete navigation triggers, quantifies scope (44 skills, 8 pods, 59 tools), and draws a clear boundary that it routes rather than executes. The only gap is that task-level natural keywords (campaign, email, ads) are not surfaced, though pod-level categories partially cover them.

Suggestions

Add a few task-level trigger keywords users naturally say (e.g., 'campaign', 'email sequence', 'social media', 'copywriting') so the router surfaces for concrete marketing requests, not just navigation requests.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('find the right marketing skill for a task', 'see what marketing capabilities exist', 'get oriented in this plugin', 'Routes to one skill') with concrete scope (44 skills, 8 named pods, 59 tools), giving comprehensive coverage for a router skill. It is not a 4 because there are no meaningful gaps in the router's action space.

5 / 5

Completeness

Explicitly answers both what ('Routes to one skill — it does not execute marketing work itself', with counts and structure) and when ('Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin') with three concrete trigger phrases. Matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases ('find the right marketing skill', 'marketing capabilities') and category terms (SEO, AEO, CRO, growth, sales enablement). It is not a 5 because common variations users actually say for individual tasks — 'campaign', 'email', 'ads', 'copywriting', 'social media' — are absent; not a 3 because category-level coverage is solid and relevant.

4 / 5

Distinctiveness Conflict Risk

Clear niche — navigation and orientation rather than executing marketing work — with an explicit boundary clause ('it does not execute marketing work itself') that minimizes conflict with the 44 specialist skills. Not a 4 because the trigger phrases are purely navigation-oriented and would not fire for execution requests.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

marketing-skill/skills/marketing-skills/SKILL.md

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.