SEO API
seranking/seo-skills
SE Ranking API integration architect. An agent skill from seranking/seo-skills.
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
$ npx skills add Nexus-JPF/note-companion --skill marketing-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "marketing-plan" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-plan into .claude/skills/marketing-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Nexus-JPF/note-companion --skill marketing-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/marketing-plan .agents/skills/marketing-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "marketing-plan" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-plan into .agents/skills/marketing-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Nexus-JPF/note-companion --skill marketing-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/marketing-plan .cursor/skills/marketing-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "marketing-plan" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-plan into .cursor/skills/marketing-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Nexus-JPF/note-companion.git --path .agents/skills/marketing-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Nexus-JPF/note-companion --skill marketing-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/marketing-plan .gemini/skills/marketing-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "marketing-plan" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-plan into .gemini/skills/marketing-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Nexus-JPF/note-companion marketing-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Nexus-JPF/note-companion --skill marketing-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/marketing-plan .github/skills/marketing-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "marketing-plan" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-plan into .github/skills/marketing-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Nexus-JPF/note-companion --skill marketing-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/marketing-plan .opencode/skills/marketing-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "marketing-plan" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-plan into .opencode/skills/marketing-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
marketing-planWhen 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. 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.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9cad635. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 2,641 words, ~5,247 tokens.
.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.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).
Invoke this skill when:
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).
/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 full workflow lives in references/methodology.md. Quick summary:
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.
Present each section's draft in chat. For each section you can:
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.
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.
Full template lives in references/plan-template.md. The structure:
references/current-state-rubric.md).marketing-ideas cross-referenced to AARRR + client-specific status (Now / Q2 / Q3+ / Q4+ / Skip).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:
Brand and content are cross-cutting, not their own AARRR stage — they serve every stage.
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.
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.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.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.
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.
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:
Use these as anchors. Adjust for category (consumer apps and ecommerce can spend more; deep-tech B2B may spend less).
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):
[(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).
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:
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:
A generic plan is a failed plan. Every plan must explicitly customize for:
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.
Plan structure stays consistent. What changes:
Detail in references/client-types.md.
What separates a good plan from a generic one:
Good plan signals:
Failure modes to avoid:
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.
~/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.The full intake questionnaire lives in references/methodology.md. The most important questions:
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.
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
SKILL.md and 14 other files (references) in .agents/skills/marketing-plan of Nexus-JPF/note-companion.
Open the folder on GitHubat commit 9cad635
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Marketing Plan this skillNexus-JPF/note-companion | 870 | 5 repos | ~5.2k | Automated safety check: Pass | MIT | |
| SEO APIseranking/seo-skills | 161 | — | ~4.1k | Automated safety check: Pass | MIT | |
| SEO Keyword Gap Auditrampstackco/claude-skills | 945 | — | ~2k | Automated safety check: Pass | MIT | |
| Growth StrategyOpenClaudia/openclaudia-skills | 713 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Qualify LeadsOthmane-Khadri/YALC-the-GTM-operating-system | 318 | — | ~1.4k | Automated safety check: Notes | MIT | |
| Gtm Strategyphuryn/pm-skills | 27k | — | ~1k | Automated safety check: Pass | MIT |
seranking/seo-skills
SE Ranking API integration architect. An agent skill from seranking/seo-skills.
rampstackco/claude-skills
Find keywords competitors rank for that the target property does not, and prioritize them by opportunity.
OpenClaudia/openclaudia-skills
Build a growth strategy with frameworks, metrics, and experimentation.
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.
phuryn/pm-skills
Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline.
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…
Nexus-JPF/note-companion
When the user wants to set up, improve, or audit analytics tracking and measurement.
Nexus-JPF/note-companion
When the user wants to conduct, analyze, or synthesize customer research.
Nexus-JPF/note-companion
When the user wants to research, profile, or analyze competitors from their URLs.
Nexus-JPF/note-companion
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
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.
Nexus-JPF/note-companion
When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks.
Works with
Categories
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Marketing Plan is instructions for the agent only.
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.
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.
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.
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.
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.
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.