CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bb-methodology

Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments). Routes to all other skills based on current hunting phase. Also use when asking "what should I do next" or "where am I in the process."

71

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

An exceptionally actionable methodology skill: concrete commands, payloads, decision trees, validation gates, and time-boxed rotation rules throughout, with essentially no wasted tokens. The main structural weakness is that it is a single monolithic document — a master orchestrator of this size would benefit from splitting mindset material and tool tables into one-level-deep reference files.

Suggestions

Split PART 1 (mindset: thinking domains, amateur-vs-pro comparison, anti-patterns) into a one-level-deep reference file (e.g., references/mindset.md) and keep SKILL.md as a routing overview, which would shorten the orchestrator body considerably.

Move the large tool-routing table and per-vuln-class checklists (escalation decision trees, Error-vs-Blind ladder) into reference files per phase or per bug class, keeping only the phase flow and navigation rules inline.

Either bundle the referenced files (docs/auth-sessions.md, bughunter/tools/*) inside the skill's references/ or scripts/ directories, or note that they live in an external shared toolkit, so the paths referenced throughout the body are verifiable.

DimensionReasoningScore

Conciseness

The body is dense and token-efficient — almost everything is checklists, decision trees, and routing tables with no padding on concepts Claude already knows. Not anchor 5 because of light motivational framing ('Hunting is not "find a bug" -- it is "prove an attack scenario."') and the large volume of detail inlined that assumes less competence than needed.

4 / 5

Actionability

Fully concrete, executable guidance throughout: exact commands ('python3 bughunter/tools/lead_board.py ingest target.com', 'ffuf -ac', 'kxss -> dalfox'), specific payloads (''', '"', '{{7*7}}', '${7*7}', 'SLEEP(10)'), and a complete tool-routing table with justifications.

5 / 5

Workflow Clarity

The 5-phase flow is clearly sequenced with explicit navigation rules for the non-linear cases ('New API endpoint discovered during testing -> Return to Phase 2'), a validation gate ('Run /validate (7-Question Gate)... Any fail? -> KILL the finding'), feedback loops (re-test after fix for incomplete patches), and checklists (session end, pre-report).

5 / 5

Progressive Disclosure

Internal structure is good (PART 1/2/3, clear headers, well-organized tables) and inline references are clearly signaled, but the body is a ~400-line monolith with no one-level-deep reference files: content like the mindset section and the large tool-routing table is inlined rather than split, and referenced paths (docs/auth-sessions.md, bughunter/tools/*) are not present in the skill bundle to verify.

3 / 5

Total

17

/

20

Passed

Description

87%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.

A strong orchestrator-style description: it explicitly states what the skill does and gives multiple natural trigger conditions in third person. The only gaps are minor — slightly abstract framing of the core capability and a few missing natural synonyms (e.g., 'recon', 'methodology').

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments)' and 'Routes to all other skills based on current hunting phase'. It falls short of anchor 5 because 'Master orchestrator' is somewhat abstract and the action coverage is composition-based rather than fully concrete.

4 / 5

Completeness

Both questions are explicitly answered with concrete trigger phrases: the what ('Master orchestrator that combines the 5-phase non-linear hunting workflow... Routes to all other skills based on current hunting phase') and the when ('Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost').

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are present: 'bug bounty hunting session', 'switching targets', 'feeling lost about what to do next', 'what should I do next', 'where am I in the process'. Not anchor 5 because common synonyms like 'recon', 'methodology', or 'scope' are missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear router niche ('Master orchestrator... Routes to all other skills') whose triggers — session start, switching targets, feeling lost, 'what should I do next' — do not overlap with phase-specific hunting skills, minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Awarexone/Agentic-Bug-Hunter

Path

skills/bb-methodology/SKILL.md

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.