CtrlK
BlogDocsLog inGet started
Tessl Logo

contact-template

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

61

Quality

73%

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 ./packages/decepticon/decepticon/skills/standard/soundwave/contact-template/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is efficient, actionable, and well-structured with explicit validation, scoring strongly across all dimensions; the main gap is the absence of a concrete feedback loop and a sample output artifact.

DimensionReasoningScore

Conciseness

The body is lean with each step giving concrete fields and formats and useful ISO 8601 examples, with only a few explanatory asides (e.g., the 15-minute default note) that earn their place but could be trimmed.

4 / 5

Actionability

It gives concrete field lists, an ordered escalation chain, real ISO 8601 example values, and a specific output path and schema, but lacks a sample output artifact (e.g., an example contact.json) that would make guidance fully copy-paste ready.

4 / 5

Workflow Clarity

Five numbered steps are clearly sequenced and backed by an explicit validation checklist, but the workflow stops short of an explicit 'if validation fails -> fix -> retry' feedback loop.

4 / 5

Progressive Disclosure

The skill is single-purpose, well-organized into clear sections (When to Use, Workflow, Validation Checklist, Anti-patterns, Output), and has no bundle files or content that warrants splitting into separate references.

5 / 5

Total

17

/

20

Passed

Description

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

The description is specific and distinctive, clearly communicating a niche capability, but it omits an explicit 'Use when...' trigger clause and relies on metadata for trigger terms, which limits completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause to the description naming concrete triggers (e.g., 'Use when creating a contact/communications plan, escalation chain, or deconfliction/blackout schedule for an engagement').

Surface natural user phrases and synonyms directly in the description (e.g., 'who do we notify', 'SOC notification') rather than only in metadata.when_to_use.

Keep the component list but pair it with the when-to-use context so the description answers both what and when in one field.

DimensionReasoningScore

Specificity

The description names the domain ('Contact / communications plan generator') and enumerates five concrete components (primary operator, escalation chain, abort signal recipient, external SOC endpoint, blackout windows), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

It clearly answers 'what' (generates a plan with named components) but lacks any explicit 'when to use' / 'Use when...' clause in the description itself, which per the rubric guideline caps completeness at 3.

3 / 5

Trigger Term Quality

It includes some natural user-facing terms like 'escalation chain' and 'blackout window' but misses common variations, synonyms, and a 'Use when...' phrasing; the explicit trigger phrases live in metadata.when_to_use rather than the description.

3 / 5

Distinctiveness Conflict Risk

The SOC endpoint, abort-signal-recipient, and blackout-window framing carves a clear niche for autonomous-AI engagement deconfliction with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.