Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:31:40 +08:00
commit 919a559763
13 changed files with 420 additions and 0 deletions

View File

@@ -0,0 +1,31 @@
---
name: battlecard-system
description: Use to standardize competitive positioning, objection handling, and talk
tracks across teams.
---
# Battlecard System Skill
## When to Use
- Launching new competitive programs or product updates.
- Training teams ahead of major deals or campaigns.
- Refreshing differentiators based on win/loss analysis.
## Framework
1. **Competitive Intel** capture strengths, weaknesses, proof, and trigger signals per competitor.
2. **Messaging Pillars** align headline, supporting proof, and objection responses.
3. **Delivery Format** deck, one-pager, LMS module, and short-form scripts.
4. **Distribution & Access** tag assets, set expiration dates, and embed in enablement tools.
5. **Feedback Loop** collect field feedback, update win/loss data, and refresh quarterly.
## Templates
- Battlecard layout (overview, talk track, objections, proof points).
- Objection handling matrix.
- Competitive win/loss capture form.
## Tips
- Keep “permission to win” statements crisp; avoid feature dumping.
- Include audio/video snippets from top performers.
- Align with legal/product teams before publishing sensitive data.
---

View File

@@ -0,0 +1,31 @@
---
name: messaging-framework
description: Use to structure value propositions, proof points, and objection responses
for enablement assets.
---
# Enablement Messaging Framework Skill
## When to Use
- Creating new sales plays, launch content, or talk tracks.
- Refreshing messaging for competitive shifts or product updates.
- Enabling partners or success teams with consistent narratives.
## Framework
1. **Audience & Pain** define persona, current pains, and desired state.
2. **Value Pillars** articulate 2-3 core benefits with supporting proof.
3. **Proof & Stories** attach metrics, customer quotes, ROI snippets, demos.
4. **Objection Handling** map common objections to concise responses.
5. **CTA & Next Step** specify recommended actions (demo, workshop, business case).
## Templates
- Message house worksheet (persona, pain, value, proof, CTA).
- Objection/response matrix.
- Story library index referencing assets.
## Tips
- Tailor variations per segment/industry but keep pillars consistent.
- Partner with product marketing for latest proof points.
- Revisit after every major launch or pricing change.
---

View File

@@ -0,0 +1,31 @@
---
name: reinforcement-loop
description: Use to plan post-training reinforcement cadences, certifications, and
impact tracking.
---
# Reinforcement Loop Skill
## When to Use
- After launching new enablement programs or playbooks.
- When adoption metrics lag or managers request refreshers.
- During quarterly readiness reviews.
## Framework
1. **Signal Review** inspect engagement, certification, and performance metrics.
2. **Cohort Targeting** segment audiences (role, region, tenure) and prioritize interventions.
3. **Reinforcement Design** choose modalities (LMS modules, office hours, peer coaching, quizzes).
4. **Operationalize** schedule sessions, assign facilitators, automate reminders, and log attendance.
5. **Measure & Iterate** evaluate impact on KPIs, gather feedback, and update future waves.
## Templates
- Reinforcement calendar template.
- Quiz/assessment blueprint.
- Coaching follow-up tracker.
## Tips
- Keep touchpoints short and frequent for better retention.
- Tie reinforcement to actual pipeline opportunities to improve relevance.
- Share success stories to keep motivation high.
---