Content
71%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, dense operational reference: highly actionable per-channel code with setup, OPSEC, detection, error-handling, and a well-constructed decision gate. Its main weaknesses are the monolithic single-file layout — six full implementations inlined where per-channel reference files belong — and the absence of explicit validation/verification steps in the operational sequences.
Suggestions
Split each channel's full implant code into one-level-deep reference files (e.g., references/discord-c2.md, references/telegram-c2.md), leaving SKILL.md as an overview with the decision gate, comparison tables, and pointers.
Remove the Quick Reference duplication — either keep it as the only inline snippets or drop it in favor of the per-channel sections.
Add an explicit first-run verification step per channel (e.g., confirm beacon check-in/registration succeeds before entering the main loop) to close the workflow-validation gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense operational content — full implant code, setup steps, comparison tables, and a decision tree — with almost no explanation of concepts Claude already knows. Minor redundancy keeps it off anchor 5: the Quick Reference repeats snippets shown verbatim in the channel sections, and the opening paragraph spells out the rationale for evading network monitoring that a C2 audience can infer. | 4 / 5 |
Actionability | Every channel gets concrete setup commands and largely copy-paste-ready Python/Bash/Solidity with realistic error handling. Two gaps hold it below fully-executable anchor 5: "ABI = [...] # ABI from compilation" is an unexplained placeholder, and the Ethereum implant's response posting is a commented-out stub with only a hint to use a side channel. | 4 / 5 |
Workflow Clarity | Each channel follows a coherent Setup → Implant → OPSEC sequence, the Decision Gate tree clearly sequences channel selection by outbound constraints, and the Error Handling & Edge Cases table (issue → symptom → resolution) supplies recovery checkpoints. It falls short of anchor 5 only because there are no explicit verification steps (e.g., confirm the first beacon check-in before relying on a channel) and no validate-then-proceed loops. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are all absent), so ~480 lines of six complete implant implementations live inline in SKILL.md. In-file structure is good (quick reference, clear headers, tables, decision gate), but the per-channel implementations are exactly the content that should be split into one-level-deep reference files with SKILL.md as an overview — matching anchor 3's "content that should be separate is inline" rather than anchor 4's "most content is appropriately placed". | 3 / 5 |
Total | 15 / 20 Passed |