bounty-hunting-methodology

Bug bounty white-box hunting methodology. Load when the target is an open-source project with a security advisory program, bug bounty, or responsible disclosure policy.

Quality

95%

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

Quality

Content

100%

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

A tight, actionable methodology with concrete commands, a clearly sequenced workflow, and an explicit validation feedback loop, all organized into well-signaled sections without token waste.

Dimension	Reasoning	Score
Conciseness	The body is lean and signal-dense — it never explains basic concepts Claude already knows (e.g. what RCE or a CVSS vector is) and every section earns its tokens, matching the score-3 'Lean and efficient' anchor.	3 / 3
Actionability	Provides executable commands (`find /workspace/target ...`, `kg_add_node(...)`, `validate_finding`, `semgrep`/`grep`) and concrete report-title examples with good/bad pairs, matching the score-3 'Fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Steps 1-5 are explicitly sequenced, and Step 5 includes a validation feedback loop ("Every finding MUST go through validate_finding... If you cannot reproduce it, it is NOT a finding"), satisfying the score-3 anchor for clear sequence with explicit validation steps.	3 / 3
Progressive Disclosure	No bundle files exist; the skill is a single, well-organized SKILL.md with clear section headers and no nested/broken references, so per the simple-skill scoring note well-organized sections suffice for a 3.	3 / 3
	Total	12 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description with explicit trigger guidance and natural user terms; its only weakness is that it describes the methodology at a high level rather than enumerating concrete actions.

Suggestions

Add 2-3 concrete actions to the description (e.g. 'map trust boundaries, trace source-to-sink data flows, and submit validated PoCs') to lift specificity from 2 to 3.

Dimension	Reasoning	Score
Specificity	Quotes "Bug bounty white-box hunting methodology" — it names the domain and activity but does not list multiple concrete actions (e.g. tracing data flows, writing PoCs), matching the score-2 anchor 'Names domain and some actions, but not comprehensive'.	2 / 3
Completeness	States what ("Bug bounty white-box hunting methodology") and an explicit when ("Load when the target is an open-source project with a security advisory program, bug bounty, or responsible disclosure policy"), satisfying the score-3 anchor for both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	"security advisory program, bug bounty, or responsible disclosure policy" are natural terms a user would say, giving good coverage; not score 2 because common variations are present rather than missing.	3 / 3
Distinctiveness Conflict Risk	The combination of bug bounty, security advisory program, and responsible disclosure policy is a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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/analyst/bounty-hunting/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.