sql-injection-testing

This skill should be used when the user asks to "test for SQL injection vulnerabilities", "perform SQLi attacks", "bypass authentication using SQL injection", "extract database information through injection", "detect SQL injection flaws", or "exploit database query vulnerabilities". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/sql-injection-testing/SKILL.md

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.

Highly actionable payload reference with a clear phased workflow, but it is over-long for a single SKILL.md, carries redundant examples, and lacks the validation feedback loops expected for database-operation skills.

Suggestions

Add explicit validation checkpoints to the workflow (e.g., confirm injection with a true/false response pair before extracting, verify column count before UNION) and a validate→fix→retry loop for failed payloads.

Move the payload catalogs and worked examples into files under references/ (e.g., payloads.md, examples.md) and keep SKILL.md as a concise overview with one-level-deep links, reducing redundancy with the Quick Reference.

De-duplicate content that appears in both the Phases and the Examples/Quick Reference sections to trim token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational payloads rather than padded concept explanations, but it runs ~450 lines with notable redundancy — Examples 1–3 re-duplicate Phase 2/3 payloads and the Quick Reference re-lists the same payloads — so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready SQL payloads for each technique (UNION, error-based, blind, time-based, OOB), full HTTP request examples, and tool mentions (SQLMap, Burp) that cover the common cases concretely.	5 / 5
Workflow Clarity	The four-phase sequence (Detection → Exploitation → Auth Bypass → Filter Bypass) is clear, but destructive/batch database operations lack explicit validate→fix→retry feedback loops, so the workflow-clarity cap of 3 for database operations applies.	3 / 5
Progressive Disclosure	Section headers are well organized, but the skill is a monolithic ~450-line single file with payload catalogs and worked examples that belong in separate reference files; no references/ bundle exists to offload them.	3 / 5
	Total	14 / 20 Passed

Description

90%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, well-structured description with explicit trigger guidance and a distinct niche; its only weakness is mild over-claim language ("comprehensive") and somewhat generic action verbs that keep specificity from the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ("identifying, exploiting, and understanding SQL injection attack vectors") but the verbs are high-level and "comprehensive techniques" is an over-claim rather than concrete capability detail.	3 / 5
Completeness	Explicitly states what the skill does ("provides comprehensive techniques for identifying, exploiting, and understanding…") and when to use it via concrete trigger phrases, answering both what and when in third-person voice.	5 / 5
Trigger Term Quality	Quotes many natural user phrases ("test for SQL injection vulnerabilities", "perform SQLi attacks", "bypass authentication using SQL injection", "detect SQL injection flaws") including the SQLi synonym, giving comprehensive trigger coverage.	5 / 5
Distinctiveness Conflict Risk	Targets a clear SQL injection niche with distinct, domain-specific triggers that are unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	18 / 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/sql-injection-testing/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.