CC hunt-xxe
Hunting skill for xxe vulnerabilities.
Hunting skill for xxe vulnerabilities.
As a process C 57/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
ProcedureWordAWSExcelPowerPointSecuritytype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: hunt-xxe (sickn33/agentic-awesome-skills)
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securitySKILL.md:283Offensive-security / dual-use content (legitimate for authorised testing; review intended use)<!-- Chunked transfer encoding to bypass WAF inspection -->
-
low Risky intent
intent-offensive-securitySKILL.md:382Offensive-security / dual-use content (legitimate for authorised testing; review intended use)**Business impact**: Full internal service compromise across the majority of the production domain fleet; potential for credential theft and lateral movement.
-
low Risky intent
intent-offensive-securitySKILL.md:392Offensive-security / dual-use content (legitimate for authorised testing; review intended use)**Business impact**: Complete AWS credential compromise from a single authenticated API call, enabling privilege escalation from application-level user to cloud infrastructure administrator.
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
body-longSKILL.md body ≈ 6723 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "license_source" - note
frontmatter-keyunknown frontmatter key "sources" - note
frontmatter-keyunknown frontmatter key "report_count" - note
edit-residuethe text marks something as outdated (lines 80, 235, 332, 338, 450, 454): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 57/100
- 0When it triggers. No condition that starts the skill
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, python, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6723 tokens
- 100Steps. 58 steps
- 100Consistency. Name and required fields are in place
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
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)
- +3Description length 38: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 38 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (21 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.