smithery/gtmagents

renewal-playbooks

Use to design and maintain structured renewal/save motions across segments and risk levels.

Installation

$ npx skills add smithery/gtmagents --skill renewal-playbooks

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,380 B
  • docs SUMMARY.md 116 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Renewal Playbooks System Skill

When to Use

  • Building standardized renewal motions (green maintainers, yellow accelerators, red save plays).
  • Coordinating cross-functional resources for strategic accounts.
  • Training CSM/AEs on messaging, proofs, and negotiation sequences.

Framework

  1. Segmentation – define tiers, ARR thresholds, personas involved, and governance requirements.
  2. Trigger Matrix – map health indicators and risk levels to recommended plays.
  3. Narrative Blocks – curate value stories, ROI stats, roadmap previews, and reference assets per persona.
  4. Commercial Guardrails – outline pricing levers, discount approvals, and deal-desk steps.
  5. Measurement – tie each play to conversion, churn, and NRR metrics with review cadence.

Templates

  • Playbook card (objective, trigger, assets, timeline, owner, metrics).
  • Meeting brief template for QBR/EBR with executive checklist.
  • Risk mitigation plan linking issues to functional owners.

Tips

  • Pair with escalation-framework for red-tier governance.
  • Refresh narratives quarterly with product + marketing to keep proof points current.
  • Include structured feedback loops so CSMs capture deviations that worked well.