marketing-plan
An agent skill by coreyhaines31, from coreyhaines31/marketingskills. Tags: analysis, documentation, marketing, planning, strategy.
What it does
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," or "fCMO plan." 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 full 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.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add coreyhaines31/marketingskills --skill marketing-plan
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/coreyhaines31/marketingskills
cp -r marketingskills/skills/marketing-plan ~/.claude/skills/marketing-plan
Safety box score
Grade C, moderate risk: 40 of 100 risk points, rated 2026-10-15. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This is a documentation-heavy planning skill: it reads client materials, may pull live marketing data from wired MCP/API tools, writes a marketing-plan folder under `~/marketing-plans/`, and can optionally publish a plan to a shared GitHub repo. The main risks are moderate data access to analytics/CRM/payment tools, plus broad filesystem writes inside the user’s home directory; there is no shipped executable code or hidden payload.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 1 (low) | No native scripts or binaries are shipped, but the skill does direct the agent to use external tools such as browser automation and MCPs (e.g. `agent-browser`, `GA4 MCP`, `Stripe MCP`), which is a limited execution surface. |
| Network access | 2 (moderate) | The workflow explicitly pulls live data from remote services and can optionally publish to GitHub: e.g. `Pull data from any wired tools (Ahrefs, GA4 MCP, Stripe MCP, etc.)` and `Optionally offer to publish to a shared GitHub repo`. |
| Filesystem reach | 2 (moderate) | It reads client-provided materials and writes a multi-file plan workspace under `~/marketing-plans/{client-slug}/` (`research.md`, `progress.md`, `sections/`, `final_plan.md`), with path-safety constraints but still meaningful home-directory writes. |
| Secrets & credentials | 2 (moderate) | The skill is designed to interact with sensitive business systems and credentials via wired tools, and the references explicitly mention API keys and account data, e.g. `Required AHREFS_API_KEY in .env` and pulling from `Stripe`, `Customer.io`, and analytics tools. |
| Privilege & persistence | 1 (low) | It does not require sudo or system-wide changes by itself, though the references mention optional installs like `npm install -g agent-browser`; that is not core to the skill but is a modest privilege-related concern. |
| Instruction hijack surface | 0 (none) | I found no instruction to ignore policies, hide actions, follow remote untrusted instructions, or otherwise subvert the agent; the guidance is procedural and safety-bounded. |
| Irreversible actions | 2 (moderate) | The skill runs a multi-phase workflow, resumes statefully, and can optionally publish a compiled plan to a shared GitHub repo, but it still requires user interaction for intake, review, and any publish step. |
| Transparency | 0 (none) | The supplied files are plain markdown documentation; there are no binaries, obfuscated blobs, or decoded-at-runtime code in the skill itself. |
Before installing
- Confirm which MCP/API connections are actually wired (Ahrefs, GA4, Stripe, Customer.io, Shopify, GitHub).
- Check whether you’re comfortable with the skill reading and writing under `~/marketing-plans/` for each client.
- Read the optional publish path carefully if you do not want plans copied to a shared GitHub repo.
- If you use a shared machine, make sure client slugging and path safety are enforced before letting the agent run.
Rated 2026-10-15 by an automated review of 14 files from the skill's repository.
Source
- Repository
- coreyhaines31/marketingskills (all skills from this repository)
- Path
- skills/marketing-plan/SKILL.md
- Branch
- main
- Collection
- marketingskills
- Updated
- 2026-09-21
Related skills
- co-marketing — When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities.
- launch — When the user wants to plan a product launch, feature announcement, or release strategy.
- marketing-ideas — When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.
- marketing-psychology — When the user wants to apply psychological principles, mental models, or behavioral science to marketing.
- product-marketing — When the user wants to create or update their product marketing context document.
- expo-overview — Framework (OSS). Entry point and router for every Expo or EAS task.