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.

61

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/outreach/composites/customer-win-back-sequencer/SKILL.md
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 highly actionable, well-sequenced skill body whose search strings, scoring formula, and templates leave nothing abstract. Its weaknesses are redundancy and time-sensitive hardcoded years that hurt token efficiency, and a monolithic single-file structure with no reference files despite enough template material to justify them.

Suggestions

Remove the "Trigger Phrases" section (it duplicates "When to Use") and tighten the intro/"Built for" prose to cut ~20 lines of redundant tokens.

Replace hardcoded years in search queries with a current-year placeholder (e.g., [CURRENT YEAR] [CURRENT YEAR-1]) so the queries don't silently expire.

Move the full email templates and the output-format template into reference files (e.g., references/email-templates.md, references/report-format.md) and keep a one-line pointer plus one exemplar email in SKILL.md.

Add a validation step before Phase 3, e.g., confirm the researched contact is still at the company and re-check any funding/growth claim with a second source before personalizing a sequence.

DimensionReasoningScore

Conciseness

The body is mostly efficient — search strings, a scoring formula, and templates rather than concept explanations — but includes unnecessary material: the "Trigger Phrases" section duplicates "When to Use" almost verbatim, the intro/"Built for" prose pads the opening, and search queries hardcode time-sensitive years ("funding OR raised OR "series" OR acquisition 2025 2026") that will age. Mostly efficient with some sections that could be tightened, matching anchor 3 rather than 4.

3 / 5

Actionability

Fully concrete, copy-paste-ready guidance throughout: exact search query strings, a completely specified scoring formula with numeric scales and multipliers, priority-tier thresholds, full email templates with subject-line options, a full output-format template, and a concrete save path. Specific examples cover the common cases (high priority, medium priority, competitor-specific), matching the anchor-5 example's standard.

5 / 5

Workflow Clarity

The Phase 0→4 sequence (Intake → Research → Scoring → Sequence Generation → Output) is clearly ordered, with the scoring formula and priority tiers acting as explicit checkpoints that gate downstream action (full sequence vs. batch vs. skip) and an "Accounts to Skip (and Why)" table documenting exclusions. Not 5 because validation gaps remain: there is no step to verify research findings (e.g., confirming the contact is still at the company) or to review generated emails before campaign setup — a meaningful gap for a batch operation over a churn list.

4 / 5

Progressive Disclosure

The single SKILL.md is ~340 lines with good section headers, but no bundle files exist and nothing is offloaded: the four full email templates, the output-format template, and the scoring rubric are all inlined content that could live in one-level-deep reference files. This sits between anchor 2 (content that belongs in separate files is inlined) and anchor 4 (well-split with clear references) — structure is good but the split is absent, so 3.

3 / 5

Total

15

/

20

Passed

Description

75%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 specific, well-scoped description that clearly communicates what the skill does with concrete actions and a distinct niche. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness, and slightly thin synonym coverage for natural trigger phrases.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user mentions churned customers, wants to win back lost accounts, or asks about re-engaging lapsed customers."

Include natural synonym variations users would say — "churned customers", "win back", "lost accounts" — to broaden trigger coverage.

State the input expectation (a churned-customer list with churn dates and reasons) so the "what" includes what the skill needs to run.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "research what has changed since they left — new funding, team growth, competitor dissatisfaction, product updates", "assess re-engagement potential", "generate a personalized win-back email sequence with timing recommendations" — with comprehensive coverage of the skill's capabilities. Not below 4 because coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

The "what" is clear and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance — the description never states when to invoke it (e.g., "Use when the user mentions churned customers or wants to win back accounts"). Per the rubric guideline, a missing explicit trigger clause caps completeness at 3, so it cannot score 4.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "churned accounts", "win-back", "re-engagement", "email sequence" are phrases users would actually say. A few natural variants are missing ("churned customers", "win back customers", "lapsed accounts"), so it falls between the good (4) and comprehensive (5) anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (churned-account win-back outreach) with distinct triggers — "churned accounts", "win-back email sequence", "re-engagement potential" — that no generic outreach or research skill would claim. Minimal conflict risk; not lower because it is unmistakably distinguishable.

5 / 5

Total

17

/

20

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.

Validation — 15 / 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.