CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reactivation-specialist

Use when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", or "sunset my dead list"; produces a closed-loop reactivation program — a lapsed-cohort definition, a staged offer ladder, a re-consent (re-permission) capture step, and a sunset-confirm / suppression rule. Owns none of the SEND-N sub-item notes: engagement-decay / sunset is email-sequence-designer's and preference-center / frequency options is preference-frequency-manager's — this skill references those notes, it does not re-emit them. Not for the general lifecycle flows (welcome/cart/post-purchase) — use email-sequence-designer; not for the preference-center / opt-down ladder — use preference-frequency-manager; not for the consent record itself — use consent-registry; not for computing EQS or the N1 veto — use email-quality-auditor. 流失召回/重新授权/沉默用户清理

Quality

89%

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

77%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, highly actionable instruction-only skill with an exemplary decision-gate and termination structure. Its one real defect is verbosity: the same cross-skill ownership boundary is repeated seven times, which inflates token cost without adding guidance, and the ladder design steps would benefit from one worked example with timings.

Suggestions

Consolidate the repeated N-sub-item ownership boundary (stated in the intro, Skill Contract, Done-when, steps 4/5/7, and the Scope guard) into the single Scope guard section, leaving one-line pointers elsewhere — this is the largest token-efficiency win.

Add one worked example of the offer ladder with concrete delays (e.g., soft touch day 0 → incentive day 7 → last-chance day 21) so step 3's "specify the delay" has an anchor for the common case.

Trim step 7, which largely restates the handoff instructions already given in steps 4 and 5, down to the two routing facts plus the 'do not score or roll up N here' rule.

DimensionReasoningScore

Conciseness

The body is mostly dense and professional, but the N-sub-item ownership boundary ("engagement-decay / sunset is email-sequence-designer's and preference-center / frequency options is preference-frequency-manager's — hand the fact, do not score it here") is restated roughly seven times across the intro, Skill Contract, Done-when, steps 4/5/7, and the Scope guard. That repetition is padded overhead that a single authoritative scope section would eliminate, so it sits between anchors 2 and 3, closer to 3.

3 / 5

Actionability

Concrete, executable design guidance throughout: numeric defaults ("no open in 90 days, no click in 180", "cap the reactivation touches (typically 3–4…)"), profile weights (0.15 / 0.30 / 0.15 / 0.20), an exact save path (memory/email/reactivation-specialist/YYYY-MM-DD-<cohort-or-goal>.md), and copy-paste Quick Start prompts. Not level 5 because the offer-ladder steps demand a delay be specified yet provide no example timing ladder or sample output artifact to anchor the common case.

4 / 5

Workflow Clarity

A clearly sequenced 7-step process with explicit validation checkpoints (the Stop-and-ask / Continue-silently decision gates and the consent-record NEEDS_INPUT guard), a Done-when checklist, and a stated error-recovery feedback loop ("if it returns BLOCK on N1, route back here to repair the opt-out / re-consent path"), which matches the anchor-5 combination of sequence, checkpoints, checklist, and loop.

5 / 5

Progressive Disclosure

The 78-line body is a clean overview: well-labeled sections (Skill Contract, Data Sources, Instructions, Decision Gates, Save Results, Reference Materials, Next Best Skill) with contract/benchmark details pushed to one-level-deep, individually annotated references (skill-contract.md, send-benchmark.md, CONNECTORS.md, SECURITY.md) rather than inlined. No bundle directories exist in this review copy to verify, but the structure and signaling themselves match the anchor-5 example.

5 / 5

Total

17

/

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.

An exemplary description: concrete deliverables, quoted user-facing trigger phrases, explicit use-when guidance, and thorough negative-scope routing to sibling skills. Its only weakness is length — the ownership/SEND-N boundary prose is dense internal jargon that could be trimmed — but every clause carries routing information rather than fluff.

DimensionReasoningScore

Specificity

The description enumerates four concrete deliverables — "a lapsed-cohort definition, a staged offer ladder, a re-consent (re-permission) capture step, and a sunset-confirm / suppression rule" — giving comprehensive coverage of what the skill produces with no generic filler. It exceeds the level-4 anchor because there are no minor gaps in the action inventory.

5 / 5

Completeness

Both halves are explicit: the what ("produces a closed-loop reactivation program" with the four named components) and the when ("Use when the user asks to…" followed by four concrete trigger phrases), exactly matching the anchor-5 pattern. It is not level 4 because the when-clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

It quotes the exact natural phrases a user would say — "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", "sunset my dead list" — and adds synonyms (win-back, lapsed, sunset, dead list) plus bilingual terms (流失召回/沉默用户清理). Coverage is comprehensive; no common variation is missing, so it does not fall to level 4.

5 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche and actively de-conflicts with four named sibling skills ("Not for the general lifecycle flows… use email-sequence-designer; not for the preference-center / opt-down ladder… not for the consent record itself… not for computing EQS or the N1 veto"), minimizing wrong-skill triggering. Not level 4, since overlap risk is addressed explicitly rather than merely reduced.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 35 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

email/nurture/reactivation-specialist/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.