conops-template

Concept of Operations document creation — executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

92%

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

The body is concise, actionable, and laid out as a clear workflow with explicit validation, but progressive disclosure is undercut by a broken reference to the schema quick-reference file that defines the very documents the skill must produce.

Suggestions

Fix or remove the dangling reference to ../references/schema-quick-reference.md; either create the file under references/ and update the path, or inline the CONOPS/ThreatActor/KillChainPhase/DeconflictionPlan schema fields so the skill can generate conforming documents.

Add an explicit error-recovery note to Step 4 (e.g., "If any check fails, revise the affected document and re-validate") to make the validation feedback loop explicit.

Include a minimal example of a generated plan/conops.json snippet so the abstract schema reference becomes immediately copy-pasteable guidance.

Dimension	Reasoning	Score
Conciseness	The lean body assumes Claude's competence, never explains concepts Claude already knows, and keeps every section actionable, matching the anchor for lean and efficient content.	3 / 3
Actionability	Provides concrete, specific guidance — a numbered interview script with multiple-choice options, named output files (plan/conops.json, plan/deconfliction.json), a 5-item validation checklist, and 5 generation rules — which is actionable for an instruction-only skill.	3 / 3
Workflow Clarity	A clear 4-step sequence (Interview, Design Kill Chain, Generate Documents, Validate) culminates in an explicit validation checklist; this is a planning/generation skill rather than fragile or destructive ops, so the missing feedback-loop cap does not apply.	3 / 3
Progressive Disclosure	The overview is well-organized with one-level-deep references (references/kill-chain-templates.md exists), but the Prerequisites reference to ../references/schema-quick-reference.md — the file defining the core output schemas — is a broken/dangling path, breaking navigation for the most important reference.	2 / 3
	Total	11 / 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 clearly enumerates concrete capabilities and occupies a distinct niche, but it omits an explicit "when to use" trigger clause and leans on domain jargon rather than natural user phrasing.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when creating a CONOPS, designing a red-team operation, or building a threat model") to lift completeness and trigger_term_quality.

Soften niche jargon with natural phrasings users would actually say (e.g., "red team plan", "operation design", "attack plan") to broaden trigger coverage.

Move the metadata.when_to_use triggers into the description field so the firing guidance is in the place the skill loader evaluates.

Dimension	Reasoning	Score
Specificity	Lists six concrete actions — "executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	The "what" is strong, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "Concept of Operations", "kill chain", and "deconfliction" are niche jargon; the natural user triggers ("create CONOPS", "design the operation", "build threat model") appear only in metadata.when_to_use, not the description, and common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The red-team planning niche (CONOPS, threat actor profiling, kill chain, deconfliction) is highly specific with distinct triggers and is unlikely to fire for the wrong skill.	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/conops-template/SKILL.md
Commit: e34afba

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