mohitagw15856/account-plan
skills/account-plan/SKILL.md
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills account-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 9, 2026, 7:39 AM121.2s1 file scanned
SKILL.md
- name:
- account-plan
- description:
- Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
Account Plan Skill
Produces a structured account plan — the document that separates account managers who grow accounts from those who just service them.
Required Inputs
- Account name
- Current ARR / revenue
- Contract renewal date
- Key contacts (names, roles, relationship strength)
- Products/services currently in use
- Known opportunities or expansion areas
- Known risks
- Planning horizon (6 / 12 / 24 months)
Output Structure
Account Plan: [Account Name]
Account Manager: [Name] | Period: [Date range]
Account Snapshot
| Metric | Current | Target (EOY) | |---|---|---| | ARR / Revenue | £[amount] | £[target] | | NPS / Health score | [Score] | [Target] | | Products in use | [List] | [Expansion targets] | | Renewal date | [Date] | — | | Risk level | Low / Medium / High | — |
Relationship Map
| Name | Title | Influence | Relationship | Notes | |---|---|---|---|---| | [Name] | [Role] | Decision maker / Influencer / User | Strong / Neutral / Weak | [Insight] |
Relationship gaps: [Who we do not have access to that we should] Executive sponsor: [Do we have one? If not — who could become one?]
Why They Stay (Retention Anchors)
[2-3 specific reasons this account renews. If the list is short, that is the risk signal.]
Growth Opportunities
| Opportunity | Product | Est. Value | Timeline | Next Action | |---|---|---|---|---| | [Opportunity] | [Product] | £[value] | [Q/Year] | [Specific action] |
Whitespace: What products do we have that this account does not use, and why?
Risks and Mitigation
| Risk | Likelihood | Impact | Mitigation | Owner | |---|---|---|---|---| | [Risk] | H/M/L | H/M/L | [Action] | [Name] |
90-Day Action Plan
| Action | Why | Owner | Due | |---|---|---|---| | [Specific action] | [Why it matters] | [Name] | [Date] |
Next QBR / EBR: [Date — if no EBR cadence, flag as a risk]
Success Criteria
At end of [period]:
- Renewed at or above current ARR
- [Expansion opportunity] progressed to [stage]
- Health score moved from [current] to [target]
Anti-Patterns
- [ ] Do not list only executive contacts in the relationship map — champions and day-to-day users are often more influential on renewal decisions
- [ ] Do not set growth opportunity estimates without a basis — even rough ARR values prevent the plan from being treated seriously
- [ ] Do not treat "no known risks" as acceptable — if no risks are identified, the plan hasn't been scrutinised honestly
- [ ] Do not write 90-day actions as vague aspirations ("strengthen the relationship") — each action must specify a call, meeting, or deliverable with a named owner
Quality Checks
- [ ] Relationship map identifies decision-makers, influencers, and any relationship gaps
- [ ] Risks all have mitigation actions and named owners
- [ ] Growth opportunities include estimated value (even roughly)
- [ ] 90-day actions are specific (not "have a call" — what call, with whom, to achieve what)
- [ ] Success criteria are measurable at the end of the planning period
Related Skills
mohitagw15856/competitor-signal-tracker
development
VerifiedTrustedCommunity
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners.
951SKILL.mdUpdated Apr 21, 2026
mohitagw15856/community-management-playbook
development
VerifiedTrustedCommunity
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
946SKILL.mdUpdated May 28, 2026
mohitagw15856/claude-superpowers
development
VerifiedTrustedCommunity
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
946SKILL.mdUpdated May 28, 2026
mohitagw15856/aeo-optimizer
development
VerifiedTrustedCommunity
Optimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
946SKILL.mdUpdated May 28, 2026