Content
77%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.
The body is an highly actionable CLI operating manual with exemplary verification and error-recovery workflows. Its weaknesses are redundancy (duplicated read-only guidance, fixture meta-commentary) and a monolithic single-file structure that inlines material better split into reference files. Overall a strong, executable skill document with moderate token-efficiency and organization improvements available.
Suggestions
State the read-only restriction once and drop the golden-fixture meta paragraph from the body, keeping only operator-relevant install/usage contract.
Move the Paths-and-state env-var matrix, MCP HTTP/TLS configuration, and Output Delivery sink semantics into reference files linked from a short overview section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with CLI-specific contract detail, but the read-only restriction is stated twice ("Do not activate this CLI for requests that require creating..." and "Read-only — do not use this CLI for create, update, delete..."), the golden-fixture paragraph is meta-commentary irrelevant to operating the CLI, and edge-case notes like the Go fallback and fleet-precedence paragraph could be trimmed. This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'; it is not a 4 because these are more than minor instances, and not a 2 because it never explains concepts Claude already knows. | 3 / 5 |
Actionability | Every section provides copy-paste-ready commands: the npx install line, `learn-disabled-example-pp-cli --version` verification, `which "<capability>"` with documented exit codes, auth token piping, profile subcommands, and the `--deliver` sink table. Guidance is fully executable with the exit-code and envelope contracts needed to consume output correctly; no gaps remain. | 5 / 5 |
Workflow Clarity | Sequences are explicit with validation checkpoints and error-recovery loops: install → verify version → ensure PATH with "Do not proceed with skill commands until verification succeeds", a numbered argument-parsing decision tree, Direct Use steps 1–4 with "If ambiguous, drill into subcommand help", plus `doctor`, `--dry-run`, and exit-code-7 retry guidance. This matches 'Clear sequence with explicit validation steps; feedback loops for error recovery'. | 5 / 5 |
Progressive Disclosure | The ~210-line body is well-sectioned but entirely inline with zero reference files — reference-type material such as the Paths and state env-var matrix, MCP HTTP/TLS configuration, and delivery-sink semantics clearly belongs in separate files. This fits 'Some structure but could be better organized... content that should be separate is inline'; it is not a 2 because section structure is strong, and not a 4 because there are no references at all and the single file carries substantial reference material. | 3 / 5 |
Total | 16 / 20 Passed |