From gtm-cowork-skills
Create comprehensive Key Account Plans for clients/prospects. Use this skill whenever the user mentions 'account plan', 'key account', 'account planning', 'strategic account', 'client plan', 'customer success plan', or wants to create a structured plan for managing an important client relationship. Also trigger when users ask to 'plan for [company name]', 'review account strategy', 'prepare account review', or mention MEDDPICC/MEDDPIC analysis alongside client planning. This skill pulls data from Attio CRM (company records, contacts, deals, notes, emails, call recordings, MEDDPICC scores) and Google Drive, then produces a polished .docx Key Account Plan document and creates summary notes + tasks back in Attio. Even if the user just names a company and says something like 'let's do an account plan' or 'prepare for my QBR with [company]', use this skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gtm-cowork-skills:key-account-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill creates comprehensive Key Account Plans following a structured 5-step framework. It pulls data from multiple sources (Attio CRM, Google Drive, email history, call recordings), synthesizes it into a professional Word document, and creates actionable notes and tasks back in Attio.
This skill creates comprehensive Key Account Plans following a structured 5-step framework. It pulls data from multiple sources (Attio CRM, Google Drive, email history, call recordings), synthesizes it into a professional Word document, and creates actionable notes and tasks back in Attio.
The output is a complete strategic document that helps account managers understand their client deeply, set aligned objectives, build action plans, implement effectively, and continuously improve the relationship.
This skill requires access to:
If any of these are unavailable, inform the user and proceed with what's available. The skill degrades gracefully — even with just Attio data, you can produce a useful plan.
Before writing anything, gather all available intelligence. This phase is about closing knowledge gaps.
search-records(object: "companies", query: "<company name>")
Pick the most complete record (look for the one with domains, team members, and deal associations). Note the record_id — you'll use it throughout.
Launch these queries simultaneously to save time:
get-records-by-ids for all people linked via the team attributeget-records-by-ids for all associated_dealssemantic-search-notes with the company name + keywords like "account plan", "strategy", "partnership"semantic-search-emails with the company name + deal-related keywordssearch-call-recordings-by-metadata filtered to the company recordgoogle_drive_search with fullText contains '<company name>'search-meetings filtered to the company recordFor the most relevant emails (especially recent ones and those with deal context), fetch full content with get-email-content. For any call recordings found, fetch transcripts with get-call-recording.
Check the deal record for MEDDPICC fields (metrics, decision criteria, competition, etc.). These are gold for the account plan — they tell you exactly where the knowledge gaps are.
This is a critical but often skipped step. Before writing the plan:
[ACTION NEEDED] markers in the document for contacts that need LinkedIn verificationThe goal is to ensure the plan reflects the actual current org chart, not stale data.
Read the docx skill (/mnt/.claude/skills/docx/SKILL.md) before generating the document. Follow its patterns for docx-js, validation, and formatting.
The document follows a 5-step framework. Each step should be populated with real data from Phase 1, supplemented by strategic analysis.
Cover Page:
Step 1: Account Overview — The foundation. Gather everything you need for smart strategic moves.
[ACTION NEEDED] for LinkedIn verification.Step 2: Objectives — Validate assumptions and align with client priorities.
Step 3: Action Plan — Ambitious but achievable steps to move the relationship forward.
Step 4: Implementation — Where plans meet reality.
Step 5: Review and Optimise — Continuous improvement loop.
Use these formatting conventions:
1B4F72, subheader blue 2E86C1, alt row EBF5FBCCCCCC, cell margins {top: 80, bottom: 80, left: 120, right: 120}After the document is created, write a summary note back to the Attio company record using create-note. The note should include:
Use Attio's supported markdown: headings (#, ##), lists (-, ), bold (**), italic (), strikethrough (~~), highlight (==), links.
Create tasks in Attio for the most urgent action items (typically 2-4 per account):
Link each task to the company record and assign to the appropriate workspace member.
When the user asks for plans for multiple companies, process them in parallel where possible:
[ACTION NEEDED] or [GAP] markers. It's better to acknowledge what you don't know than to fill gaps with fluff.npx claudepluginhub extruct-ai/gtm-cowork-skillsGuides enterprise account planning and execution, including MEDDICC qualification, stakeholder management, mutual action plans (MAPs), and deal health tracking via 'stale MAP equals dead deal' rule. Use for complex sales cycles over 60 days.
Generates scannable HTML account dossiers and call prep documents for internal sales use, with optional brand kit styling.
Persistent intelligence layer that accumulates deal knowledge, competitive intel, product context, and team patterns over time — making every other skill smarter with use. This skill should ALWAYS be checked at the start of any GTM-related task. It reads from and writes to a structured knowledge base so that insights from one conversation carry into the next. Use this skill on every interaction that involves sales, marketing, CS, partnerships, or RevOps context. Also trigger proactively when the user shares deal outcomes, competitive intel, product updates, rep feedback, or customer insights — capture it even if they didn't ask you to.