Content
82%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 tight, highly actionable setup guide: every step has copy-paste commands or complete executable code, and it consistently delivers non-obvious gotchas (CLI/go.mod version pinning, XProtect, Error==Fatal semantics, GinkgoT() interop). Minor room to trim the standard-Go *_test package primer, add a post-bootstrap verification step, and offload detail to reference files.
Suggestions
Trim the section-3 primer on Go's *_test package mechanics ("Go specially permits a *_test package to live in the same directory...") down to the Ginkgo-specific consequence — Claude already knows external test packages.
Add a verification step after bootstrap, e.g. run `go test` or `ginkgo` on the freshly generated suite to confirm the wiring before moving on to authoring specs.
Consider moving the dot-import alternatives catalog (section 4) into a reference file linked from SKILL.md to slim the main body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Quotes: "Go specially permits a *_test package to live in the same directory as the package it tests, compiled as a separate package" and "is the single go test entry point" re-explain standard Go concepts Claude already knows. The rest is lean, non-obvious Ginkgo knowledge ("The CLI version must match the github.com/onsi/ginkgo/v2 version in your go.mod", "Error/Errorf == Fatal/Fatalf", the XProtect note) with no padding — efficient with minor trims available, not the 3 level which requires more substantial unnecessary explanation. | 4 / 5 |
Actionability | Quotes: "go install github.com/onsi/ginkgo/v2/ginkgo", "ginkgo bootstrap", the complete executable suite_test.go listing, "assert.Equal(GinkgoT(), foo{}.Name(), \"foo\")", "gomock.NewController(GinkgoT())" — copy-paste ready commands and complete code covering every common case, including remediation commands ("spctl developer-mode enable-terminal"). | 5 / 5 |
Workflow Clarity | Quotes: numbered sections 1–6 in install→bootstrap→generate order, with a checkpoint ("ginkgo version confirms the install") and an error-recovery loop for the riskiest step ("re-run go install ... from the package to sync them"). Not 5 because verification is absent after bootstrap/generate (e.g., no step to run the generated suite to confirm the wiring); not 3 because an explicit checkpoint and remediation loop are present. | 4 / 5 |
Progressive Disclosure | Quotes: "For the mental model see `ginkgo:overview`", "**Authoring specs** ... → `ginkgo:writing-specs`", and a closing "Where to go next" section — clearly signaled, one-level-deep pointers plus an external docs link. Not 5 because there are no bundle files, so all detail (full suite-file walkthrough, the dot-import alternatives catalog in section 4) is inlined in a ~100-line body rather than split into references. | 4 / 5 |
Total | 17 / 20 Passed |