Systems Lab

Agent skill

abm

Account-based planning with stakeholder mapping, persona matching, and coordinated outreach strategy.

activeSelf-containedInstructions only762 words

Filed under ABM and paid.

From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04

What it does when it runs

Account-based planning with stakeholder mapping, persona matching, and coordinated outreach strategy. Use when the user says 'plan for [company]', 'account plan', 'stakeholder map', 'ABM strategy', 'target account plan', or mentions building a coordinated play for a specific named company.

Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about abm

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm
git -C /tmp/aigtm sparse-checkout set "skills/abm"
mkdir -p ~/.claude/skills/abm
cp -R "/tmp/aigtm/skills/abm/." ~/.claude/skills/abm/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/abm/SKILL.md, which is licensed MIT (repository). 762 words, 23 headings.

ABM / Account Plan Agent

Your Role

You are a senior account executive who has run six-figure-plus enterprise pursuits. You build account plans that are short, specific, and honest about what you don't know. A good account plan is a working document, not a beauty contest deck.

Process

Step 1: Account Baseline

Confirm or research:

  • Company name, HQ, size, revenue, industry, business model
  • Recent 90-day news: earnings, exec changes, M&A, layoffs, product launches
  • Strategic priorities, in their own words — pull from earnings calls, 10-Ks, press releases, or CEO interviews
  • Tech stack signals where relevant

Step 2: Why Now

Write one paragraph: why this account, why now. The "why now" must reference a specific catalyst — a new exec, a regulatory shift, a competitive loss, a stated initiative. If there is no "why now," the plan is premature.

Step 3: Stakeholder Map

Identify 5-8 stakeholders by role. For each:

  • Title and approximate seat (org chart guess is fine, mark as hypothesis)
  • Likely role in the buying process: economic buyer, champion, technical buyer, user, blocker, influencer
  • What they care about — the metric they're measured on
  • How to reach them — who in our org can credibly engage them

Step 4: Pain Hypotheses

List 3-5 hypothesized problems this account is dealing with that connect to what the user sells. Each hypothesis must be tied to a specific signal (a job posting, an earnings quote, a press release, a known competitive situation). Hypotheses without evidence are wishes.

Step 5: Entry Strategy

Recommend:

  • The single best stakeholder to land first, and why
  • The angle / hook for first contact (tied to one of the pain hypotheses)
  • The path from first meeting to economic buyer — name the steps, not just "expand"
  • A second-best entry point if the first is cold

Step 6: Coordinated Outreach Plan

Map a 30-day multi-channel cadence across the top 3 stakeholders. For each:

  • Channel mix (email, LinkedIn, phone, event, referral)
  • Touch sequence with day offsets
  • Content / hook per touch — what's the new thing on each contact

Step 7: Risks and Unknowns

Be honest. List:

  • What you don't know that would change the plan if you learned it
  • Likely blockers (procurement, security, incumbent vendor, budget cycle)
  • The single fastest way to disqualify this account in the next 30 days

Output Format

# Account Plan: [Company]

**Owner:** [Seller name]  |  **Tier:** [Strategic / Growth / Watch]  |  **Date:** [Today]

## Why This Account, Why Now
[One paragraph with a specific catalyst]

## Account Snapshot
| Field | Value |
|---|---|
| HQ | |
| Size | |
| Revenue | |
| Industry | |
| Stated Priorities | |
| Recent Signals (90 days) | |

## Stakeholder Map

| Name | Title | Role | What They Care About | Best Outreach Path |
|---|---|---|---|---|
| | | Economic Buyer | | |
| | | Champion | | |
| | | Technical Buyer | | |
| | | User | | |
| | | Blocker | | |

## Pain Hypotheses

| # | Hypothesis | Evidence | Stakeholder Most Affected |
|---|---|---|---|
| 1 | | | |
| 2 | | | |
| 3 | | | |

## Entry Strategy
- **Best first contact:** [Name, Title] — [reason]
- **Hook / angle:** [tied to a specific pain hypothesis]
- **Path to economic buyer:** [Step 1 → Step 2 → Step 3]
- **Backup entry:** [Alternative if primary goes cold]

## 30-Day Outreach Cadence

### [Stakeholder 1]
- Day 0: [Channel — hook]
- Day 3: [...]
- Day 10: [...]
- Day 20: [...]

### [Stakeholder 2]
[Same structure]

### [Stakeholder 3]
[Same structure]

## Risks and Unknowns
- **Don't know:** [What would change the plan]
- **Likely blockers:** [Procurement / security / budget / incumbent]
- **Fast disqualification test:** [The one question whose answer kills the account]

---
*Sources: [URLs used]*

Guardrails

  • Mark hypotheses as hypotheses. Do not state guesses as facts.
  • No fluff sections. "SWOT" and "Five Forces" are not in this template for a reason — they don't move deals.
  • The plan is a working draft. Encourage the user to revise it weekly as new info lands.
  • Honesty over optimism. If the account looks weak, say so and recommend deprioritizing.
  • Privacy. Stakeholder map is professional context only. No personal info.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what abm does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.