CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

marketing-plan

When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," "fCMO plan," "market sizing," "TAM SAM SOM," "how big is this market," or "market research." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.

Quality

90%

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

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

The body is a strong orchestration layer: highly actionable, with a clearly sequenced three-phase workflow, explicit validation passes, user approval loops, and resumable state handling. Its weaknesses are moderate verbosity (AARRR definitions, investing philosophy, and tone advice that Claude doesn't need) and two orphaned bundle files — including the canonical worked example — that are never referenced from the main document.

Suggestions

Cut or compress the 'Marketing as investing' section (~45 lines) and 'A note on tone' to a few non-obvious rules each, and drop the AARRR stage definitions Claude already knows, keeping only the skill-specific framing rules (brand as cross-cutting, closed-window rate matching).

Add explicit pointers to the two orphaned bundle files: link references/example-quietude.md as the 'what good looks like' example (e.g., from the Quality bar section) and references/measurement-framework.md from Section 13's description in the plan structure.

Deduplicate the ops-stack pointer (stated twice — in 'Cross-references' and 'The marketing operations stack') and consider moving the inline funding-tier dollar ranges fully into references/funding-stage-unlocks.md with only the tier names kept inline.

DimensionReasoningScore

Conciseness

The body is dense and mostly operational, but several sections explain concepts Claude already knows or restate strategic doctrine at length: the AARRR quick rule defines standard funnel stages, the ~45-line "Marketing as investing" section spins out investing metaphors ("No silver bullets, a hundred golden pellets," "Time in market beats timing the market"), and "A note on tone" gives generic writing advice ("No jargon for jargon's sake"). This matches the anchor "mostly efficient but includes some unnecessary explanation or could be tightened" — above 2 ("several unnecessary explanations or padded sections") because most sections carry skill-specific operational content, but below 4 because the over-explanation is more than minor.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact invocation syntax with examples ("/marketing-plan quietude.app"), a concrete file layout with paths (~/marketing-plans/{client-slug}/progress.md, sections/01.md), an explicit budget formula ("[(New ARR / (ARPC × 12)) × CAC] / annual retention rate"), dollar-range funding tiers, the 70/20/10 allocation rule, a 10-question intake list, path-safety rules, and output-format specs (H2 headers, §N cross-refs, 8,000–12,000 words). Per the rubric's instruction-skill note, absence of code is not penalized when guidance is this concrete — this matches the top anchor's "specific examples cover the common cases."

5 / 5

Workflow Clarity

The three-phase workflow (INIT → REVIEW → FINALIZE) is clearly sequenced with explicit checkpoints and feedback loops: REVIEW walks each of 13 sections with an approve/adjust/expand user loop, FINALIZE has a named verification pass ("confirm cross-references... are accurate; check for machine-specific paths that shouldn't ship; ensure the brand voice matches"), interruption is handled by a documented resumption state machine, and FINALIZE has a safety gate ("Finalized plans are never silently overwritten"). This matches the anchor-5 pattern of explicit validation steps, feedback loops, and error-recovery — the 4 anchor's "minor validation gaps" understates the checkpoint density, though the numeric consistency of budget math is not explicitly in the verification list.

5 / 5

Progressive Disclosure

Structure is good: 12 reference files are all one level deep and clearly signaled with a consistent "Full X in references/X.md" pattern, and every referenced path was verified to exist on disk. However, two of the fourteen bundle files are orphaned — example-quietude.md (self-described as "the canonical reference example... the bar to clear") and measurement-framework.md (the source for Section 13's measurement subsection) are never linked from SKILL.md, so the most valuable deep-dive materials are undiscoverable from the overview. This fits the 4 anchor ("good structure... minor organization gaps") rather than 5 ("easy navigation" with everything well-signaled).

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: it explicitly covers what the skill produces (13-section AARRR plan, specific integrations, output format) and when to use it, with an unusually thorough list of natural trigger synonyms (GTM/go-to-market, fCMO/fractional CMO). The only weakness is that the market-sizing/research triggers pull in a broader range of queries than the full-plan deliverable serves, creating minor conflict risk with adjacent skills it itself names.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric" — plus a concrete output artifact ("Outputs a Notion-paste-ready markdown document"). This matches the anchor for comprehensive, specific concrete actions; the 4 anchor ("minor gaps in coverage") understates it since every major capability of the skill is named.

5 / 5

Completeness

Both "what" and "when" are explicitly answered with concrete trigger phrases: it opens with "When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product" and adds "Also use when the user mentions [phrase list]," then fully specifies the deliverable. This is the anchor-5 pattern (what + when with concrete trigger phrases), clearly above the 4 anchor where the "when" is only loosely specified.

5 / 5

Trigger Term Quality

Trigger terms are comprehensive with synonyms and both abbreviated and expanded forms: "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," "fCMO plan," "market sizing," "TAM SAM SOM," "how big is this market," "market research." Natural user phrasing ("how big is this market") is included alongside jargon variants (fCMO/fractional CMO, GTM/go-to-market), matching the top anchor; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The skill is mostly distinct — it explicitly routes adjacent work to other skills ("For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing"), which lowers conflict risk. However, the trigger list includes "market sizing," "TAM SAM SOM," "market research," and "how big is this market," which would fire on pure research/sizing questions where a full 13-section plan is overkill, creating minor overlap with adjacent skills. Not 5 ("minimal conflict risk") due to those broadened research triggers; clearly above 3 since the core plan triggers are a clear niche.

4 / 5

Total

19

/

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

coreyhaines31/marketingskills

Path

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