BC windows-privilege-escalation
Provide systematic methodologies for discovering and exploiting privilege escalation vulnerabilities on Windows systems during penetration testing engagements.
Provide systematic methodologies for discovering and exploiting privilege escalation vulnerabilities on Windows systems during penetration testing engagements.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
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 · 10
✓ No critical or high findings
Medium and low: 10
-
low Risky intent
intent-offensive-securityreferences/detailed-guide.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Windows Privilege Escalation - Detailed Guide
-
low Risky intent
intent-offensive-securityreferences/detailed-guide.md:7Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Provide systematic methodologies for discovering and exploiting privilege escalation vulnerabilities on Windows systems during penetration testing engagements. This skill covers system enumeration, cr
-
low Risky intent
intent-offensive-securityreferences/detailed-guide.md:16Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Authorization**: Written permission for penetration testing activities
-
low Risky intent
intent-offensive-securityreferences/detailed-guide.md:21Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Privilege Escalation Path**: Identified vector to higher privileges
-
low Risky intent
intent-offensive-securityreferences/detailed-guide.md:104Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### 2. Credential Harvesting
-
low Dangerous commands
cmd-execpolicy-bypassreferences/detailed-guide.md:288Runs PowerShell with execution policy bypassed (documentation of a security skill)powershell.exe -ExecutionPolicy Bypass -File Sher…ps1
security skill -
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)description: "Provide systematic methodologies for discovering and exploiting privilege escalation vulnerabilities on Windows systems during penetration testing engagements."
quoted -
low Risky intent
intent-offensive-securitySKILL.md:26Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Windows Privilege Escalation
-
low Risky intent
intent-offensive-securitySKILL.md:42Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Credential dumping triggers security alerts
-
low Risky intent
intent-offensive-securitySKILL.md:118Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### Example 5: Credential Harvesting from Registry
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "date_added"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1049 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 159: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.