Content
90%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.
An excellent operational skill: lean, table-driven, and copy-paste executable, with strong error-recovery notes. The only gaps are a missing explicit stack-verification checkpoint before running suites and some deep reference material (chaos internals, full flag list) that could be split out.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with project-specific operational facts in tables and command blocks — flags, service sets, URLs, credentials, gotchas — with zero padding or explanations of concepts Claude already knows; every section earns its tokens. | 5 / 5 |
Actionability | Fully executable throughout: copy-paste commands (`./local-stack.sh up --db psql --ui`, `chaos cut postgres`, `npm --prefix gravitee-am-test run ci:gateway`), exact URLs, ports, and admin credentials cover the common cases. | 5 / 5 |
Workflow Clarity | Sequence is clear (choose mode → `up` → run the matching suite) with a fail-fast Docker check and good recovery guidance ("use `--build` … Use when a container crashes on boot", "`chaos heal --all` before concluding AM is broken"), but there is no explicit verification step (e.g., check `status` before running suites). | 4 / 5 |
Progressive Disclosure | Well-sectioned single-file skill with a clearly signaled one-level reference ("See `docker/local-stack/README.md` for the full reference"); the flag table and chaos deep-dive are borderline inline reference material that could live in a separate file. | 4 / 5 |
Total | 18 / 20 Passed |