CtrlK
BlogDocsLog inGet started
Tessl Logo

customer-win-back-sequencer

For churned accounts, research what has changed since they left — new funding, team growth, competitor dissatisfaction, product updates that address their pain — then assess re-engagement potential and generate a personalized win-back email sequence with timing recommendations. Chains web research and LinkedIn monitoring with email sequence generation.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A well-sequenced, highly actionable multi-phase workflow with concrete search strings, a scoring model, and ready-to-use email templates; its main weakness is that everything lives in one long monolithic file with no progressive disclosure to bundle references.

Suggestions

Move the Phase 3 email-sequence templates and the Phase 2 scoring rubric into reference files (e.g. references/email-templates.md, references/scoring.md) and link to them from a concise overview, so the SKILL.md body stays a lean overview.

Add an explicit verification checkpoint before sequence generation, e.g. confirm each email's claimed change is backed by a Phase 1 research finding, to strengthen the batch-generation feedback loop.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — it never explains basic concepts like what email outreach or MRR is — and nearly every token earns its place as literal search strings, a scoring formula, or the email templates that are the skill's actual deliverable.

3 / 3

Actionability

Guidance is concrete and copy-paste ready: exact search-query strings, a fully specified Win-Back Score formula with factor ranges, complete email templates with placeholders, a structured output format, and a concrete save path.

3 / 3

Workflow Clarity

Phases 0–4 are explicitly sequenced, and the Phase 2 scoring tiers act as a gating checkpoint that decides downstream action while the "Accounts to Skip (and Why)" section serves as a verification step, satisfying the validation-checkpoint expectation for a batch research-and-generate workflow.

3 / 3

Progressive Disclosure

The skill is a single 340-line file with no bundle references, and the large inline email-template library (Phase 3) and scoring rubric are content that could plausibly be split into separate reference files, so structure exists but content that should be separate is inline.

2 / 3

Total

11

/

12

Passed

Description

82%

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 specific, third-person description that names concrete actions and uses natural win-back vocabulary, but it omits any explicit "Use when…" trigger clause, leaving the when-to-use guidance implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. "Use when re-engaging churned customers, building win-back campaigns, or monitoring churned accounts for changes that reopen the conversation."

Include common user phrasings like "win-back campaign", "churn list", or "bring back lapsed customers" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "research what has changed", "assess re-engagement potential", "generate a personalized win-back email sequence with timing recommendations", and "Chains web research and LinkedIn monitoring with email sequence generation" — matching the anchor for listing multiple specific concrete actions rather than naming only a domain.

3 / 3

Completeness

It clearly answers "what does this do" but never states when Claude should invoke it; there is no "Use when…" clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It covers natural domain terms a user would say — "churned accounts", "win-back email sequence", "re-engagement potential", "competitor dissatisfaction" — giving good coverage of the phrasings a user reaches for when they need this skill.

3 / 3

Distinctiveness Conflict Risk

The churned-account win-back niche is narrow and distinct from general outreach or sales skills, with triggers unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.