CtrlK
BlogDocsLog inGet started
Tessl Logo

windows-privilege-escalation

This skill should be used when the user asks to "escalate privileges on Windows," "find Windows privesc vectors," "enumerate Windows for privilege escalation," "exploit Windows misconfigurations," or "perform post-exploitation privilege escalation." It provides comprehensive guidance for discovering and exploiting privilege escalation vulnerabilities in Windows environments.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/windows-privilege-escalation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 command reference with excellent executable coverage, but its monolithic structure and absence of validation checkpoints in a risky exploit workflow hold back progressive disclosure and workflow clarity.

Suggestions

Add explicit validation checkpoints between workflow phases (e.g., 'Confirm shell is SYSTEM via whoami' after each escalation attempt) to lift workflow clarity past the destructive-operation cap.

Split the kernel-exploit catalog and Quick Reference tables into separate reference files (e.g., references/kernel-exploits.md) and link to them from SKILL.md to improve progressive disclosure.

De-duplicate commands that appear in both the Core Workflow sections and the Quick Reference/Examples sections to tighten conciseness.

DimensionReasoningScore

Conciseness

A dense, mostly lean command reference that avoids explaining concepts Claude already knows, with only minor redundancy (Quick Reference tables and Examples restate commands from earlier sections).

4 / 5

Actionability

Provides copy-paste-ready PowerShell and tool commands plus five concrete end-to-end examples that cover the common privilege-escalation cases with specific parameters.

5 / 5

Workflow Clarity

A clear numbered 1–6 core workflow exists, but this is a risky exploit skill with no inline validation/verification checkpoints between phases, so the rubric cap of 3 applies despite the sequence.

3 / 5

Progressive Disclosure

The ~490-line SKILL.md is a single monolithic file with no bundle references; headers organize it well, but content that could live in separate reference files (kernel-exploit catalog, command cheatsheet) is fully inlined.

3 / 5

Total

15

/

20

Passed

Description

87%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 that explicitly states both capability and trigger conditions with concrete, natural phrasings. The only soft spot is a slightly abstract 'what' clause that keeps specificity just below the top anchor.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions across the triggers ('enumerate,' 'exploit,' 'escalate,' 'find vectors'), but the 'what' clause ('comprehensive guidance for discovering and exploiting') is mildly abstract, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both 'what' ('provides comprehensive guidance for discovering and exploiting privilege escalation vulnerabilities') and 'when' ('should be used when the user asks to...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Five natural phrases users would say ('escalate privileges on Windows,' 'find Windows privesc vectors,' 'enumerate Windows for privilege escalation') with synonyms; a few common variations are absent, stopping short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear Windows privilege-escalation niche with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
Reviewed

Table of Contents

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.