CtrlK
BlogDocsLog inGet started
Tessl Logo

hunt-sqli

Hunting skill for sqli vulnerabilities. Built from 12 public bug bounty reports including modern NoSQL injection (Rocket.Chat CVE-2021-22911 MongoDB $regex, Mongoose ORM CVE-2024-53900 $where bypass), modern ORM raw-fragment SQLi (Django CVE-2024-42005, Sequelize GHSA-wrh9-cjv3-2hpw), second-order SOQL injection (HackerOne Salesforce), time-based blind SQLi in GraphQL resolvers, and SQLi on OIDC-proxy backends. Use when hunting SQLi on any target. Dedicated NoSQL operator injection (MongoDB/CouchDB $where/$regex/$ne) is owned by hunt-nosqli — NoSQL appears here only as adjacent ORM/WAF context.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 hunting skill with concrete payloads, commands, and a validation gate that gives Claude exactly what to do. Its main weakness is structure: all content lives in one large SKILL.md with no bundle files or one-level-deep references, hurting progressive disclosure.

Suggestions

Split the bulky reference material into bundle files — e.g. references/payloads.md for the payload trees, references/waf-bypass.md for the bypass catalog, and references/cve-citations.md for the disclosed-report list — then link to them one level deep from SKILL.md.

Tighten or trim the 'Crown Jewel Targets' and 'Real Impact Examples' narrative sections, keeping only the operational signals (URL patterns, asset types) and moving the illustrative prose into a reference file.

Add inline per-step validation cues within the 'Step-by-Step Hunting Methodology' (e.g. 'confirm before proceeding') rather than consolidating all validation in the separate Gate 0 section.

DimensionReasoningScore

Conciseness

Largely efficient with dense code blocks, payloads, and command lists rather than explaining concepts Claude already knows, though the 'Crown Jewel Targets' and 'Real Impact Examples' scenarios add narrative/motivational padding that could be trimmed.

4 / 5

Actionability

Fully copy-paste ready: exact sqlmap flags (--level=3 --risk=2), curl time-based detection commands, grep patterns for JS source hunting, Burp Intruder column-enumeration lists, and concrete payloads for every technique family.

5 / 5

Workflow Clarity

A clearly sequenced 10-step methodology plus a 'Gate 0 Validation' section with explicit pre-report checkpoints and proof requirements (validation present, so the destructive/batch cap does not apply), though per-step validation checkpoints are consolidated in Gate 0 rather than inline at each step.

4 / 5

Progressive Disclosure

Well-structured with clear section headers, but the ~420-line body is monolithic — no references/scripts/assets bundle exists and large blocks (full CVE citation list, WAF-bypass catalog, payload trees) that would benefit from one-level-deep reference files are fully inlined.

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, specific description that names concrete SQLi families with CVE evidence and explicitly carves out scope from hunt-nosqli. It answers both what and when, though the trigger clause is broad and a fully-spelled 'SQL injection' synonym would widen natural-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete SQLi subtypes (NoSQL injection, ORM raw-fragment SQLi, second-order SOQL, time-based blind in GraphQL resolvers, OIDC-proxy backends) backed by named CVEs — comprehensive concrete coverage of the hunting domain.

5 / 5

Completeness

Clearly states what it does (hunt sqli across named technique families) and has an explicit 'Use when hunting SQLi on any target' trigger, but the 'when' clause is somewhat broad/generic rather than enumerating concrete triggering situations.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ('hunting SQLi', 'sqli vulnerabilities', 'NoSQL injection', 'GraphQL resolvers', 'OIDC-proxy') with both the 'sqli' acronym and 'SQLi' form, but omits the fully spelled-out 'SQL injection' synonym.

4 / 5

Distinctiveness Conflict Risk

Actively manages boundaries by stating dedicated NoSQL operator injection 'is owned by hunt-nosqli' and that NoSQL appears here only as adjacent ORM/WAF context — clear niche with minimal conflict risk.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
elementalsouls/Claude-BugHunter
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.