Champion change

Skill quivly/skills/customer-engineering/champion-change

Production-ready Agent Skills for Customer Engineering, Post-Sales, and Customer Success teams. Quivly Skills is a curated open-source collection of reusable skills that give AI agents deep expertise in customer engineering workflows. Every skill follows the official Agent Skills specification.

Install

npx -y skills add quivly/skills --skill champion-change

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Responds to a champion or sponsor departure — maps the remaining relationship surface, assesses exposure, and builds a re-entry plan for the new stakeholder. Use when a key contact leaves, changes roles, or a new decision-maker inherits the account.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, as published. Nobody here has run it

Champion Change Response

Executive and champion turnover is one of the top churn causes in B2B. You run the response: map what's left, protect the relationship, and win the successor.

Core principle: move inside 30 days — that's when the successor forms vendor impressions and scopes tool reviews.

Workflow

Confirm the change and its shape (get-contacts, search-conversations): who left/moved, what they owned (budget? daily usage? political air cover?), and who inherits.
Map the remaining relationship surface (get-contacts, search-calls): who else knows us, likes us, and has influence. Rate the exposure:
- Cushioned — multi-threaded; other engaged stakeholders can carry the story
- Exposed — the departed champion was the main thread
- Critical — single-threaded AND renewal inside 6 months
Reconstruct the value story the champion carried (search-calls, search-conversations) — the successor inherits a line item, not the context. Collect the wins, metrics, and history that justify us.
Build the two-track plan:
- Successor track — early intro meeting framed as "here's what your team achieves with us" (business outcomes, not product tour); learn their priorities; expect and prepare for a tool review
- Departed-champion track — stay warm; where they land, they're a future deal

Output Format

Champion change: {Customer} — who changed, exposure rating, renewal distance

Remaining relationship map — who we still have, strength of each thread

Value story to transfer — the 3-5 proof points the successor must hear early

Two-track plan — successor plays with dates; departed-champion follow-up

Risk note — if exposure is Critical, the explicit escalation ask (exec sponsor intro, priority handling)

Guidelines

Move fast: the first 30 days of a new stakeholder are when vendor impressions form and reviews get scoped.
Never open with "let me show you the product" — open with what their team accomplishes with it.
A new exec often brings their preferred stack; assume a competitive review is coming and pre-empt it with outcomes evidence.
Log the departed champion's destination — champion tracking is a pipeline source.

Related skills: renewal inside 6 months → renewal-risk; briefing for the successor intro → account-360.