CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

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/analyst/bounty-hunting/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 skill body is a tight, actionable white-box hunting playbook with a clearly sequenced loop and an explicit prove-or-discard validation gate that appropriately caps false-positive risk. It stays lean and well-structured with only minor verbosity and no bundle-file overhead.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence (e.g. lists sinks and sources without explaining what they are), with only minor padding such as the bounty-payout ranking rationale in 'High-Value Vulnerability Classes'.

4 / 5

Actionability

It provides concrete executable commands (find, semgrep, grep) and a complete validate_finding checklist with required fields, though the kg_add_node/validate_finding calls are assumed-available tools rather than fully self-contained runnable snippets.

4 / 5

Workflow Clarity

The core loop is explicitly sequenced as Steps 1-5 with a hard validation checkpoint in Step 5 ('If you cannot reproduce it, it is NOT a finding'), plus a 'What NOT to Do' guardrail list — a clear feedback loop for a destructive/batch-style submission workflow.

5 / 5

Progressive Disclosure

Content is well-organized into focused sections (Target Assessment, Methodology, Vuln Classes, Report Convention, What NOT to Do) with no nested references; no bundle files exist, which is appropriate for this length, though some sections (vuln-class detail, report examples) could be split into references if it grew.

4 / 5

Total

17

/

20

Passed

Description

76%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 concise and clearly answers both what the skill does and when to load it, with strong trigger terms tied to bounty-program signals. Its main weakness is specificity — it describes the methodology domain without enumerating the concrete hunting actions.

Suggestions

Add 1-2 concrete actions to the description (e.g. 'Trace untrusted input to dangerous sinks and prove exploitability with a validated PoC') to lift specificity above a single domain label.

Include a couple of natural synonyms users might say ('vulnerability research', 'responsible disclosure') to round out trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain ('bug bounty white-box hunting methodology') but the only concrete action implied is reading/analyzing open-source projects for vulnerabilities — it lists no explicit actions like 'trace', 'exploit', or 'report'.

3 / 5

Completeness

It states the 'what' ('Bug bounty white-box hunting methodology') and an explicit 'Load when...' trigger clause enumerating concrete scenarios, satisfying both what and when clearly.

5 / 5

Trigger Term Quality

It includes natural trigger terms a user might say ('bug bounty', 'open-source project', 'security advisory program', 'responsible disclosure policy') plus platform names (H1, Bugcrowd), giving good keyword coverage with a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

The trigger is narrowly scoped to open-source projects with a formal advisory/bounty/disclosure program, making it distinct from general code-review or scanning skills, with only minor overlap risk with general security-analysis skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
Reviewed

Table of Contents

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.