CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-specs

Author good Ginkgo specs — container nodes (Describe/Context/When), subject nodes (It/Specify), setup/cleanup nodes (BeforeEach, JustBeforeEach, AfterEach, DeferCleanup, BeforeSuite/AfterSuite), the "declare in container, initialize in BeforeEach" rule, separating creation from configuration, reusable test helpers with GinkgoHelper()/GinkgoHelperGo(), and By/GinkgoWriter output. Use when writing or reviewing specs or extracting a test helper. Covers the tree-construction-time pitfalls (no assertions/init/loop-capture in container bodies).

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is dense, actionable, and tightly scoped to Ginkgo-specific knowledge, with executable examples throughout. It is well structured, though as a reference-style skill it lacks an explicit multi-step validation workflow.

Suggestions

Consider adding a short ordered checklist for the most common end-to-end task (e.g., extract a repeated assertion into a GinkgoHelper-marked helper) to push workflow clarity toward a 5.

If the skill grows, move the GinkgoHelperGo/async helper detail into a referenced file to keep the overview leaner.

DimensionReasoningScore

Conciseness

The body is lean and focused on Ginkgo-specific semantics Claude would not reliably know (tree-construction-time behavior, node ordering, DeferCleanup LIFO, GinkgoHelper failure framing), with no padding about basic testing concepts.

5 / 5

Actionability

Each concept ships a complete, executable Go example (spec shape, wrong/right declare pattern, JustBeforeEach separation, DeferCleanup, By, GinkgoHelper, GinkgoHelperGo), copy-paste ready and covering common cases.

5 / 5

Workflow Clarity

Guidance is coherently sequenced (shape → declare rule → setup ordering → cleanup → output → helpers → next steps), but it is reference-style guidance rather than an explicit validate-fix-retry workflow; not a destructive/batch skill so no cap applies.

4 / 5

Progressive Disclosure

Well-organized with clear section headers, a 'Where to go next' navigation block, and one-level-deep cross-references signaled with arrows; no bundle files exist to split further, and the length does not demand external references.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, comprehensive, and clearly states both what the skill does and when to use it, with a distinct Ginkgo-focused trigger. It is one of the strongest possible descriptions for a domain skill.

DimensionReasoningScore

Specificity

Enumerates many concrete capabilities (container/subject/setup node types, the declare-in-container rule, GinkgoHelper/GinkgoHelperGo, By/GinkgoWriter, tree-construction pitfalls), matching the 'multiple specific concrete actions; comprehensive coverage' anchor.

5 / 5

Completeness

Explicitly answers both 'what' (authors Ginkgo specs with enumerated capabilities) and 'when' ('Use when writing or reviewing specs or extracting a test helper'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when writing or reviewing specs or extracting a test helper' clause supplies natural user phrases with synonyms (writing/reviewing/extracting) plus the Ginkgo domain vocabulary, matching comprehensive keyword coverage.

5 / 5

Distinctiveness Conflict Risk

Targets a clear Ginkgo-specific niche with distinct triggers (Ginkgo specs, named node types), giving minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
onsi/ginkgo
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.