These skills were developed and tested on Windows. Mac users will need to adapt file paths and any PowerShell commands before use.
How to invoke a skill
  1. 1.Open Claude Code — available at claude.ai/code, as a desktop app, or via the VS Code / JetBrains extension.
  2. 2.Click View prompt → on any skill below. Copy the file contents and save it as a .md file in your ~/.claude/commands/ folder. The filename becomes the command name.
  3. 3.Open Claude Code in your terminal. Type /skill-name (e.g. /day-prep) and follow any prompts it gives you.
  4. 4.Skills with placeholders like [YOUR_VERTICAL] need to be edited before first use — see the How to Use section for each skill.
Pre-Sales & Discovery
Pre-Sales · Discovery View prompt →
/aep-use-cases
Use Case Mapper
Figure out which AEP capabilities fit an account — and build the story around them.

How to use
Tell Claude the account name and vertical, or paste in discovery notes. It maps pain points to AEP capabilities and returns use case narratives. The more deal context* you have loaded in Claude Code memory, the more specific the output.
Pre-Sales · Discovery View prompt →
/ucx-discovery
Discovery Planner
Run a sharper discovery conversation and walk out with something you can actually use.

How to use
Tell Claude the account name and which products are in scope. It returns a structured set of discovery questions and a formatted output doc you can use in follow-up. Include the Unified CX Playbook skill below for full play context.
Pre-Sales · Reference View prompt →
/unified-cx
Unified CX Playbook
Your in-session reference for all three UCX plays — personas, use cases, and competitive notes included.

How to use
Load this at the start of any UCX-focused session — no prompt needed. Claude treats the play framework, persona maps, and use cases as background context for everything that follows. Before first use, fill in the [YOUR_VERTICAL] placeholders throughout the file.
Pre-Sales · Brand View prompt →
/brand-guardian
Brand Compliance Checker
Catch brand and compliance issues before they reach the customer.

How to use
Share copy, design specs, or channel examples and invoke. Claude audits against your demo brand's guidelines and returns a compliance report with flagged issues. Before first use, create a brand guidelines file and update the file path in the skill.
Deal & Account Work
Deal Management View prompt →
/deal-update
Weekly Deal Digest
Turn a week's worth of notes into a clean, structured portfolio update.

How to use
Drop in notes from your week — fragments, meeting recaps, anything you have. Tell Claude one deal or all. It returns structured deal blocks or a summary table. Before first use, update the Active Accounts list in the skill file and load your deal context* into Claude Code memory.
Deal Management View prompt →
/day-prep
Daily Meeting Brief
Walk into every meeting knowing what matters.

How to use
Paste your calendar for the day in any format — Outlook list, Copilot export, rough notes. Claude maps each meeting to known context and returns a tight per-meeting brief. Load deal memory and stakeholder profiles into Claude Code first — that's what the briefs are built from.
Visual Input
Visual Input View prompt →
/ss
Screenshot Action
Point Claude at a screenshot and tell it what to do.

How to use
Type /ss followed by what you want done — /ss explain, /ss fix, /ss 3 summarize. Claude reads your most recent screenshot (or more if you specify a count) and acts on it. This skill assumes your screenshots are saved to a single folder on your machine. Before first use, open the skill file and set that folder path — Claude will always look there.
Visual Input View prompt →
/scr
Recording Analyst
Point Claude at a screen recording and tell it what to do.

How to use
Type /scr followed by what you want done — /scr explain, /scr fix, /scr 2 summarize. Claude extracts frames from your most recent screen recording and acts on them. This skill assumes your recordings are saved to a single folder on your machine. Before first use, open the skill file and set that folder path. ffmpeg is required to extract frames — on Windows it will be auto-installed if missing; Mac users will need to install it manually (brew install ffmpeg).
* Deal context is the per-account information Claude uses to personalize output — stage, stakeholders, competitive dynamics, open questions, and more. To build it, share what you have: meeting notes, emails, presentations, call recaps. Claude reads them, extracts what's relevant, and stores it in a file it reads at the start of every session. Skills that need account context pull from it automatically — you don't re-explain your deals each time.