agentleFS
Sign inStart free
kyle-olmsteadkyle-olmstead/cs-claude-engine/skills/renewal-defense/SKILL.md

renewal-defense

Skill1 starsChanged 23 days agoApache-2.0View on GitHub

This skill should be used when the user says "prep the [account] renewal", "renewal plan for [account]", "is [account] going to renew", "[account] renews in N days", "renewal defense", "right-size scenario for [account]", "what's our renewal outlook on [account]", or when a book review flags PB-RET-02. It builds the standard renewal defense plan for an account inside the 120-day window that is yellow, under-utilized, or recently contracted but not red: the three scenarios with GRR-dollar impact, the stakeholder ask map, dated actions against the R-120/90/60/45/30/14 anchors, value-story inputs, and one approval-gated kickoff draft.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow ${CLAUDE_PLUGIN_ROOT}/skills/customer-360/references/playbook-protocol.md with these specifics.

    line 18
  2. Distinctive:

    Never propose pricing, discounts, free months, or term changes.

    line 42
  3. Distinctive:

    Do not schedule more than one meeting per stakeholder in the first 14 days.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Renewal defense (PB-RET-02)

Follow ${CLAUDE_PLUGIN_ROOT}/skills/customer-360/references/playbook-protocol.md with these specifics.

When it applies

contract.days_to_renewal ≤ 120 and any of: health.band == "yellow", usage.seat_utilization < 0.50, contract.contraction_flag_90d == true. If the account meets a PB-RET-01 trigger instead (red, champion departed, aged P1, ECRI ≥ 60), run red-account-turnaround: it includes this plan. If the renewal is more than 120 days out, say so and offer customer-360 or ebr-generator (a renewal-variant EBR at R-180 is the better move).

Prompt

${CLAUDE_PLUGIN_ROOT}/prompts/retention/renewal_defense_playbook.prompt with rca_json = {} (no RCA in the standard path). Set playbook_id to PB-RET-02. Compute timeline_anchor_today from days_to_renewal; if the R-120 or R-90 window has already passed, compress the plan and say so in the summary.

Artifacts

  • PB-RET-02.renewal_defense_playbook.action.json
  • PB-RET-02.renewal_defense_playbook.comm_1.md: renewal kickoff draft to the economic buyer (or exec sponsor if no economic buyer is engaged); approval required.
  • A one-page PB-RET-02.renewal_plan.md rendered from the action for the user's own renewal review: scenario table, stakeholder asks, timeline, value-story inputs and the measurements still needed.

Proposed writes

  • ~~crm: cse_scenario on the renewal opportunity (informational; never the stage, amount, close date or forecast category); task "Renewal kickoff meeting: <account>" due within 10 days; one task per unmeasured value-story input ("Measure <outcome> before R-90").
  • ~~calendar: proposed hold for the value review inside the R-90 window.
  • ~~email: a draft of comm_1 in the user's mailbox.

Rules specific to this playbook

  • Never propose pricing, discounts, free months, or term changes. "Proposal inputs" are facts, not numbers for the paper.
  • Do not schedule more than one meeting per stakeholder in the first 14 days.
  • For the digital segment the plan must be executable with automation plus one CSM touch.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free