CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keep-churn

Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, actionable instruction-only skill with concrete thresholds, commands, and scripted intervention sequences. Its main defects are the missing validation of the produced register, incomplete playbook coverage for several listed risk types, and a dangling docs/output-kit.md reference that undermines the output-format guidance.

Suggestions

Add docs/output-kit.md to the skill bundle (or inline the output format), since the body instructs Claude to follow it but the file does not exist in the skill directory.

Provide intervention sequences — or at least brief guidance — for the risk types listed in the signal table that currently lack playbooks (Disengaged, Satisfaction collapse, Relationship gap, Disengagement).

Add a validation checkpoint before delivery, e.g. confirm every CRITICAL/HIGH account in the register has a renewal date and primary signal, and that each present risk type maps to an intervention sequence.

DimensionReasoningScore

Conciseness

The body is dense and efficient — quantified signal thresholds in tables, compact day-by-day playbooks, and no explanations of concepts Claude already knows. Minor trimmable elements (the persona sentence and slight severity overlap between the Step 1 and Step 2 tables) keep it below the lean-every-token-earns-its-place anchor.

4 / 5

Actionability

Provides executable find/grep commands, quantified thresholds (">40% usage", "NPS drop of 20+", "ARR >$50K"), scripted talk tracks, and a register template. However, playbooks are given for only 5 of the ~8 risk types in the signal table — Disengaged, Satisfaction collapse, and Relationship gap have no intervention sequence — a minor gap that blocks the top anchor.

4 / 5

Workflow Clarity

Steps 0–4 are clearly sequenced with an input-gathering checkpoint and conditional branches ("If no improvement, escalate", "If still evaluating, ask for a timeline"). Falls short of anchor 5 because there is no validation step verifying the final register or intervention output before delivery; this is analysis/reporting, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Section structure is good (clear step headers, tables, labeled playbooks), but the skill's entire output format depends on "docs/output-kit.md", which does not exist in the bundle (no references/, scripts/, or assets/ directories), and "/atlas-report" is an undefined external skill. The dangling critical reference plus ~60 lines of inlined playbooks that could be split out places this at the some-structure-but-could-be-better-organized anchor rather than the good-structure anchor.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description in third-person voice that clearly states what the skill does and when to use it, with concrete severity tiers and multiple natural trigger phrases. The only weaknesses are mild: the signal-scanning action is less concrete than the others and a few common churn-domain trigger variants (retention, renewal risk) are absent.

DimensionReasoningScore

Specificity

Lists three concrete actions — "scans health signals for at-risk accounts", "classifies risk level (CRITICAL/HIGH/MEDIUM)", "produces an intervention sequence per risk type" — matching the several-specific-actions anchor with minor gaps. Not anchor 5 because "scans health signals" does not enumerate which signals and coverage like escalation criteria is absent.

4 / 5

Completeness

Explicitly answers both questions: the "what" is the scan → classify → intervene pipeline, and the "when" is a concrete "Use when asked to..." clause with five quoted trigger phrases — an exact match for the top anchor. Not lower because neither what nor when is missing or vague.

5 / 5

Trigger Term Quality

Five natural quoted phrases ("find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", "rescue this account") give good keyword coverage with synonyms. Falls short of anchor 5 because common variants like "retention plan", "renewal risk", or "customer health review" are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear churn/customer-success niche with distinctive triggers ("who might churn", "churn prevention plan", "rescue this account") that no generic analysis skill would naturally claim. Minimal conflict risk, matching the top anchor.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-churn/SKILL.md

Reviewed

Table of Contents

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.