CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blind-sqli

Blind SQL injection under hostile WAF — manual bypass playbook for when sqlmap fails because common tokens (SUBSTRING, IF, AND, WHERE, single quotes) are filtered. Covers token-fingerprinting probe loops, arithmetic-multiplication boolean evaluation, hex-encoded literals, and exponential-probe binary search. Loaded on top of sqli.md when the binary oracle exists but tampers can't pass the WAF.

Quality

91%

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

88%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 excellent operational playbook: executable scripts, a clear step sequence, and real validation gates (oracle check, sanity gate) before expensive batch extraction. The only weaknesses are minor verbosity in a few asides and a single-file layout that, while well-organized, is denser than the ideal overview-plus-references split.

Suggestions

Trim the cost-justification asides ('saves ~70% of the round-trip cost', 'Saves you from re-checking which quote variant...') — the scripts and the step sequence already justify the approach.

Consider moving the WAF substitution matrix and the anti-patterns section into a small references/ file to keep SKILL.md as a leaner overview, which would also raise progressive disclosure structure.

EXTRACT_EXPR is referenced in Steps 4-6 but never given a worked example (e.g. the concrete information_schema subquery from Step 2); one fully assembled example would make the extraction scripts immediately runnable end-to-end.

DimensionReasoningScore

Conciseness

Mostly lean operational prose where the one conceptual explanation (MySQL boolean-as-integer arithmetic) is essential to the technique. Minor trims possible, e.g. 'One script run beats 15 sequential bash calls (saves ~70%...)' and 'Saves you from re-checking which quote variant the WAF blocked this iteration.'

4 / 5

Actionability

Copy-paste-ready bash probe and extraction scripts with env-var parameterization, concrete payloads ("x\"||1=1#"), a bench-tested substitution table, and a per-position extraction loop — specific examples cover the common cases.

5 / 5

Workflow Clarity

Clear sequenced workflow (oracle confirmation → token fingerprint → substitution → hex literals → length discovery → extraction) with explicit validation checkpoints for the batch request loops: the ≤2-minute oracle gate, the filter probe, and the Step 6 sanity gate that aborts before a multi-hundred-request extraction on an empty result.

5 / 5

Progressive Disclosure

Single-file skill with no bundle files; sections are clearly headed and all content is needed inline for the coherent playbook. It exceeds the 'under 50 lines' simple-skill case and the substitution matrix/anti-patterns could arguably live in reference files, so structure is good but not exemplary.

4 / 5

Total

18

/

20

Passed

Description

92%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: concrete capabilities, explicit when-to-use conditions, correct third-person voice, and clear positioning against the companion sqli.md skill. The only gap is that a few natural trigger phrasings live in metadata.when_to_use instead of the description itself.

DimensionReasoningScore

Specificity

Lists four concrete, named techniques ('token-fingerprinting probe loops, arithmetic-multiplication boolean evaluation, hex-encoded literals, and exponential-probe binary search') plus the triggering condition — comprehensive coverage of the playbook's capabilities with no vague filler.

5 / 5

Completeness

Explicitly answers what ('manual bypass playbook... Covers token-fingerprinting probe loops...') and when ('Loaded on top of sqli.md when the binary oracle exists but tampers can't pass the WAF') with concrete trigger conditions.

5 / 5

Trigger Term Quality

Natural phrases like 'Blind SQL injection', 'sqlmap fails', 'hostile WAF', and 'tamper' are present, but a few common user phrasings (e.g. 'boolean-based', 'bypass') appear only in metadata.when_to_use rather than the description field itself.

4 / 5

Distinctiveness Conflict Risk

Clear niche (blind SQLi under WAF token filtering) explicitly scoped as a companion to sqli.md that applies only after sqlmap --tamper fails — minimal overlap with the general sqli skill.

5 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/exploit/web/blind-sqli/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.