CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

marketing-ops

Central router for the marketing skill ecosystem. Use when unsure which marketing skill to use, when orchestrating a multi-skill campaign, or when coordinating across content, SEO, CRO, channels, and analytics. Also use when the user mentions 'marketing help,' 'campaign plan,' 'what should I do next,' 'marketing priorities,' or 'coordinate marketing.'

68

Quality

86%

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

82%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.

A well-executed router skill: the routing matrix with 'NOT this' disambiguation is genuinely actionable, the campaign orchestration sequences are concrete and ordered, and the quality gate plus tracker integration give the workflow explicit checkpoints. The main improvements are trimming minor marketing-speak and adding an ambiguity-resolution rule for requests that match multiple routes.

DimensionReasoningScore

Conciseness

The body is dominated by dense trigger/route tables with a genuinely useful "NOT this" disambiguation column — an efficient format for a router. Minor padding remains (the "works 3x better with context" marketing line, the role preamble), so it sits at efficient-with-trimmable-instances rather than every-token-earns-its-place.

4 / 5

Actionability

For an instruction-only skill, guidance is fully executable: an exact routing matrix (trigger → named skill, with disambiguation), a copy-paste command "python3 scripts/campaign_tracker.py campaign.json" whose embedded sample makes the campaign JSON format discoverable, three concrete numbered campaign sequences, an output-artifacts table, and a pre-output quality gate. Common cases are covered with specific, ready-to-follow direction.

5 / 5

Workflow Clarity

Three clearly defined modes, step-numbered campaign sequences, and an explicit pre-output Quality Gate checklist tied to tracker check-ins ("run the tracker at every check-in — the overdue/ownerless flags feed the Quality Gate"). Not 5: there is no explicit feedback loop for ambiguous routing (what to do when a request matches two rows) and validation checkpoints are implicit in the sequences.

4 / 5

Progressive Disclosure

The single bundle file (scripts/campaign_tracker.py) exists and is clearly referenced with its arguments, and the body is well-sectioned with headers and tables. Not 5: at ~200 lines, content that could live in reference files (the full routing matrix per pod, the three campaign sequence templates) is inlined in SKILL.md; not 3 because what is present is well-signaled and appropriately organized for a router that needs its matrix loaded at decision time.

4 / 5

Total

17

/

20

Passed

Description

83%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: third-person, specific about routing/orchestration/coordination, with an explicit and well-triggered 'Use when' clause covering both use-when-unsure and cross-domain coordination scenarios. The only weakness is that its broadest trigger phrases could collide with the specialist skills it is meant to disambiguate.

DimensionReasoningScore

Specificity

"Central router for the marketing skill ecosystem" names the domain and several concrete actions ("route marketing questions", "orchestrating a multi-skill campaign", "coordinating across content, SEO, CRO, channels, and analytics") in third-person voice. Not 5 because the actions are coordination meta-verbs rather than a comprehensive list of concrete operations; well above the 1-2-action anchor of 3.

4 / 5

Completeness

Explicitly answers both questions: what ("Central router for the marketing skill ecosystem" that routes, orchestrates, and coordinates) and when ("Use when unsure which marketing skill to use, when orchestrating a multi-skill campaign... Also use when the user mentions 'marketing help,' 'campaign plan'...") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Includes natural, quotable user phrasings — "marketing help," "campaign plan," "what should I do next," "marketing priorities," "coordinate marketing" — plus "when unsure which marketing skill to use". A few common variations (e.g., "marketing audit," "growth plan," "which skill should I use") are missing, keeping it at the good-but-not-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche as the ecosystem's router with distinct "unsure which skill" triggers, but broad phrases like "marketing help" and "marketing priorities" overlap siblings such as cmo-advisor and the specialist skills it routes to. Minor overlap risk, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

marketing-skill/skills/marketing-ops/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.