AC Broken Authentication Testing
This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential…
As a process C 60/100 · Has gaps — weak spots: result and completion, consistency, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (Broken Authentication Testing) differs from the folder (broken-authentication)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 81 steps
- 100Execution cost. Instruction body is 3029 tokens
- 100Running it twice. Mutating operations check current state
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 397: enough signal without eating the budget
- +4Structure: 80 headings
- +3Step-by-step instructions: 81 items
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.