expansion-retention

When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention. Also use when the user mentions 'churn,' 'retention,' 'expansion revenue,' 'upsell,' 'NRR,' 'net revenue retention,' 'customer success,' 'land and expand,' 'closed-lost,' or 'renewal.' This skill covers expansion and retention systems from usage triggers through automated customer success. Do NOT use for technical implementation, code review, or software architecture.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable GTM strategy skill with concrete matrices and sequenced playbooks, weakened mainly by a monolithic structure that forgoes progressive disclosure and by occasional unverifiable statistic padding.

Suggestions

Split the dense reference material into one-level-deep bundle files (e.g., references/benchmarks.md for NRR/segment tables, references/tech-stack.md for the tool directory) and signal them from a leaner SKILL.md overview to improve progressive_disclosure.

Trim or substantiate the unsourced statistic claims ('77% of the largest software companies', '85%+ accuracy', '38% faster growth') to tighten conciseness and avoid drift over time.

Add explicit validate→adjust→retry checkpoints to the onboarding and renewal workflows (e.g., 'if milestone missed by day X, trigger recovery play') to lift workflow_clarity to the top anchor.

Dimension	Reasoning	Score
Conciseness	Dense, table-driven reference content that mostly earns its tokens, but carries several unverifiable statistical asides ('77% of the largest software companies...', '38% faster revenue growth', '85%+ accuracy') and a few explanatory sentences Claude does not need.	4 / 5
Actionability	Highly concrete instruction-only guidance: weighted health-score components, a points-based PQA model with decay rules, a day-by-day onboarding sequence, and a renewal timeline keyed to days-before-renewal — copy-paste ready playbooks covering common cases.	5 / 5
Workflow Clarity	Multi-step processes (onboarding milestones, 180→7 day renewal timeline, three-phase closed-lost cadence, NRR decision framework) are clearly sequenced, but lack explicit validate→fix→retry feedback loops; not a destructive/batch skill so no validation cap applies.	4 / 5
Progressive Disclosure	The body is a ~460-line monolith with nine numbered sections plus reference appendices, all inlined and no bundle files or external references despite benchmark tables, a tech-stack directory, and capacity-planning matrices that would benefit from being split out.	3 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: concrete actions, comprehensive trigger terms, explicit what-and-when guidance, and a clear negative boundary. It hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention') and scopes the domain end-to-end ('from usage triggers through automated customer success'), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (expansion and retention systems) and 'when' ('When the user wants to...' and 'Also use when the user mentions...'), plus a negative boundary ('Do NOT use for...').	5 / 5
Trigger Term Quality	Comprehensive natural keyword coverage including synonyms and abbreviations — 'churn,' 'retention,' 'expansion revenue,' 'upsell,' 'NRR,' 'net revenue retention,' 'customer success,' 'land and expand,' 'closed-lost,' 'renewal' — phrases users would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear post-sale revenue/retention niche with distinct triggers and an explicit exclusion clause ('Do NOT use for technical implementation, code review, or software architecture'), minimizing overlap with adjacent GTM skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tech-leads-club/agent-skills
Path: packages/skills-catalog/skills/(gtm)/expansion-retention/SKILL.md
Commit: fc886b7

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.