CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sqli

SQL Injection — automated and manual exploitation of unsanitized SQL queries. Covers Union-based, Error-based, Blind (Boolean/Time-based), and Stacked queries. Includes sqlmap automation with WAF bypass tamper scripts.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/exploit/web/sqli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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, command-dense body whose escalation decision table and confirmation criteria are exemplary, but it is weakened by redundancy across four overlapping blind-SQLi sections, a batch extraction blueprint with no completion validation, and a total absence of progressive disclosure into reference files.

Suggestions

Consolidate the four blind-SQLi sections (Fast-Path, Manual-vs-Tool Decision Rule, Bulk Extraction Strategies, Parallel Blueprint) into a single escalation workflow — the same 'do not iterate manual probes after confirmation' rule is stated three separate times.

Add a completion-validation step to the parallel extraction blueprint: after reconstruction, assert that all STR_LEN position files exist and the result length equals STR_LEN before treating the secret as extracted.

Move the DBMS-specific manual payloads and the parallel extraction script into references/ files (e.g., references/payloads.md, references/blind-blueprint.sh), keeping SKILL.md as a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body is command-dense with no conceptual padding ('sqlmap -u ... --batch --dbs', payload blocks), but the blind-SQLi discipline is restated across four overlapping sections — 'Do NOT iterate manual character extraction', 'the next bash call MUST escalate to sqlmap', 'HARD RULE: ... not a single-character sequential probe' — that could be consolidated. Fits 'mostly efficient but could be tightened' (3) better than 'minor trims' (4).

3 / 5

Actionability

Mostly executable guidance — the sqlmap invocations, hash-cracking loop, and the parallel extraction blueprint are near copy-paste ready with concrete parameters (--technique=BT --threads=5). Not 5: the '<KNOWN_TRUE_MARKER>' placeholder requires establishing a true-response baseline that is never demonstrated, and the blueprint's inner 'seq 32 126' sequential loop contradicts the binary-search strategy taught in the section above it.

4 / 5

Workflow Clarity

Sequences are clear with explicit confirmation criteria ('time delay ≥5s OR boolean diff in response') and a state→action decision table including 'Submit/verify the partial result before launching a second harness'. However, the flagship batch workflow (20-concurrent-job parallel extraction) lacks completion validation — the reconstruct step globs pos_*.txt and silently skips missing positions, so a dropped request yields a short/garbled string undetected; per the batch-operations cap this holds at 3 rather than 4.

3 / 5

Progressive Disclosure

Section headers are clear and well-ordered, but this is a ~260-line monolith with zero external files — the DBMS-specific manual payloads and the 45-line parallel extraction blueprint script are inline content that belongs in separate reference files. Fits 'some structure but content that should be separate is inline' (3); not 2 since organization within the file is good, and not 4 since there is no reference split at all for a file this long.

3 / 5

Total

13

/

20

Passed

Description

75%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, third-person description that names concrete techniques and tooling comprehensively, but the description field itself lacks an explicit 'Use when...' trigger clause — that guidance is relegated to metadata.when_to_use — which caps completeness and slightly limits trigger coverage within the field.

Suggestions

Append a 'Use when...' clause to the description field itself (e.g., 'Use when a target shows SQL errors, unsanitized query parameters, or a task mentions SQL injection, sqli, sqlmap, union select, or database dumps.') so completeness does not depend on the separate when_to_use metadata.

Fold the highest-value trigger synonyms from metadata.when_to_use — 'sqli', 'database dump', 'single quote', 'information_schema' — into the description text to raise trigger-term coverage within the field.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'automated and manual exploitation of unsanitized SQL queries', 'Union-based, Error-based, Blind (Boolean/Time-based), and Stacked queries', 'sqlmap automation with WAF bypass tamper scripts' — with comprehensive coverage of the domain in third-person voice ('Covers', 'Includes'). Not 4: technique classes, tooling, and bypass methods are all named with no notable gap.

5 / 5

Completeness

The 'what' is clear ('exploitation of unsanitized SQL queries... Covers Union-based, Error-based, Blind... Includes sqlmap automation') but the description field itself contains no 'Use when...' clause — the trigger guidance lives entirely in a separate metadata.when_to_use field. Per the guideline, a missing use-when clause caps completeness at 3; not 4 because the evaluated field has no explicit trigger phrasing.

3 / 5

Trigger Term Quality

'SQL Injection', 'sqlmap', 'WAF bypass', and the named technique classes are natural terms a user would say, but common variants like 'sqli', 'database dump', and DB names (mysql, postgresql) appear only in metadata.when_to_use, not in the description field itself. Good coverage with a few natural terms missing, so 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

'SQL Injection' combined with named technique classes and sqlmap forms a clear niche with distinct triggers and minimal overlap risk against adjacent web-exploitation skills (XSS, SSRF, command injection).

5 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

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