Content
82%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 strong, highly actionable playbook: copy-paste ready code and commands for every major platform path, dense lookup tables, and a clear numbered workflow with a post-patch validation step. The only notable weaknesses are minor trimming opportunities and the absence of a feedback loop for verifying dynamic bypasses.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and command-driven with almost no concept explanation (no 'what a debugger is' filler), and every table row carries a technique or command. Not a 5 because the intro paragraph ("Each check has a known counter.") and the "Known exemplars" section restate malware-family behaviors Claude largely already knows and could be trimmed. | 4 / 5 |
Actionability | Fully executable, copy-paste ready material covers the common cases: a complete LD_PRELOAD bypass.c with gcc build and run commands, gdb catch-syscall sequences, r2 patching commands ("wx 31c0c3 @ <addr>"), and strings/yara scan commands. Not below 5: the few terse bypass cells ("Patch return to FALSE") are pointers for inherently tool-specific actions, not missing detail for the main paths. | 5 / 5 |
Workflow Clarity | A clear numbered sequence (enumerate → check/bypass tables → dynamic debugger routes → static patching → promote/promote-to-KG) with an explicit validation checkpoint for the destructive step ("Run static-validation YARA post-patch to ensure binary still loads" plus the self-checksum caution). Not a 5 because the dynamic-analysis path lacks feedback loops (e.g., verifying the bypass held before proceeding). | 4 / 5 |
Progressive Disclosure | The file is well-organized with clearly headed sections, and no bundle files exist so nothing is mis-nested. Not a 5 because it exceeds the under-50-line single-file exception and inlines content that could be split ("Known exemplars", "Tool cheat sheet", and the per-technique tables) into one-level-deep reference files, which would keep the SKILL.md a leaner overview. | 4 / 5 |
Total | 17 / 20 Passed |