sqlmap-database-pentesting

This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns from a vulnerable database," or "perform automated database penetration testing." It provides comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

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

The body is highly actionable with real, well-chosen sqlmap commands and good example coverage, but it is over-long for a SKILL.md due to heavy command repetition across sections and lacks both validation checkpoints for destructive operations and any progressive-disclosure file split.

Suggestions

Add validation/safety checkpoints before destructive or batch operations — e.g., confirm authorization and scope before --dump-all/--os-shell, and verify the injection point is confirmed before dumping — to lift workflow clarity above the destructive-operations cap of 3.

Split the large reference material (Supported DBMS table, SQL Injection Techniques table, full Troubleshooting catalog, and Examples) into separate files under references/ and link to them from SKILL.md, keeping only the core workflow and quick-start inline.

De-duplicate the command base: the Core Workflow, Quick Reference Commands table, and Essential Options table repeat the same flags — consolidate into one reference and cross-reference it instead of restating.

Dimension	Reasoning	Score
Conciseness	Mostly command-focused and free of concept over-explanation, but the same base command is repeated across Core Workflow, Quick Reference Commands, Essential Options, Examples, and Troubleshooting, creating noticeable redundancy that could be tightened.	3 / 5
Actionability	Fully executable, copy-paste-ready sqlmap commands with worked examples covering GET/POST injection, bulk scanning, aggressive testing, credential extraction, and OS-shell access — concrete and specific throughout.	5 / 5
Workflow Clarity	Core Workflow is numbered (steps 1–6) and Example 1 shows a staged enumeration progression, but destructive/batch operations (--dump, --dump-all, --os-shell, --file-write) lack any validation or verification checkpoints, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Section headers provide reasonable organization, but at ~390 lines everything is inlined — the DBMS support table, technique reference, examples, and troubleshooting catalog clearly belong in separate reference files, and no external file references exist.	3 / 5
	Total	14 / 20 Passed

Description

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

The description is well-crafted: third-person voice, explicit 'use when' triggers with natural phrasing, and concrete enumeration of capabilities. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'automate SQL injection testing,' 'enumerate database structure,' 'extract database credentials using sqlmap,' 'dump tables and columns,' 'detect and exploit SQL injection vulnerabilities' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly states both what ('comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities') and when ('This skill should be used when the user asks to...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Embeds natural user phrases as quoted triggers ('automate SQL injection testing,' 'extract database credentials using sqlmap,' 'dump tables and columns from a vulnerable database') that a user would plausibly say, with good synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to SQLMap and SQL injection exploitation, a clear niche with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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: zebbern/claude-code-guide
Path: skills/sqlmap-database-pentesting/SKILL.md
Commit: 9d252b3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.