Content
72%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A dense, highly actionable command reference with strong coverage of Windows and Linux privesc techniques, but it lacks structured validation checkpoints for its destructive operations and is a single large file with no progressive disclosure into bundle references.
Suggestions
Add explicit validation checkpoints for destructive operations, e.g. after a Potato/service-abuse run add a step to verify SYSTEM (`whoami /priv` or `whoami` shows SYSTEM) before proceeding to credential extraction, and re-validate after service restarts.
Split the per-tool detail tables and detection-signature reference into separate bundle files (e.g. references/potato-family.md, references/detection.md) and point to them from SKILL.md to apply progressive disclosure.
Move the large detection-rules block into a dedicated references file so the main SKILL.md reads as an overview plus quick-reference rather than a monolithic knowledge base.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly terse command snippets with brief comments and assumes Claude's competence; minimal concept over-explanation, though a handful of inline explanatory notes and tables add minor length that could be trimmed. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout — GodPotato, PrintSpoofer, sudo -l exploit patterns, SUID vectors, cron injection — covering the common cases with specific, runnable examples. | 5 / 5 |
Workflow Clarity | There is an enumerate-before-exploit preamble and a Decision Gate for next steps, but the destructive/batch operations (kernel exploits, service restarts, persistence) lack explicit validate-then-proceed feedback loops, which per the rubric caps workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | No bundle files exist and the ~490-line SKILL.md is a single monolithic file with good section headers but no one-level-deep external references; substantial reference material (per-tool details, detection rules) that could live in separate files is inlined. | 3 / 5 |
Total | 15 / 20 Passed |