Content
86%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 lean, highly actionable skill body that front-loads project-specific rules, sequences the work in numbered steps, and closes with a concrete verification checklist. The only weaknesses are the absence of a minimal example for the handler and client-wrapper steps, and no error-recovery loop for failing checks.
Suggestions
Add a minimal handler or client-wrapper skeleton (a few lines each) so steps 3 and 5 are copy-paste ready rather than directory pointers.
Add one line of recovery guidance in Verify (e.g., what to do when `make breaking` or `lint:api-contract` fails) to close the feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries repo-specific knowledge Claude cannot infer ("getCachedJson(key, true)", "[(sebuf.http.int64_encoding) = INT64_ENCODING_NUMBER]", "PREMIUM_RPC_PATHS"), with zero padding or explanation of known concepts. Matches the lean anchor-5 example. | 5 / 5 |
Actionability | Concrete commands ("make generate", "npm run lint:api-contract", "npm run test:related") and an inline proto option template make most guidance executable. Minor gaps: "Wrap the generated client in src/services/{domain}/" and the handler implementation step give no example of what the result looks like. | 4 / 5 |
Workflow Clarity | Six clearly numbered steps plus a dedicated Verify section with explicit checks ("make lint and make breaking", "Confirm the generated diff matches the proto change only") and one contingency for toolchain unavailability. It sits between anchors 4 and 5 because there is no fix-and-retry feedback loop when a verification check fails. | 4 / 5 |
Progressive Disclosure | Under 50 lines with well-organized Rules/Steps/Verify sections and clearly signaled one-level-deep references ("Full walkthrough with examples: [docs/adding-endpoints.mdx]", "Framework notes: [CONTRIBUTING.md#...]"). No bundle files exist or are needed, so the simple-skill organization applies. | 5 / 5 |
Total | 18 / 20 Passed |