Agent skill

Marketing Plan

by Nexus-JPF in Nexus-JPF/note-companion

When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

MITAuto-check passedMarketing & SEO

Install Marketing Plan

skills CLI
$ npx skills add Nexus-JPF/note-companion --skill marketing-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Nexus-JPF/note-companion marketing-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/marketing-plan .claude/skills/marketing-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
marketing-plan
GitHub stars
870
Used in
5 other repos
Token cost
~5.2k tokens
SKILL.md length
2,641 words
Files
15 (incl. references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

  • Works in 3 steps: INIT (research + intake) → REVIEW (walk through each of 13 sections… → FINALIZE (compile + verify + publish)
  • Needs a comprehensive marketing plan for a client
  • SKILL.md covers When to use, How this skill is invoked, The three phases and The 13-section plan structure, plus 17 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Marketing Plan is an agent skill from Nexus-JPF/note-companion. 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…

Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including reference files (for example `evals/evals.json`, `references/aarrr-framework.md` and `references/budget-planning.md`).

It sits in Marketing & SEO, covering Go-to-market strategy and Product metrics. It works with Notion and Model Context Protocol. The repository describes itself as: Note Companion: AI assistant for Obsidian that goes beyond just a chat. (prev File Organizer 2000). The licence is MIT.

When your agent uses it

  • Needs a comprehensive marketing plan for a client
  • A company they advise
  • Their own product
  • The user mentions marketing plan

Example prompts

  • “marketing plan,”
  • “growth plan,”
  • “GTM plan,”
  • “/marketing-plan”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. INIT (research + intake)
  2. REVIEW (walk through each of 13 sections interactively)
  3. FINALIZE (compile + verify + publish)

What it can do on your machine

Read from SKILL.md and the folder at commit 9cad635. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Marketing Plan loads about 5.2k tokens when it runs, and up to ~60k if it reads all its reference files. Until then it costs about 241 tokens; SKILL.md has 2,641 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~241
When it runs · the whole SKILL.md, loaded when a task matches
~5.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~60k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 2,641 words, ~5,247 tokens.

Download SKILL.mdSave it as .claude/skills/marketing-plan/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
marketing-plan
description
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.

Marketing Plan

You are an expert marketing strategist operating at fCMO (fractional CMO) level. Your job is to produce a comprehensive, executable 12-month marketing plan for a specific client or company, structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to their actual budget, team, stage, and capabilities, and cross-referenced with the full marketing-ideas library and the embedded 17-section current-state audit rubric.

The deliverable is a single Notion-paste-ready markdown document — the kind of strategy artifact a fractional CMO would present to founders. It must be specific to the client (not generic), exhaustive (covers every tactical surface area, not just what's prescribed), and operationally honest (reflects what their team can actually execute with their current stack and headcount).

When to use

Invoke this skill when:

  • A user is starting a new client engagement as a fractional CMO or marketing consultant
  • A founder needs a 12-month marketing roadmap they can share with their team or investors
  • A team wants to consolidate scattered marketing work (SEO research, brand voice docs, audit findings, onboarding analyses) into a single coherent plan
  • The user explicitly asks for a "marketing plan," "growth plan," "GTM plan," "fCMO plan," "AARRR plan," or "90-day + 12-month marketing roadmap"
  • An existing scored audit (from any prior current-state assessment) needs to be sequenced into an action plan

Do not use when the user wants a tactical execution document for a single channel (use the channel-specific skill instead — emails, ads, seo-audit, onboarding, etc.), or when the user just wants marketing ideas without commitment to a plan (use marketing-ideas).

How this skill is invoked

/marketing-plan {client-name-or-domain}

Examples:

  • /marketing-plan quietude.app
  • /marketing-plan acme-saas
  • /marketing-plan (will prompt for client name)

On invocation, the skill reads ~/marketing-plans/{client-slug}/progress.md and resumes based on the state machine documented in references/methodology.md Step 1.1.2 (fresh → INIT → REVIEW → FINALIZE → finalized). Finalized plans are never silently overwritten — the user is asked whether to revise as v{N+1}, start fresh, or re-open a section.

The three phases

The full workflow lives in references/methodology.md. Quick summary:

Phase 1 — INIT (research + intake)

Read all available materials about the client. Pull data from any wired tools (Ahrefs, GA4 MCP, Stripe MCP, etc.). Conduct structured intake covering: client overview, ICP, current funnel state, funding state, team composition, marketing budget, channels currently active, what's already been done, what's in-flight, what's stuck, tooling stack. Save to research.md.

Use the embedded 17-section current-state rubric (references/current-state-rubric.md) as your scoring lens for Section 3 — score each section 0–5 against available materials.

Phase 2 — REVIEW (walk through each of 13 sections interactively)

Present each section's draft in chat. For each section you can:

  • Approve as-is ("good," "next")
  • Adjust ("change X to Y")
  • Add observations ("also mention Z")
  • Expand ("go deeper on this")

Save each confirmed section to the progress file as you go. The skill is resumable — if interrupted, run /marketing-plan client-name again to pick up at the next unfinished section.

Phase 3 — FINALIZE (compile + verify + publish)

Compile all 13 sections into final_plan.md. Run a verification pass: confirm cross-references (marketing-ideas idea numbers, related skills, MCP integrations) are accurate; check for machine-specific paths that shouldn't ship; ensure the brand voice matches what was captured in the strategic frame.

Optionally offer to publish to a shared GitHub repo (e.g., {client-org}/{client-context}/marketing/plan.md) if the user wants to share it with the team.

The 13-section plan structure

Full template lives in references/plan-template.md. The structure:

  1. Executive summary — 3 big bets, 90-day priorities, 12-month outcome. Written so it can be lifted into an investor or board update.
  2. Strategic frame — Category claim, ICP distilled, business-model logic, brand voice non-negotiables.
  3. Current state — Team, budget, what's done, what's in-flight, what's stuck. Scored against the embedded 17-section current-state rubric (references/current-state-rubric.md).
  4. Acquisition — How strangers become aware. Channels current + planned + skipped, 90-day and 12-month moves, skills + tools.
  5. Activation — How a new user has an experience that converts. Onboarding, first session, App Store / signup, paywall, lifecycle setup.
  6. Retention — How a converted user stays and deepens. Lifecycle flows, churn prevention, win-back, support-as-marketing.
  7. Referral — How retained users bring more users. Ambassador / affiliate / Guides / WOM mechanics.
  8. Revenue — Pricing, packaging, upsells, bundles, hardware-to-software, B2B ACV.
  9. 90-day roadmap — Weeks 1–2 (Unblock), 3–4 (Foundation), 5–8 (Velocity), 9–12 (Compound). AARRR-tagged, owner-assigned.
  10. 12-month outlook — Quarterly milestones tied to funding-stage capability unlocks.
  11. Marketing operations stack — Marketing skills + MCP/API integrations mapped to each AARRR stage. Capability unlocks by funding stage.
  12. Tactical idea bank — All 139 ideas from marketing-ideas cross-referenced to AARRR + client-specific status (Now / Q2 / Q3+ / Q4+ / Skip).
  13. Measurement, RACI, open decisions, appendix — North-star metric, leading indicators by stage, RACI table, blocking decisions, links to deeper docs.

The AARRR framing

AARRR replaces the older "channels and tactics" approach because it forces every recommendation to be funnel-stage-tagged, which makes the plan executable in priority order.

Full primer in references/aarrr-framework.md. Quick rule:

  • Acquisition = strangers → aware (top of funnel)
  • Activation = aware → first valued experience (signup, onboarding, first session)
  • Retention = repeat users (lifecycle, churn prevention, deepening engagement)
  • Referral = retained users → bring more users (programs, viral mechanics)
  • Revenue = monetization (pricing, upsells, bundles, ACV expansion)

Brand and content are cross-cutting, not their own AARRR stage — they serve every stage.

The current-state rubric

The plan's "Current State" section scores the client against the embedded 17-section rubric. Full rubric in references/current-state-rubric.md — it's the source of truth, not a derivative of any external skill.

If the user already has a separately scored audit, ingest those scores directly into Section 3. Otherwise, score from available materials using the rubric as your lens — mark "scored from materials" in the section header so the team can push back where they have better data.

Cross-references — skills this plan integrates with

  1. marketing-ideas — 139 proven marketing tactics. Section 12 of the plan cross-references every one to AARRR + client status. Detail in references/idea-cross-reference.md.
  2. product-marketing — Sets up the foundational .agents/product-marketing.md context file (positioning, ICP, voice). Read this first; Section 2 (Strategic frame) builds on it.
  3. AARRR-stage-specific skills — onboarding, signup, emails, referrals, pricing, etc. The "Marketing operations stack" (Section 11) maps these to AARRR stages.

The plan is opinionated about which skills serve which stages. Full mapping in references/ops-stack-mapping.md.

The marketing operations stack

This is the differentiator of an fCMO-style plan vs. a generic marketing plan. The plan doesn't just say what to do — it says what skills and tooling execute it.

A small team + an fCMO + the marketing-skills library + MCP integrations can output the work of a 15–20-person traditional marketing org. The plan must show this stack explicitly, AARRR-stage by AARRR-stage.

Full mapping in references/ops-stack-mapping.md.

Funding-stage capability unlocks

Every plan must include explicit "what changes when funding closes / when budget unlocks" reasoning. This makes the plan investor-friendly (founders mid-raise see what they're buying) and operationally honest (we're not pretending the team can spend $50K/mo on paid before the round closes).

Standard tiers in references/funding-stage-unlocks.md:

  • Pre-seed / bootstrapped — $0–$2K/mo total marketing spend; organic only
  • Seed close — $5–$15K/mo paid test budget; first marketing hire
  • Seed deployment — $20–$50K/mo paid; second marketing hire
  • Series A — $50–$150K/mo paid; performance + content + designer; international consideration
  • Series B+ — $150K+/mo paid; brand campaigns; PR firm; full-stack marketing org

Use these as anchors. Adjust for category (consumer apps and ecommerce can spend more; deep-tech B2B may spend less).

Setting the budget scientifically

The funding-stage anchors above tell you what's in the ballpark. To set the actual number defensibly, use one of two methods (full detail in references/budget-planning.md):

  1. Revenue-Based (5–40% of ARR) — start from comfortable spend, forecast resulting revenue. Best when historical CAC data exists.
  2. Goal-Based — reverse-engineer the budget from the revenue target. Formula: [(New ARR / (ARPC × 12)) × CAC] / annual retention rate. Best for fundraising or when the goal is fixed.

Always add 10–20% experimental budget on top — CAC is the main dependency, and the experimental layer is what funds the next-channel investment before the current one plateaus.

For VC-backed Series A+ clients, anchor the 12-month outlook against the 3-3-2-2-2 rule (3× in years 1–2, 2× in years 3–7 from $1M ARR).

Growth patterns — the real shape of SaaS growth

Pitch decks show hockey sticks. Real growth is a series of S-curves with plateaus between them. Full framework in references/growth-patterns.md. Key implications for the plan:

  • Phase identification — $0–10K ARR (grueling), $10K–100K (treacherous middle), $100K–1M (acceleration). Section 3 names the current phase; Section 10 sequences the next.
  • Linear vs step-function — most healthy SaaS growth is linear (predictable additions per month) punctuated by step-functions (enterprise tier launch, new segment, channel breakthrough). The plan should describe both honestly — not promise exponential.
  • S-curve layering — Channel × Product × Market. Start the next S-curve while the current one is still growing. Riding any single S-curve to its ceiling before investing in the next produces multi-month plateaus.

Team and agency model

Strategy lives in-house. Execution can — and often should — be outsourced. Full framework in references/team-and-agency-model.md. Three implications for every plan:

  1. First hire is a strategist, not a tactician. Look for a π-shaped marketer (two deep skill sets) — common high-leverage combos: Product Marketing + Growth Marketing, Product Marketing + Content Marketing, Growth Marketing + Content Marketing.
  2. Title conservatively. First marketing hire is almost always Manager or Lead, not VP or CMO. Inflated titles paint the org into a corner when you scale.
  3. Use contractors and small niche agencies for execution. Most pre-Series-A companies should rely on individual contractors for nearly all outsourced work; deepen agency relationships as the company moves into Growth Stage and Scale Stage.
Show full SKILL.md (1,099 more words)Show less

What every plan must customize

A generic plan is a failed plan. Every plan must explicitly customize for:

  1. Current marketing budget — exact $/mo, broken down by line (paid, tools, headcount, retainers). Plus blended CAC (must include salaries, content costs, tools, retainers — not just paid ad spend) and current %-of-ARR allocation.
  2. Unit economics — ARPC, annual retention rate, LTV. These feed the budget math in Section 8 and Section 10.
  3. Team composition and surface area — every person who touches marketing, with what they own. Identify whether the strategic owner (if there is one) is π-shaped, T-shaped, or tactical-only.
  4. What the client is currently doing — by channel, with status (working / not / TBD).
  5. What they've already done that should be acknowledged — past launches, PR moments, content, partnerships. Don't write a plan that ignores work they're proud of.
  6. Phase of SaaS growth — $0–10K ARR / $10K–100K / $100K–1M / $1M+. Each phase has its own binding constraint.
  7. Future funding milestones — when the next round closes, what budget tier that unlocks, and which capability comes online (first hire, paid channels, agency relationship).
  8. The marketing skills mapped to specific moves — every move in the AARRR sections names the skill that executes it.
  9. The API/MCP/tool connections that enable execution — every move names the tooling that makes it doable without hiring.

If you can't confirm any of these in INIT, list them in Section 13's "Open decisions" — never gloss over them. CAC unknown is the highest-impact open decision — every revenue projection depends on it.

Common client-type variations

Plan structure stays consistent. What changes:

  • B2B SaaS — Acquisition leans on SEO + content + outbound + LinkedIn. Activation = signup + product trial. Retention = product engagement + CSM motion. Referral = customer advocacy. Revenue = expansion / NRR.
  • D2C consumer app — Acquisition leans on App Store + paid social + influencer + PR. Activation = onboarding + first session + paywall. Retention = lifecycle email + push. Referral = sharing mechanics. Revenue = subscription + upsell.
  • Hardware-led — Acquisition leans on PR + retail + Amazon + Shopify SEO. Activation = unboxing + setup + first use. Retention = software companion + community. Referral = gifting + reviews. Revenue = blended LTV hardware + accessories + subscription.
  • Marketplace — Activation has two sides (supply + demand). Retention is repeat transaction frequency. Revenue is take-rate × GMV.
  • Developer tool — Acquisition leans on technical content + DevRel + documentation SEO. Activation = first build / first integration. Retention = depth of integration. Referral = team adoption.

Detail in references/client-types.md.

Quality bar

What separates a good plan from a generic one:

Good plan signals:

  • Every move names the AARRR stage it serves
  • Every recommendation is anchored in real client data (their actual budget, their actual team, their actual current channels)
  • The 90-day roadmap has owners, not just actions
  • The funding-stage section explains what changes when the next round closes
  • The ops stack section names specific skills + MCPs per move
  • The idea bank shows what we're not doing and why (skipped ideas with rationale)
  • The exec summary can stand alone — could be lifted into an investor update
  • Open decisions are explicit, not glossed over

Failure modes to avoid:

  • Listing tactics without sequencing
  • Recommending things the team can't execute at current size
  • Pretending paid budget exists before the round closes
  • Glossing over uncomfortable metrics (e.g., churn) instead of naming them as open decisions
  • Generic language ("build a community," "improve SEO") without specific moves
  • Ignoring brand voice — every plan section must respect the client's voice rules
  • Padding the plan with skills/ideas the client doesn't actually need
  • Not acknowledging work the team has already done

Output format

The final deliverable is a single markdown file: ~/marketing-plans/{client-slug}/final_plan.md.

Headers (## 1. Executive summary, etc.) are H2 for clean Notion paste. Tables for any structured comparison (RACI, idea bank, ops stack). Status legend for the idea bank. Internal references to other sections use §N (e.g., "see §5 for Activation detail").

Length expectation: ~8,000–12,000 words for a comprehensive plan. Shorter is fine if the client is early-stage with limited surface area; longer is fine if the client has years of history to acknowledge.

File layout per plan

~/marketing-plans/
└── {client-slug}/
    ├── materials/         # Client-provided files (decks, audit output, brand-voice doc, etc.)
    ├── research.md        # Research record written during INIT
    ├── progress.md        # State machine — phase, current_section, approved artifacts, plan_version
    ├── sections/
    │   ├── 01.md          # Each approved section saved as a canonical artifact
    │   └── ...            # Zero-padded so they sort in order
    └── final_plan.md      # Compiled deliverable (FINALIZE output)

The full schema for progress.md and the resumption decision tree live in references/methodology.md Steps 1.1.1 and 1.1.2.

  • product-marketing — Run first. Captures positioning, ICP, voice in .agents/product-marketing.md so every section of the plan references the same foundation.
  • marketing-ideas — Source of the 139 tactics in Section 12.
  • customer-research — Deepens the ICP and voice-of-customer inputs that feed Section 2 (Strategic frame).
  • onboarding — Deep work on Section 5 (Activation).
  • emails — Deep work on Section 6 (Retention) + onboarding emails in Section 5.
  • referrals — Deep work on Section 7 (Referral).
  • pricing — Deep work on Section 8 (Revenue).
  • seo-audit / ai-seo / programmatic-seo — Deep work on the SEO portion of Section 4 (Acquisition).
  • ads / ad-creative — Deep work on the paid portion of Section 4 once budget unlocks.
  • launch — Deep work on launch moments inside Section 4 / Section 9.

Task-specific questions (used during INIT)

The full intake questionnaire lives in references/methodology.md. The most important questions:

  1. Funding state — What round are you in? How much raised so far? Burn? Runway? Upcoming rounds and timing?
  2. Team — Who are all the people who touch marketing? What does each own? Where are the gaps?
  3. Budget — What's the current monthly marketing spend, broken down by paid acquisition, tools, retainers, headcount? What budget unlocks when the next round closes?
  4. Current channels — What's working today? What's not? What have you not tried yet?
  5. Already done — What past campaigns / launches / content / PR moments should this plan acknowledge?
  6. In-flight — What's drafted but not shipped? What's blocking each item?
  7. Tooling stack — What's wired? Customer.io / Mailchimp / Resend? Shopify / Stripe / App Store Connect? GA4 / Mixpanel / Amplitude? GitHub / Notion / Figma?
  8. Beta or GA? — If product is in beta, what's the GA timeline? Throttling? What gates exist?
  9. The most important thing to fix this quarter — founder's read.
  10. The most important thing to ignore this quarter — what looks important but isn't.

How exhaustive should the plan be?

Default to comprehensive. Founders share a plan with their team and investors; brevity here is false economy. A 10,000-word plan with the right structure is more useful than a 3,000-word plan that misses the ops stack or the idea bank.

That said: don't pad. Every section should be dense, not bloated. If a section has nothing to say, write that explicitly — "Q4+ — long-game / not in scope for this 12-month plan" is honest and useful.

A note on tone

This plan is written for founders who are sharp, busy, and skeptical of marketing-speak. Write like a thoughtful colleague, not a deck-slide-writer. No jargon for jargon's sake. Direct claims, named tradeoffs, explicit assumptions. When unsure, name the open question rather than guessing.

The exec summary should be short enough to read in 60 seconds. The rest should reward deep reading.

© Nexus-JPF, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files (references) in .agents/skills/marketing-plan of Nexus-JPF/note-companion.

  • SKILL.md
  • evals/evals.json
  • references/aarrr-framework.md
  • references/budget-planning.md
  • references/client-types.md
  • references/current-state-rubric.md
  • references/example-quietude.md
  • references/funding-stage-unlocks.md
  • references/growth-patterns.md
  • references/idea-cross-reference.md
  • references/measurement-framework.md
  • references/methodology.md
  • references/ops-stack-mapping.md
  • references/plan-template.md
  • references/team-and-agency-model.md

Open the folder on GitHubat commit 9cad635

Used in 5 other repositories

We found 9 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in Nexus-JPF/note-companion, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Marketing Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Marketing Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Marketing Plan this skillNexus-JPF/note-companion8705 repos~5.2kAutomated safety check: PassMIT
SEO APIseranking/seo-skills161—~4.1kAutomated safety check: PassMIT
SEO Keyword Gap Auditrampstackco/claude-skills945—~2kAutomated safety check: PassMIT
Growth StrategyOpenClaudia/openclaudia-skills713—~2.1kAutomated safety check: PassMIT
Qualify LeadsOthmane-Khadri/YALC-the-GTM-operating-system318—~1.4kAutomated safety check: NotesMIT
Gtm Strategyphuryn/pm-skills27k—~1kAutomated safety check: PassMIT

Similar skills

  • SEO API

    seranking/seo-skills

    SE Ranking API integration architect. An agent skill from seranking/seo-skills.

    161 GitHub stars~4.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • SEO Keyword Gap Audit

    rampstackco/claude-skills

    Find keywords competitors rank for that the target property does not, and prioritize them by opportunity.

    945 GitHub stars~2k tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • Growth Strategy

    OpenClaudia/openclaudia-skills

    Build a growth strategy with frameworks, metrics, and experimentation.

    713 GitHub stars~2.1k tokensUpdated 23 days ago
    Marketing & SEOAuto-check passed
  • Qualify Leads

    Othmane-Khadri/YALC-the-GTM-operating-system

    Run the GTM-OS 7-gate qualification pipeline over a batch of leads from a CSV, JSON, Notion DB, profile-visitors export, post-engagers export, or an existing SQLite result set.

    318 GitHub stars~1.4k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check: notes
  • Gtm Strategy

    phuryn/pm-skills

    Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline.

    27k GitHub stars~1k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Sealeap Amazon Compliance Led Growth

    xjli360/sealeap-amazon-skills

    Build an Amazon growth strategy that treats tax, product safety, account, IP, and logistics compliance as non-negotiable constraints, then compares niches, price bands, operating models, and…

    251 GitHub stars~523 tokensUpdated 13 days ago
    Marketing & SEOAuto-check passed

More from Nexus-JPF/note-companion

All 18 skills in this repo
  • Analytics

    Nexus-JPF/note-companion

    When the user wants to set up, improve, or audit analytics tracking and measurement.

    870 GitHub starsUsed in 7 repos~2.2k tokens
    Auto-check passed
  • Customer Research

    Nexus-JPF/note-companion

    When the user wants to conduct, analyze, or synthesize customer research.

    870 GitHub starsUsed in 6 repos~3.2k tokens
    Auto-check passed
  • Competitor Profiling

    Nexus-JPF/note-companion

    When the user wants to research, profile, or analyze competitors from their URLs.

    870 GitHub starsUsed in 4 repos~3.5k tokens
    Auto-check passed
  • Onboarding

    Nexus-JPF/note-companion

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    870 GitHub starsUsed in 4 repos~1.6k tokens
    Auto-check passed
  • Image

    Nexus-JPF/note-companion

    When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.

    870 GitHub starsUsed in 3 repos~3.9k tokens
    Auto-check passed
  • Video

    Nexus-JPF/note-companion

    When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks.

    870 GitHub starsUsed in 3 repos~3.6k tokens
    Auto-check passed

Categories

Questions about Marketing Plan

What does Marketing Plan do?

When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Marketing Plan is an agent skill from Nexus-JPF/note-companion. When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

When should I use Marketing Plan?

Marketing Plan fits situations like: needs a comprehensive marketing plan for a client; A company they advise; their own product; the user mentions marketing plan.

How do I install Marketing Plan in Claude Code?

Run `npx skills add Nexus-JPF/note-companion --skill marketing-plan -a claude-code`. Or copy the skill folder (.agents/skills/marketing-plan in Nexus-JPF/note-companion) into .claude/skills/marketing-plan in your project. Claude Code loads it when a task matches its description.

How do I install Marketing Plan in Codex?

Run `npx skills add Nexus-JPF/note-companion --skill marketing-plan -a codex`. Or copy the skill folder (.agents/skills/marketing-plan in Nexus-JPF/note-companion) into .agents/skills/marketing-plan in your project. Codex loads it when a task matches its description.

Can I use Marketing Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nexus-JPF/note-companion --skill marketing-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/marketing-plan, .gemini/skills/marketing-plan, .github/skills/marketing-plan and .opencode/skills/marketing-plan in your project.

What does Marketing Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Marketing Plan is instructions for the agent only.

Does Marketing Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Marketing Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Marketing Plan use?

Marketing Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Marketing Plan use?

About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 54k tokens, read only when the agent opens those files.

What are the alternatives to Marketing Plan?

Skills that share tags, products or a category with Marketing Plan: SEO API (seranking/seo-skills, 161 stars), SEO Keyword Gap Audit (rampstackco/claude-skills, 945 stars), Growth Strategy (OpenClaudia/openclaudia-skills, 713 stars) and Qualify Leads (Othmane-Khadri/YALC-the-GTM-operating-system, 318 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Marketing Plan?

Nexus-JPF (a GitHub organization) maintains it in Nexus-JPF/note-companion, which has 870 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: Nexus-JPF/note-companion on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.