Content
81%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, well-structured instruction skill with a clear sequenced workflow and explicit validation checkpoints. Its main weakness is minor promotional padding in the intro and a few abstract step descriptions that lack executable examples.
Suggestions
Trim the opening 'It has caught real bugs...' sentence to a brief factual note or move it to the README; the invariant description is sufficient context.
Add one concrete stack-primitive example (e.g., a one-line call showing the SIGSTOP/SIGCONT zombie pattern) so the 'Add the stack primitive' step is executable rather than abstract.
The 'Where things live' file map is borderline inline reference material; if it grows, consider splitting it into a separate file referenced from SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and assumes Claude's competence (Rust, cargo, harness internals), but the opening 'It has caught real bugs (eviction data loss, unordered lifecycle shutdown, coordinator failover stalls) precisely because...' is promotional context that could be trimmed. | 4 / 5 |
Actionability | Provides real file paths, enum/flag names (GateArgs, ChaosEvent, chaos_timeline()), and a copy-paste bash build+run block, but some steps remain abstract ('Add the stack primitive if the disruption is new (prefer process signals and etcd operations)') without an executable example. | 4 / 5 |
Workflow Clarity | The 'Adding a chaos scenario' section is a clear 6-step sequence with an explicit validation checkpoint ('three consecutive green runs is the bar') and a feedback loop ('If timing makes a scenario a lottery, make it deterministic'), reinforced by the red/green 'Validating a fix' section. | 5 / 5 |
Progressive Disclosure | Well-organized sections (When to add, Where things live, Adding a chaos scenario, Validating a fix) with one-level-deep, clearly signaled references to the harness README; no bundle files exist, and at ~80 lines the simple-skill exception does not apply, leaving minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |