contact-template

Contact / communications plan generator — primary operator, escalation chain, abort signal recipient, external SOC endpoint, blackout windows.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

The skill body is lean, actionable, and well-structured: a clear five-step workflow with concrete field names and ISO 8601 examples, an explicit validation checklist, and a dedicated anti-patterns section. It respects token budget and assumes Claude's intelligence while remaining fully instructional.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — e.g. 'Resolve from the RoE escalation_contacts', 'Format: "<start>/<duration-or-end>"' with concrete ISO 8601 examples — with no padding or re-explanation of concepts Claude already knows. Matches 'Lean and efficient; every token earns its place'.	3 / 3
Actionability	Concrete guidance throughout: explicit field names ('name, role, channel, availability'), a numbered escalation chain with defined roles, and copy-pasteable ISO 8601 blackout examples. As an instruction-only skill the absence of executable code is not penalized because the guidance is specific and actionable, matching the top anchor.	3 / 3
Workflow Clarity	A clear five-step sequence (identify operator → escalation chain → abort recipient → SOC endpoint → blackouts) is paired with an explicit 'Validation Checklist' preceding the output write and a schema to validate against. Matches 'Clear sequence with explicit validation steps; checklists for complex processes'.	3 / 3
Progressive Disclosure	No bundle files are needed for this single-purpose skill, and the body is cleanly organized into well-signaled sections (When to Use, Workflow, Validation Checklist, Anti-patterns, Output) with no nested reference chains, matching the allowance for self-contained skills that score 3 on well-organized structure.	3 / 3
	Total	12 / 12 Passed

Description

67%

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

The description is specific and distinctive about a contact/communications plan generator, but it lacks an explicit 'Use when...' trigger clause and the natural-language trigger terms users would say are only partially covered in the description itself. Strengthening the trigger guidance would raise completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g. 'Use when creating a contact or communications plan, defining an escalation chain, or setting blackout windows') to satisfy the completeness dimension.

Surface natural user phrases — such as 'who do we notify', 'SOC notification', 'escalation chain' — directly in the description rather than only in metadata.when_to_use, to improve trigger_term_quality.

Keep the concrete component list; it is the description's strongest asset for specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Quotes 'primary operator, escalation chain, abort signal recipient, external SOC endpoint, blackout windows' — the description enumerates multiple concrete deliverable components rather than vague language, matching the anchor 'Lists multiple specific concrete actions'.	3 / 3
Completeness	The 'what' is clearly stated (a generator for the listed contact-plan components), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which per the judging guidelines caps completeness at 2 ('Has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	The description includes 'Contact / communications plan generator' and 'escalation chain' — some relevant natural keywords — but lacks common variations a user would say (e.g. 'who do we notify', 'SOC notification'), and richer triggers live only in metadata.when_to_use rather than the description itself. This matches 'Some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The comms/escalation-plan niche is distinctive and tied to engagement-specific concepts (abort signal recipient, external SOC endpoint, blackout windows), making it unlikely to trigger for the wrong skill — matching 'Clear niche with distinct triggers; unlikely to conflict'.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: PurpleAILAB/Decepticon
Path: packages/decepticon/decepticon/skills/standard/soundwave/contact-template/SKILL.md
Commit: e34afba

Reviewed: about 14 hours 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.