Individual skill

finding-protocol

0upvotes

Canonical finding schema, evidence references, verification semantics, and report quality.

packages/decepticon/decepticon/skills/shared/finding-protocol/SKILL.md

Read pinned source

Source commit df879550544d36b6b1e69062f05adae28537adf2

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 6,567
Repository last updated: Nov 7, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent Repository topic
ai Repository topic
cybersecurity Repository topic
hacking Repository topic
langchain Repository topic
langgraph Repository topic
llm Repository topic
generative-ai Repository topic
pentesting Repository topic
pentest Repository topic
engineering Derived category

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 8,441 bytes

Read excerpt


# Finding Protocol — One Canonical File

A canonical finding records observed facts, evidence, independent verification,
and supported report detail in one file. Engagement summaries link to this
canonical finding. Assignment order and completion decisions belong to the
active workflow.

## File Naming Convention

For workflow version 2 use system artifact tools. A vulnerability is saved as
`findings/{severity}_{number}_{title}.md`, e.g.
`findings/high_01_cross-tenant-document-read.md`. The system issues its UUID,
stable human ID (`FIND-01`), number and filename. Never count files to allocate
IDs. UUID relationships survive filename, title and severity changes.