One CSM who already preps renewals well, and the account notes you already have.
An approved renewal prep skill in every CSM's Claude: same method, current by default, live in the first week.
The method one person already has
Before an important renewal, a strong CSM opens CRM notes, scans recent calls, checks product usage, reviews open tickets, looks at renewal terms, and writes a prep brief. The method is valuable, but it usually lives in one person's chat history.
With knacks, that CSM describes the prep routine in plain English and knacks drafts the skill with examples and tests. The renewals lead approves it, it ships to every CSM's Claude with nothing to install, the skill library is its home, and the owner keeps it current. That is the knacks loop: Publish, Approve, Ship, Use, Improve.
Anatomy of the skill
| Method | Pull CRM notes, call transcripts, support tickets, usage trend, and contract terms for the account, then write the prep brief: risk rating, likely objections, questions to ask, stakeholder notes, expansion angles, next steps. Run it when a renewal call lands within 45 days, before an executive business review, or during risk review. |
|---|---|
| Reference files | ICP, product modules, renewal risk taxonomy, support severity rules, current pricing and packaging, approved positioning. |
| Examples | Two real prep briefs the renewals lead rates as strong, alongside the account inputs that produced them. |
| Tests | The brief must cite its sources, rate risk against the taxonomy, avoid unsupported claims, and end with owners and next steps. |
| Owner | Director of Customer Success or renewals lead. |
| Version | Version history with a one line changelog, so any CSM can see when the pricing context or risk taxonomy last changed. |
What the team lead reviews
Does the skill cite which notes, tickets, transcripts, and usage data it used?
Does the risk rating follow the company's renewal risk taxonomy instead of vague sentiment?
Does the output avoid unsupported claims, internal-only assumptions, or blame language?
Does the brief produce questions, owners, next steps, and escalation paths?
Example output
Usage down 22 percent in the admin module, two unresolved support tickets, and new economic buyer not yet mapped.
Seat utilization, unclear ROI from the last quarter, support responsiveness, and whether the new packaging changes renewal terms.
Confirm success criteria for renewal, validate which teams still depend on the product, and identify whether procurement has changed.
Bring support lead into the call, send usage recovery plan, schedule exec sponsor follow-up, and update close plan in CRM.
Kept current
When reality changes, the owner updates the skill once and every CSM gets the new version the same day. Example: the 2026 price list lands.
No capture and no usage tracking, ever. knacks never sees chats, screens, or who runs what.
Why it matters
This skill does not replace the CSM. It gives every CSM the best prep pattern the team already knows. New hires start from a stronger baseline, the owner can improve one version instead of chasing ten variants, and the whole team preps from the same approved version.
Publish your first renewal prep skill.
Book a walkthrough and we will map the method, owner, review criteria, and launch path.
Book a walkthrough