Prioritize Accounts
Use when the user asks which existing accounts to work now, which leads are hottest in...
Install
npx skills add XiaomiMiMo/MiMo-Code --skill prioritize-accounts -g -a claude-code -y- Repository
- XiaomiMiMo/MiMo-Code13.7k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when the user asks which existing accounts to work now, which leads are hottest in a grounded list or pipeline, how to rank a territory, book, pipeline, ICP list, or account list, where to focus this week, or what rep-ready next actions to take. Prioritize accounts using current evidence, suppress or account for in-flight motion, and identify reachable contacts when supported. Use enrichment instead for net-new company discovery or missing-data completion.
Prioritize Accounts
Prepare a sales person with a small, evidence-grounded account action view: which accounts deserve attention now, why they rose, who to engage, and what safe next step to take.
Common Skill Instructions
MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.
Account Ranking
Use this priority order when the account set, ranking basis, or motion is ambiguous.
- Explicit user request, named account list, owner scope, territory, ranking basis, or stated preference
- CRM-backed open pipeline or user-provided CRM-equivalent account truth
- Accounts with a source-grounded why-now signal, clear net_new or expansion branch, and reachable primary contact
- Accounts with meaningful deal value, timing, momentum, risk, or actionability
- Accounts without active motion, duplicate outreach risk, ownership ambiguity, or another hard suppressor
- Accounts that fit the rep's stated capacity window
Default broad requests to open pipeline deals, deal value / ACV adjusted by timing, momentum, risk, and actionability, with a mixed motion goal. Do not create the candidate universe from enrichment, public context, calendar, or messages alone.
Key Dependency Categories
It is critical to use all of these categories if you can, if any relevant plugins or connectors are available, to ensure high quality responses. If the user declines, or connectors aren't available, state that limitation in your final answer. You can also use other relevant connectors as needed.
