CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deconfliction-template

Deconfliction plan generator: distinguish authorized engagement activity from real incidents.

Quality

74%

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/deconfliction-template/SKILL.md
SKILL.md
Quality
Evals
Security

Deconfliction Plan Generator

When to Use

When designing or revising deconfliction, use the system-provided plan/roe.json and any current CONOPS and contact plan as context.

Workflow

  1. Preserve confirmed decisions from an existing plan. Use the same engagement_name as RoE.
  2. Record approved source IPs, user-agent markers, tool hashes, or testing windows in identifiers. Each entry needs type and value; put context in description. Do not invent infrastructure or claim a marker is configured when it is only proposed.
  3. Set notification_procedure for the active phases authorized by RoE. Use the confirmed SOC contact from the contact plan when one exists. An absent contact or endpoint does not authorize contacting a third party.
  4. Populate deconfliction_code only with an operator-confirmed code; otherwise retain its empty default. Identify missing material coordination decisions.
  5. Validate plan/deconfliction.json against DeconflictionPlan. Deconfliction identifiers never expand scope or override abort triggers. Bundle publication follows the selected planning workflow.

Document schema (derived from the validator's model)

plan/deconfliction.json must validate against DeconflictionPlan. Fields not listed here are not part of the model and are ignored by the validator.

fieldtyperequiredallowed values / nested keys
engagement_namestryes
identifierslist[DeconflictionEntry]noeach object: type, value, description
notification_procedurestrno
soc_contactstrno
deconfliction_codestrno

DeconflictionEntry object:

fieldtyperequiredallowed values
typestryes
valuestryes
descriptionstrno
Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/soundwave/deconfliction-template/SKILL.md

Last updated
First committed

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.