CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bug-chaining

Standalone bug chaining skill — synthesized from omni-killchain, omni-references/chaining-impact, triage-validation, apex-hunter, web2-vuln-classes, bug-bounty, and bb-methodology. Covers the complete chaining mindset: 10-question filter, 15 proven chain patterns (A–O) with payout data, escalation ladders per vuln class, conditional-chain table (when a standalone bug needs a gadget), impact-writing rules, CVSS chain multipliers, and 30-minute chain-or-move decision clock. Use when you have a low/medium finding and want to know how to chain it to Critical, or when strategizing what to hunt for maximum payout. Authorized testing only — bug bounty in-scope, pentest engagement, or CTF.

Quality

83%

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

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

A highly actionable, well-sequenced chaining playbook whose main weaknesses are redundancy across the pattern/conditional-table/tier/quick-reference sections and a monolithic single-file structure with no progressive disclosure. The workflow, decision checkpoints, and concrete commands are excellent.

Suggestions

Deduplicate the open redirect/takeover/SSRF chains that currently appear in both the 15 patterns and the Conditional Chain Table, Payout Tiers, and Quick Reference — keep one canonical pattern description and have the other sections reference it by pattern letter only.

Split the pattern catalog (A–O), per-class escalation ladders, and CVSS multiplier table into references/ files (e.g. references/patterns.md, references/escalation-ladders.md), keeping the filter, workflow, clock, and conditional table in SKILL.md as the overview.

Trim the per-pattern 'Payout range' annotations in the pattern bodies since the same figures are consolidated in the PAYOUT TIERS section.

DimensionReasoningScore

Conciseness

The body is dense and mostly free of concept explanations Claude already knows, but the same chain material repeats across sections — e.g. open redirect → OAuth code theft appears in Pattern C ("Craft: /oauth/authorize?redirect_uri=https://target.com/redirect?to=https://evil.com"), the Conditional Chain Table ("Open redirect | + OAuth redirect_uri → code theft"), Payout Tier B ("Open redirect → OAuth code theft → ATO"), and the Quick Reference ("OAuth callback | Open redirect on any page → code theft (Pattern C)") — and payout figures are stated twice (per-pattern and in tiers). Consolidating these would cut meaningful tokens without losing information.

3 / 5

Actionability

Guidance is copy-paste ready throughout: exact parameters ("redirect=, return_to=, next=, url=, r=, continue="), exact metadata endpoints ("http://169.254.169.254/latest/meta-data/iam/security-credentials/" with IMDSv2/GCP/Azure variants), concrete payloads ("PATCH /api/users/{victim_id} {\"role\":\"admin\"}"), specific tools and flags ("hashcat -a 0 -m 16500", "Turbo Intruder (single-packet)"), and named mass-assignment parameters to test. For an instruction-only skill this is as actionable as it gets.

5 / 5

Workflow Clarity

The CHAIN-FINDING WORKFLOW gives a clear classify → find gadget → prove → maximize sequence with explicit go/no-go checkpoints ("If you cannot write Step 2 as a real HTTP request → the chain isn't proven. Do not submit."), the 10-question filter is a scored checklist with decision rules ("3+ YES → ready to report... 0 YES → kill it"), and the 30-minute clock adds time-boxed decision points with feedback loops ("If stuck: 10-question filter — which Q can you make YES?").

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so everything lives in one ~500-line SKILL.md. Internal section structure and headers are good, but content that naturally belongs in reference files — the 15 pattern write-ups (~200 lines), the escalation ladders, and the CVSS multiplier table — is fully inlined rather than split out, leaving SKILL.md as a catalog rather than an overview.

3 / 5

Total

16

/

20

Passed

Description

83%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 description with explicit what/when structure, concrete component inventory, and clear scope boundaries. Its main flaws are the wasted provenance sentence listing seven source skills and the omission of the very natural 'escalate/escalation' trigger phrasing.

DimensionReasoningScore

Specificity

The description enumerates many concrete components — "10-question filter, 15 proven chain patterns (A–O) with payout data, escalation ladders per vuln class, conditional-chain table..., impact-writing rules, CVSS chain multipliers, and 30-minute chain-or-move decision clock" — which is comprehensive coverage. It falls short of a 5 because the opening provenance sentence ("synthesized from omni-killchain, omni-references/chaining-impact, triage-validation, apex-hunter...") lists source skills rather than capabilities, and phrases like "complete chaining mindset" and "proven" are mild over-claims.

4 / 5

Completeness

Both halves are explicit: the 'what' is a detailed inventory ("Covers the complete chaining mindset: 10-question filter, 15 proven chain patterns (A–O)... CVSS chain multipliers, and 30-minute chain-or-move decision clock") and the 'when' gives two concrete trigger scenarios ("Use when you have a low/medium finding and want to know how to chain it to Critical, or when strategizing what to hunt for maximum payout"), plus an explicit authorization scope.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "bug chaining", "chain it to Critical", "low/medium finding", "payout", "bug bounty", "pentest", "CTF" — phrases a hunter would actually say. A few common variants are missing, notably "escalate/escalation" (the most natural way users describe this need), "vulnerability chaining", and "increase severity/impact".

4 / 5

Distinctiveness Conflict Risk

The chaining-to-Critical niche is distinct and the authorization boundary ("bug bounty in-scope, pentest engagement, or CTF") narrows it further. Minor overlap risk remains: the description itself names sibling skills it was synthesized from ("bug-bounty, and bb-methodology"), and the "strategizing what to hunt for maximum payout" trigger could also fire for a general bug-hunting methodology skill if one exists in the same environment.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (516 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

Awarexone/Agentic-Bug-Hunter

Path

skills/bug-chaining/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.