CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

email-lifecycle-broadcast-planner

Step of the email-lifecycle playbook: builds the month's send calendar and writes this week's email and SMS broadcasts against the approved cadence and segments. Run email-lifecycle instead; not for direct use.

Quality

78%

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-broadcast-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary lean instruction skill: dense, specific, and free of padding, with a clear step sequence and built-in checks (stock confirmation, send-limit totals, blackout flags). The main improvements are structural — unpacking the run-on Reads line and spelling out error-recovery loops for unconfirmed stock or exceeded send limits.

DimensionReasoningScore

Conciseness

The body is a lean Reads/Does/Writes structure where every clause carries operational content — exact paths ("lifecycle/calendar/<YYYY-MM>.md"), specific fields ("subject + 2 alternates, preview, body, CTA with tracked URL, plain text"), and concrete rules ("60–70% useful sends in non-sale weeks"). Nothing explains concepts Claude already knows; every token earns its place, matching the score-5 anchor.

5 / 5

Actionability

As an instruction-only skill it gives highly concrete output specs — per-send field checklists, exclusion rules, exact write paths, test-winner criteria — so the absence of code is not penalized. It stops short of fully executable because several items defer to unshown context ("offer if any (from the ladder only)", "Margin box from offer-math", "the one idea") whose formats are defined elsewhere, leaving minor gaps.

4 / 5

Workflow Clarity

The four numbered steps give a clear sequence (calendar, then this week's finished sends, then SMS, then margin boxes) with most checkpoints present: "stock confirmed for each featured product", "Totals the month's sends ... against the plan's monthly send limit; spreads the sends or proposes the upgrade", and "Flags blackout dates and shipping cut-offs". It lacks the explicit validate-fix-retry feedback loops of the score-5 anchor, e.g. what to do when stock is unconfirmed or the send limit is exceeded beyond 'proposes the upgrade'.

4 / 5

Progressive Disclosure

The body is a compact overview that correctly delegates detail to one-level-deep references in the parent skill, each signaled with its purpose ("copy-craft.md", "sms-push-whatsapp.md", "modes-and-incidents.md (seasonal)"). It sits at 4 rather than 5 because the references are packed into a single dense run-on 'Reads' sentence alongside tool calls and data sources rather than presented as clearly navigable, individually-signposted pointers.

4 / 5

Total

17

/

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-skill description with concrete actions, correct third-person voice, and exemplary conflict-avoidance routing for a playbook atom. Its weaknesses are a thin set of natural trigger synonyms and trigger guidance phrased only as a negative rather than as positive 'use when' conditions.

Suggestions

Add the domain's natural vocabulary — newsletter, campaign, promotional calendar, launch emails — so the description's keywords match how users and the parent playbook refer to this work.

Complement the negative routing with a positive trigger clause, e.g. 'Invoked when the email-lifecycle playbook reaches its broadcast-planning step,' to make the 'when' fully explicit.

Expand the action list slightly (e.g., 'drafts subject lines with alternates and A/B tests, plans SMS for high-intent moments') to lift specificity beyond two summary actions.

DimensionReasoningScore

Specificity

The description names two concrete actions — "builds the month's send calendar" and "writes this week's email and SMS broadcasts against the approved cadence and segments" — which places it at the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several distinct actions (e.g., subject-line drafting, A/B testing, SMS consent handling) the way the score-4 and score-5 anchors require.

3 / 5

Completeness

The 'what' is clear (builds the monthly send calendar, writes this week's email and SMS broadcasts) and the 'when' is explicit via routing guidance: "Run email-lifecycle instead; not for direct use" — an explicit statement of when this skill applies (only as a playbook step, never directly). It falls short of the score-5 anchor because the trigger guidance is phrased negatively rather than as concrete positive trigger phrases.

4 / 5

Trigger Term Quality

Relevant domain keywords are present ("email", "SMS", "send calendar", "broadcasts", "cadence", "segments") but common variations a user would naturally say are missing — "newsletter", "campaign", "marketing", "promotional calendar". This matches the 'some relevant keywords but missing common variations or synonyms' anchor rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

It claims a clear niche ("Step of the email-lifecycle playbook") and actively prevents mis-triggering with "Run email-lifecycle instead; not for direct use", which routes any direct request to the parent skill. This matches the score-5 anchor: clear niche with distinct triggers and minimal conflict risk.

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-broadcast-planner/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.