CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

email-lifecycle-flow-writer

Step of the email-lifecycle playbook: writes one lifecycle flow as a build sheet for the brand's email tool, every message finished in the brand voice. Run email-lifecycle instead; not for direct use.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/marketing/email-lifecycle-flow-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dense, disciplined procedural skill: correctly sequenced with real validation loops, literal output templates, and conditional external references. Its main cost is compression — multi-clause mega-sentences hide critical requirements — and its references are unverifiable from this bundle since they live in the parent skill's directory.

Suggestions

Break the ~90-word sentences in steps 1 and 3 into short labeled lists (e.g. the flow-header fields, the per-message checklist) so no requirement is buried mid-sentence.

Include one condensed worked example of a finished flow entry (status line + one message) inline so the quality bar does not depend entirely on the external 'worked-flows.md'.

DimensionReasoningScore

Conciseness

The body explains nothing Claude already knows and has no padding — every line is procedural. It sits between anchors 4 and 5: efficient overall, but steps 1 and 3 are ~90-word single sentences that bury critical requirements (the flow-header field list, the per-message checklist) and could be structured with no token cost. Not anchor 5's 'every token earns its place' in effective form, clearly above anchor 3.

4 / 5

Actionability

Highly concrete for an instruction-only skill: exact paths ('lifecycle/flows/<flow-slug>.md'), literal templates ('not ready: answer Q3, Q5', the 'Graphic needed:' line format), and a worked hypothesis example ('abandoned checkout: ≥ 4% of recipients order within 7 days'). It falls short of anchor 5 because the core deliverable's syntax is delegated to the external 'loadable-flow-format.md' and no worked output example appears inline — minor gaps, so anchor 4.

4 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced (wire, plan, write, self-check, gaps, hypothesis, art), step 4 is an explicit validate-and-rewrite loop, and step 5 gates output status. This meets much of anchor 5, but the extreme sentence density makes some checkpoints implicit (e.g. 'Check plan reality' criteria) and final verification is delegated to the parent skill — between anchors 4 and 5.

4 / 5

Progressive Disclosure

References are one level deep and well-signaled with purpose and conditional loading ('sms-push-whatsapp.md when the flow has those legs', 'worked-flows.md (quality bar)'), matching anchor 4's 'references mostly clear'. It is not anchor 5 because all references live outside this skill's own bundle ('../email-lifecycle/references/'), none are present here to verify, and the body inlines heavy procedural detail that makes the SKILL.md more than a lean overview.

4 / 5

Total

16

/

20

Passed

Description

66%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 well-scoped sub-step description in third person with a clear 'what' and an explicit redirect-style 'when'. Its weaknesses are narrow action coverage and missing natural trigger variations users would say when they need lifecycle email work.

Suggestions

Add one or two more concrete actions to broaden coverage, e.g. 'wires the flow in the tool's real syntax, plans message timing, and records a per-cycle hypothesis'.

Include the natural phrases users actually say for this domain — 'welcome series', 'abandoned checkout', 'drip campaign', 'lifecycle email' — so the skill (and its parent) surface on real requests.

State positively when it runs, e.g. 'Runs as a step of the email-lifecycle playbook when a flow is ready to be built', in addition to the 'not for direct use' redirect.

DimensionReasoningScore

Specificity

The description names the domain and 1-2 concrete actions ('writes one lifecycle flow as a build sheet for the brand's email tool, every message finished in the brand voice') but does not comprehensively cover what the step involves (wiring, hypotheses, gap-handling are unmentioned). It is a clear anchor-3 match: not the generic anchor 2, but short of the 'several specific actions' of anchor 4.

3 / 5

Completeness

It clearly answers 'what' (writes one lifecycle flow as a build sheet, messages finished in brand voice) and gives explicit trigger guidance in redirect form ('Run email-lifecycle instead; not for direct use'), which is equivalent to a 'when' clause for a sub-step skill. It falls short of anchor 5 because no concrete positive trigger phrases are given, so anchor 4 is the best fit.

4 / 5

Trigger Term Quality

Natural keywords like 'lifecycle flow', 'email tool', and 'brand voice' are present, but common user phrasings (welcome series, abandoned checkout, drip campaign) are missing. This matches anchor 3 ('some relevant keywords but missing common variations') rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'Step of the email-lifecycle playbook' plus 'Run email-lifecycle instead; not for direct use' carves a clear niche and actively redirects any mis-trigger to the parent skill, giving minimal conflict risk — a direct match for anchor 5.

5 / 5

Total

15

/

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

Path

skills/marketing/email-lifecycle-flow-writer/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.