Sdr account prioritization plan
Skill amplemarket/skills/skills/sdr-account-prioritization-plan
Help SDRs figure out which accounts to focus on and how to break into them -- combining internal engagement data with external signals to prioritize accounts and plan next moves.From its SKILL.md
npx -y skills add amplemarket/skills --skill sdr-account-prioritization-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.9 KB, 829 tokens by cl100k_base, as published. Nobody here has run it
SDR Account Prioritization Plan
Help SDRs figure out which accounts to focus on and how to break into them -- combining internal engagement data with external signals to prioritize accounts and plan next moves.
Instructions
When an SDR wants to plan their account work, pull account data, enrich with external signals, and build a prioritized penetration plan with specific next steps per account.
Steps
-
Identify the SDR's accounts. Either:
- Use
mcp__claude_ai_Amplemarket__list_accountsfiltered by the SDR's email to find accounts they own - Or ask the SDR for the accounts or domains they want to review
- Use
-
Gather internal data by calling
mcp__claude_ai_Amplemarket__get_accountfor each account. This gives engagement stats, AI-generated insights, and known contacts. -
Gather external signals to identify which accounts have timely reasons to engage now. Use
mcp__claude_ai_Amplemarket__search_companiesorWebSearchto check for:- Recent funding rounds
- Leadership changes
- Hiring surges
- Product launches or expansions
- Any other buying signals
-
Prioritize accounts. Rank by combining:
- Engagement signals -- which accounts are showing life? Recent opens, replies, interested signals from the AI insights
- External signals -- which accounts have timely triggers that create an opening?
- Account fit -- which accounts are the best ICP match based on firmographics and insights?
The best accounts to focus on are the ones where internal engagement and external signals converge.
-
For each priority account, build a penetration plan:
- What do we know? -- summarize engagement history and AI insights (interest level, pain points, current solution, competitors)
- What don't we know yet? -- gaps in understanding, unanswered questions, missing information
- Who should we go after? -- check existing contacts via
mcp__claude_ai_Amplemarket__get_contactsfor interaction history, and usemcp__claude_ai_Amplemarket__search_peopleto find new contacts who haven't been reached yet. Consider who's already been contacted, what happened, and who's missing. - What's the angle? -- based on engagement insights + external signals, what's the best way in?
-
Help with execution when asked. If the SDR wants to act:
- Find contacts at an account via
mcp__claude_ai_Amplemarket__search_people - Enrich a specific person via
mcp__claude_ai_Amplemarket__enrich_person - Create a lead list from discovered contacts via
mcp__claude_ai_Amplemarket__create_lead_list
- Find contacts at an account via
-
Present a well-formatted penetration plan. Lead with the prioritized account list, then give per-account plans. Keep it action-oriented -- the SDR should finish reading and know exactly who to reach out to and why.
Examples
User prompt: "Help me plan my week -- which accounts should I focus on?"
Simple example output: The agent pulls 20 accounts, checks engagement data and external signals. Surfaces 5 priority accounts: 2 with recent positive engagement (warm replies, should follow up), 2 with strong external signals (one just raised Series B, another hired a new VP Sales), and 1 where engagement + external signals converge (interested reply last week AND the company just announced expansion). For each, it shows what we know, who to target, and the recommended angle.
Troubleshooting
| Problem | Solution |
|---|---|
| Too many accounts | Prioritize the top 5-10 based on signal strength. Offer to plan the rest in a follow-up. |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most roadmap strategy skills give in 829 tokens
Counted across 614 of the 719 authors here whose files we hold, read 2026-09-06
- Check for product marketing context firstin 39 of 614, across 16 files
- Use compact with a custom summaryin 32 of 614, across 16 files
- Compact after planningin 30 of 614, across 16 files
- Do not compact mid-implementationin 30 of 614, across 17 files
- Structure launch marketing across three channel typesin 21 of 614, across 5 files
- Read the compaction suggestionin 20 of 614, across 10 files
- Write before compactingin 17 of 614, across 11 files
- Write important context to files before compactingin 16 of 614, across 5 files
- Recruit early users one-on-onein 16 of 614, across 3 files
- Identify 3-5 core content pillarsin 15 of 614, across 9 files
- Target a specific keyword or questionin 14 of 614, across 4 files
- Stagger announcements to maintain momentumin 14 of 614, across 4 files
Said here and by no other author read
- Identify the SDR accounts
- Gather internal data for each account
- Gather external signals for accounts
- Prioritize accounts by signal convergence
- Build a penetration plan for priority accounts
- Present a well-formatted penetration plan
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.