notify-templates

Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".

Quality

95%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

This is an excellent skill file that provides concrete, copy-paste-ready notification templates with clear routing rules, batch handling guidance, and specific anti-patterns to avoid. It's concise, assumes Claude's intelligence, and covers edge cases (batch vs. single, escalation thresholds) without verbosity. The actionable constraints ('do not spawn a subagent', 'do not call send_slack_alert once per SKU') are particularly well-placed.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient throughout. It assumes Claude's competence, avoids explaining what templates or JSONL are, and every section earns its place with specific templates, routing rules, and anti-patterns. The 'batch, don't spam' and 'how to send' sections are practical constraints, not filler.	3 / 3
Actionability	Every template is copy-paste ready with clear slot names. The routing table gives specific thresholds ($25k, $100k, top-100 SKU). The 'how to send' section provides executable bash/python commands for appending to the outbox, and the batch example is concrete and runnable.	3 / 3
Workflow Clarity	For a template-filling skill, the workflow is unambiguous: fill slots → append to outbox → confirm. The routing table clearly sequences decision-making (who gets what, when). The batch section explicitly addresses the sweep vs. single-SKU distinction with clear instructions for each case. The skill is not a destructive multi-step process, so validation checkpoints are not critical here.	3 / 3
Progressive Disclosure	The content is well-organized into logical sections (templates, routing, batching, sending) with clear headers. At ~80 lines it's appropriately sized for a single file with no need for external references. No bundle files are needed or referenced, and the structure supports easy scanning.	3 / 3
	Total	12 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid description that clearly communicates both what the skill does and when to use it, with explicit trigger terms. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., generating, formatting, populating templates). Overall it performs well for skill selection purposes.

Suggestions

Add specific action verbs to the capability description, e.g., 'Generates and populates fixed-format templates for Slack alerts, supplier emails, and escalations.'

Dimension	Reasoning	Score
Specificity	Names the domain (notifications/alerts) and lists specific template types (Slack alerts, supplier emails, escalations), but doesn't describe concrete actions like 'generate', 'send', or 'format' in detail.	2 / 3
Completeness	Clearly answers both what ('Fixed-format templates for Slack alerts, supplier emails, and escalations') and when ('Load this whenever the task is notify, alert, email, or tell ops') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes natural trigger terms users would say: 'notify', 'alert', 'email', 'tell ops', 'Slack alerts', 'supplier emails', 'escalations'. These cover common variations well.	3 / 3
Distinctiveness Conflict Risk	The combination of fixed-format templates, specific notification channels (Slack, supplier emails), and operational escalation context creates a clear niche that is unlikely to conflict with general email or messaging skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: anthropics/cwc-workshops
Commit: 970b040

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.