Content
100%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.
Exemplary skill body: it assumes prior knowledge, packs every section with Ginkgo-specific rules and pitfalls backed by complete executable Go examples, and cleanly delegates adjacent topics (decorators, timeouts, tables, filtering) to sibling skills with a consistent reference convention. No padding, no basics re-explained, no misplaced content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence from the first line ("Assumes Ginkgo is wired into the suite (`ginkgo:setup`) and you know the two-phase model") and never explains what Ginkgo or BDD testing is. Every section delivers non-obvious, Ginkgo-specific rules ("Container bodies run once, at tree-construction time", "DeferCleanup... runs in LIFO order"), matching the level-5 anchor 'every token earns its place' rather than level 4, which expects trimmable over-explanation. | 5 / 5 |
Actionability | All examples are real, complete, executable Go — the spec skeleton, the WRONG construction-time example, the JustBeforeEach creation/config split, the DeferCleanup env-restore ("DeferCleanup(os.Setenv, \"MODE\", original)"), the GinkgoHelper and GinkgoHelperGo examples — covering the common cases copy-paste ready. This matches the level-5 anchor; level 4 would imply minor gaps in the examples. | 5 / 5 |
Workflow Clarity | This is a single-task guidance skill (write good Ginkgo specs), and the single action is unambiguous: the content states decisive rules ("Declare shared variables in the container body... Initialize them in BeforeEach", "prefer DeferCleanup", "Prefer it to JustAfterEach + if CurrentSpecReport().Failed()", "Prefer it over the older manual frame-counting"), with ordering made explicit in the setup/cleanup table ("outer→inner", "inner→outer"). Under the simple-skill guideline, unambiguous single-action guidance scores 5; there are no destructive/batch operations that would require validation checkpoints and cap the score. | 5 / 5 |
Progressive Disclosure | No bundle files exist, and none are needed: the body is one coherent, well-sectioned topic that delegates advanced material to sibling skills via clearly signaled one-level-deep references ("→ `ginkgo:decorators`", "→ `ginkgo:timeouts-and-async`", and a 'Where to go next' section). Navigation is easy via consistent headers, matching the level-5 anchor ('well-signaled one-level-deep references... easy navigation'); level 4 would require buried references or content misplaced relative to the split, which is not the case. | 5 / 5 |
Total | 20 / 20 Passed |