AB threat-detection
Scan auth and access logs for brute force, injection, path traversal, admin probing and request floods, with triage guidance. Use when analyzing logs for threats or reviewing suspicious activity after an alert.
Scan auth and access logs for brute force, injection, path traversal, admin probing and request floods, with triage guidance.
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Exfiltration
exfil-read-secret-filesassets/sample_access_log.txt:8Reads credential / secret files (test fixture / example file; documentation of a security skill)2026-10-14 09:03:00 198.51.100.25 GET /ping?host=8.8.8.8;cat%20/etc/shadow 200
fixturesecurity skill -
low Risky intent
intent-offensive-securityreferences/threat-indicators.md:9Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Password spraying across multiple accounts
-
low Risky intent
intent-offensive-securityreferences/threat-indicators.md:100Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Privilege escalation attempts
-
low Risky intent
intent-offensive-securitySKILL.md:130Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- The script does not detect privilege escalation, check IP reputation or flag unusual access times.
detector
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 32 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2245 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +3Description length 210: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 32 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.