Marketing Plan
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
Strategic account planning and execution for enterprise deals.
$ npx skills add github/awesome-copilot --skill gtm-enterprise-account-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot gtm-enterprise-account-planning --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/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gtm-enterprise-account-planning .claude/skills/gtm-enterprise-account-planning && 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 "gtm-enterprise-account-planning" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-enterprise-account-planning into .claude/skills/gtm-enterprise-account-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-enterprise-account-planning", 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/github/awesome-copilot/tree/main/skills/gtm-enterprise-account-planningType 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 github/awesome-copilot --skill gtm-enterprise-account-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot gtm-enterprise-account-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gtm-enterprise-account-planning .agents/skills/gtm-enterprise-account-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gtm-enterprise-account-planning" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-enterprise-account-planning into .agents/skills/gtm-enterprise-account-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-enterprise-account-planning", 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 github/awesome-copilot --skill gtm-enterprise-account-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot gtm-enterprise-account-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gtm-enterprise-account-planning .cursor/skills/gtm-enterprise-account-planning && 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 "gtm-enterprise-account-planning" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-enterprise-account-planning into .cursor/skills/gtm-enterprise-account-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-enterprise-account-planning", 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/github/awesome-copilot.git --path skills/gtm-enterprise-account-planning--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 github/awesome-copilot --skill gtm-enterprise-account-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot gtm-enterprise-account-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gtm-enterprise-account-planning .gemini/skills/gtm-enterprise-account-planning && 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 "gtm-enterprise-account-planning" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-enterprise-account-planning into .gemini/skills/gtm-enterprise-account-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-enterprise-account-planning", 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 github/awesome-copilot gtm-enterprise-account-planningInstalls 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 github/awesome-copilot --skill gtm-enterprise-account-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gtm-enterprise-account-planning .github/skills/gtm-enterprise-account-planning && 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 "gtm-enterprise-account-planning" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-enterprise-account-planning into .github/skills/gtm-enterprise-account-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-enterprise-account-planning", 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 github/awesome-copilot --skill gtm-enterprise-account-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot gtm-enterprise-account-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gtm-enterprise-account-planning .opencode/skills/gtm-enterprise-account-planning && 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 "gtm-enterprise-account-planning" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-enterprise-account-planning into .opencode/skills/gtm-enterprise-account-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-enterprise-account-planning", 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.
gtm-enterprise-account-planningStrategic account planning and execution for enterprise deals.
Gtm Enterprise Account Planning is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Strategic account planning and execution for enterprise deals. Use when planning complex sales cycles, managing multiple stakeholders, applying MEDDICC qualification, tracking deal health, or building mutual action plans. Includes the "stale MAP equals dead deal" pattern.
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Go-to-market strategy. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 82701c2. 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.
Gtm Enterprise Account Planning loads about 3.9k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 2,067 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 github/awesome-copilot at commit 82701c2, republished under its MIT licence (© github). 2,067 words, ~3,912 tokens.
.claude/skills/gtm-enterprise-account-planning/SKILL.md (or your agent's skills folder).Strategic account planning and execution for enterprise deals. Turn complex sales cycles into systematic wins — or at least know when they're dying before you waste months.
Triggers:
Context:
The Pattern I've Seen:
The Mutual Action Plan (MAP) is the single best indicator of deal health. Not pipeline stage. Not verbal commitments. Not "they love the product."
The MAP tells you everything:
Healthy deal:
Dying deal:
Why This Happens:
When a deal is real, the customer wants it to happen. They're doing work. They're involving stakeholders. They're moving through their process.
When a deal is dying, you're doing all the work. They're "too busy." They'll "get back to you next week." The economic buyer is "traveling."
The 3-Week Rule:
If your MAP hasn't been updated in 3 weeks, the deal is dead — you just don't know it yet. I've never seen a deal close with a stale MAP. Not once in 11 years.
What to Do:
Week 1 of silence: Send MAP update: "Here's what we've completed. What's your status on [specific customer action]?"
Week 2 of silence: Escalate to champion: "Haven't heard back on MAP. Are we still on track for [date]? If priorities shifted, let me know."
Week 3 of silence: Qualify out or reset: "It seems like timing might not be right. Should we pause and reconnect in [timeframe], or is there a blocker I can help with?"
Common Mistake:
Keeping deals in pipeline because "they said they want it." Verbal interest ≠ action. If they're not doing work, they're not buying.
The Pattern:
You're 8 weeks into a deal. POC went great. Champion loves you. Technical validation complete. You send the proposal.
Then: radio silence.
What happened? You never met the Economic Buyer.
The Economic Buyer (EB) is the person who:
Not:
Why Deals Die Without EB Access:
You built the business case with your champion's assumptions. But the EB has different priorities:
When you send proposal to EB through the champion, EB sees:
Result: Deal stalls or dies.
The Framework: EB Validation Checklist
Before sending proposal, validate:
If you answered "no" to any, don't send the proposal yet.
How to Get EB Access:
Ask your champion: "Before we finalize pricing, I'd love 15 minutes with [EB name] to make sure we're aligned on outcomes and timeline. Can you intro us?"
If champion blocks: "I can handle that, you don't need to talk to them" → This is a red flag. Either champion doesn't have access (not a real champion) or they're afraid EB will kill the deal (which means deal is weak).
Push back: "I totally understand. At the same time, I want to make sure [EB] sees the full value before seeing the price. In my experience, when economic buyers aren't involved early, deals get delayed in procurement. Can we do a quick alignment call?"
Common Mistake:
Treating EB meeting as "nice to have." It's mandatory for any deal >$50K. No EB access = no deal.
The Pattern:
Enterprise software purchases are made by committees. But committees don't buy. People buy.
And people buy for personal reasons:
Framework: Personal Win Identification
For each stakeholder, map:
Professional Win:
Professional Risk:
Personal Motivations:
Example: VP of Engineering
Professional Win:
Professional Risk:
Personal Motivations:
How This Changes Your Pitch:
Generic pitch: "Our platform improves incident response time by 40%."
Personal win pitch: "You mentioned the on-call burden is burning out your team. We've seen teams reduce on-call pages by 40% in the first month, which helps with retention. And since you're focused on uptime metrics for the board, the improved response time shows up immediately in your QBR dashboards."
The Difference:
Generic = business case Personal = career case
Both matter. But personal wins close deals.
Common Mistake:
Selling only to the business problem. "This saves money. This improves efficiency." That's necessary but not sufficient. People need to see what's in it for them personally.
A complete account plan has four interconnected pieces. Each feeds the others.
Component 1: Account Summary
Component 2: Org Chart
Component 3: Opportunity Plan (MEDDICC)
Plus: Issues/Risks table with mitigation plans, help needed, responsible parties
Component 4: Mutual Action Plan (MAP)
Decision Criteria:
Full account plans worth investment for top 10-20% of accounts by potential deal size. For rest, use simplified version (summary + MEDDICC + next steps).
Common Mistakes:
Before engaging strategic account, quantify their investment in your domain via LinkedIn.
How to Execute:
Why This Works:
If a company has 50 employees with "SRE" in their profile, they're mature in site reliability. If they have 2, they're not ready for advanced observability tools.
This tells you:
Example:
Searching "[Company] + DevOps":
Searching "[Company] + SRE":
Common Mistakes:
Enterprise sales follows defined stages with clear exit criteria. Don't advance stages without meeting criteria.
Stage 0 — Pipeline Generation: Prospecting → Qualified interest confirmed Stage 1 — Discovery: Environment/pain/requirements → Pain identified, stakeholders mapped Stage 2 — Demonstrating: Product demo, champion building → Champion identified Stage 3 — Proving Value: POC/trial → Technical validation complete Stage 4 — Proposal: Pricing, terms, scope → Proposal delivered, EB aligned Stage 5 — Paper Process: Legal, procurement, security → Approvals secured Stage 6 — Closed Won: Deal signed → Customer success handoff
Exit Criteria Matter:
Don't move from Stage 2 → Stage 3 until you have a champion. Don't move from Stage 3 → Stage 4 until POC success criteria are met. Don't move from Stage 4 → Stage 5 until EB has approved.
Common Mistake:
Advancing stages based on activity, not criteria. "We demoed, so we're in Stage 3" — but if they haven't agreed to POC, you're still in Stage 2.
Is deal size above average ACV?
├─ No → Simplified plan (summary + MEDDICC)
└─ Yes → Continue...
│
Sales cycle >60 days?
├─ Yes → Full account plan
└─ No → Simplified planIs MAP being updated weekly?
├─ Yes → Healthy
└─ No → Continue...
│
Has it been >3 weeks since last MAP update?
├─ Yes → Dead deal (qualify out or reset)
└─ No → At risk (escalate to champion)Have you met the Economic Buyer?
├─ No → Don't send yet (get EB access first)
└─ Yes → Continue...
│
Does EB agree on problem and success metrics?
├─ Yes → Send proposal
└─ No → Align with EB before sending1. Creating account plan too late
2. MEDDICC filled with assumptions
3. Stale Mutual Action Plan
4. Mapping only the buyer
5. Ignoring personal wins
6. Not tracking deal health
7. Skipping champion validation
MAP Health Check:
MEDDICC Validation:
Personal Win Questions:
Account Plan Checklist:
Based on enterprise sales at a platform company during hypergrowth, with patterns from closing strategic accounts, navigating complex procurement processes, and learning the hard way that stale MAPs = dead deals. Not theory — lessons from watching deals die because we didn't track health metrics and closing deals because we validated EB alignment early.
© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/gtm-enterprise-account-planning of github/awesome-copilot.
Open the folder on GitHubat commit 82701c2
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.
Gtm Enterprise Account Planning 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 |
|---|---|---|---|---|---|---|
| Gtm Enterprise Account Planning this skillgithub/awesome-copilot | 40k | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Marketing PlanNexus-JPF/note-companion | 870 | 5 repos | ~5.2k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Jaredrhod Marketingjaredrhod/ai-marketing-skills | 282 | — | ~584 | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Traffic Acquisitionvivy-yi/xiaohongshu-skills | 478 | 1 repos | ~4k | Automated safety check: Pass | None |
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
jaredrhod/ai-marketing-skills
Run any marketing task the way jaredrhod actually runs it. An agent skill from jaredrhod/ai-marketing-skills.
vivy-yi/xiaohongshu-skills
A skill your agent uses when driving traffic to Xiaohongshu account from external sources, acquiring new followers beyond organic discovery, implementing multi-platform growth strategy, or scaling…
nexscope-ai/Amazon-Skills
Comprehensive product research and opportunity analysis for Amazon sellers.
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Categories
Strategic account planning and execution for enterprise deals. Gtm Enterprise Account Planning is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Strategic account planning and execution for enterprise deals.
Gtm Enterprise Account Planning fits situations like: planning complex sales cycles; managing multiple stakeholders; applying MEDDICC qualification; tracking deal health.
Run `npx skills add github/awesome-copilot --skill gtm-enterprise-account-planning -a claude-code`. Or copy the skill folder (skills/gtm-enterprise-account-planning in github/awesome-copilot) into .claude/skills/gtm-enterprise-account-planning in your project. Claude Code loads it when a task matches its description.
Run `npx skills add github/awesome-copilot --skill gtm-enterprise-account-planning -a codex`. Or copy the skill folder (skills/gtm-enterprise-account-planning in github/awesome-copilot) into .agents/skills/gtm-enterprise-account-planning 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 github/awesome-copilot --skill gtm-enterprise-account-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gtm-enterprise-account-planning, .gemini/skills/gtm-enterprise-account-planning, .github/skills/gtm-enterprise-account-planning and .opencode/skills/gtm-enterprise-account-planning in your project.
SKILL.md names no scripts, command-line tools or credentials: Gtm Enterprise Account Planning 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.
Gtm Enterprise Account Planning is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Gtm Enterprise Account Planning: Marketing Plan (Nexus-JPF/note-companion, 870 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars) and Jaredrhod Marketing (jaredrhod/ai-marketing-skills, 282 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,830 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 9, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.