Agent skill
win-loss-dataset
Structure for capturing qualitative + quantitative win/loss insights with consistent tagging.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/win-loss-dataset
SKILL.md
Win/Loss Dataset Skill
When to Use
- Running structured win/loss programs.
- Aligning qualitative interviews with CRM metrics.
- Sharing insights across product, sales, pricing, and marketing teams.
Framework
- Data Model – deal metadata (segment, region, product, stage), outcome, competitor, primary driver, secondary driver, confidence.
- Qualitative Tags – categories for pricing, product gaps, implementation, support, brand, relationships.
- Quotes & Evidence – key quotes, call clips, doc references with consent + access controls.
- Analytics Layer – dashboards for driver frequency, trendlines, influence on win rate, revenue impact.
- Action Tracking – link insights to backlog items, status, owner, and due date.
Templates
- Interview note template with pre-defined tags + drop-downs.
- Dataset schema (CSV/Sheet/BI) with validated fields.
- Dashboard layout for driver trends + revenue impact.
Tips
- Keep raw qualitative notes but publish sanitized, anonymized snippets for broader sharing.
- Standardize driver taxonomy every quarter to avoid drift.
- Pair with
run-win-loss-programcommand for automatic dataset updates.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?