roe-template

Rules of Engagement document creation — scope definition, prohibited/permitted actions, testing windows, escalation contacts, incident procedures.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/soundwave/roe-template/SKILL.md

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.

The body is a well-structured, mostly lean instruction skill with a clear validated workflow and good progressive disclosure into real reference files. The main gaps are an implicit rather than explicit validate→fix→retry loop and one referenced path outside the bundle.

Suggestions

Make the validation feedback loop explicit in Step 3, e.g. 'If the checklist fails, fix the JSON and re-run validation before presenting to the user.'

Resolve or inline the missing ../references/schema-quick-reference.md reference so every cited path exists within the skill's bundle.

Tighten the intro ('legally binding foundation...') to a single clause to remove the last bits of non-essential explanation.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly assumes Claude's competence — concrete question types, options, and schema references with no padding — though the opening 'legally binding foundation' framing and a few descriptive sentences could be trimmed slightly.	4 / 5
Actionability	Guidance is concrete and actionable: specific question types (single/multi/free-form with allow_other=true), enumerated engagement-type options, named schema (decepticon.core.schemas.RoE) and output path, with only minor gaps since full field enumeration is deferred to referenced files.	4 / 5
Workflow Clarity	A clear three-step sequence (Interview → Generate → Validate) with an explicit validation checkpoint ('Run through the checklist in references/validation-checklist.md before presenting'), but the validate→fix→retry feedback loop is only implicit rather than spelled out.	4 / 5
Progressive Disclosure	The overview body points to one-level-deep, clearly signaled references (roe-example.json, validation-checklist.md) that exist in the bundle; the only organization gap is the ../references/schema-quick-reference.md path, which is not present in this skill's bundle.	4 / 5
	Total	16 / 20 Passed

Description

70%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 clearly distinct within the red-team planning domain, but it lacks an explicit 'Use when' trigger clause, which caps its completeness. Trigger-term coverage is good though missing a few natural synonyms like 'RoE' and 'boundaries'.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating a Rules of Engagement (RoE) document, defining engagement scope, or setting authorization boundaries before a red team engagement.'

Add the 'RoE' abbreviation and 'boundaries' as natural synonyms in the description so the skill triggers on the phrasings operators actually say.

Make the action verb explicit per component (e.g. 'define scope', 'enumerate prohibited/permitted actions') rather than noun-phrases to lift specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	Lists several concrete RoE components — 'scope definition, prohibited/permitted actions, testing windows, escalation contacts, incident procedures' — giving broad coverage, but the items are noun-phrases describing document sections rather than explicit actions Claude performs, leaving minor gaps versus the comprehensive-action anchor.	4 / 5
Completeness	The 'what' is clear and concrete (RoE document creation with enumerated components), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description itself, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	'Rules of Engagement document creation' and 'scope definition' are natural terms a user would say, but the description omits common synonyms like 'RoE' and 'engagement boundaries' that appear only in metadata, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	'Rules of Engagement document creation' carves out a clear, specialized red-team planning niche with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	16 / 20 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/roe-template/SKILL.md
Commit: 0cf691e

Reviewed: 2 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.