CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup

Wire Ginkgo into a Go package — install the ginkgo CLI and Ginkgo+Gomega, ginkgo bootstrap to generate the suite_test.go (TestXxx/RegisterFailHandler(Fail)/RunSpecs), the package xxx_test convention, dot-import alternatives (aliased import, dsl/* subpackages, --nodot), ginkgo generate, and *testing.T interop via GinkgoT()/GinkgoTB() for testify/gomock. Use when first adding Ginkgo to a repo, bootstrapping a suite, or integrating a *testing.T-based library.

Quality

93%

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

82%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.

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.

DimensionReasoningScore

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

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 maximally concrete: every clause names a specific action, tool, or file, and the explicit 'Use when...' clause provides three natural trigger scenarios. It cleanly scopes the skill to one-time setup, distinguishing it from sibling authoring/running skills, with no fluff or over-claims.

DimensionReasoningScore

Specificity

Quotes: "install the ginkgo CLI and Ginkgo+Gomega", "ginkgo bootstrap to generate the suite_test.go", "ginkgo generate", "*testing.T interop via GinkgoT()/GinkgoTB() for testify/gomock" — six specific concrete actions with comprehensive coverage of the setup workflow and no vague language. Not 4 because there are no minor gaps in coverage; every setup sub-task is named.

5 / 5

Completeness

Explicitly answers both: what ("Wire Ginkgo into a Go package — install... ginkgo bootstrap... ginkgo generate... *testing.T interop") and when ("Use when first adding Ginkgo to a repo, bootstrapping a suite, or integrating a *testing.T-based library") with concrete trigger phrases. The 'Use when' clause is present, so the completeness cap does not apply.

5 / 5

Trigger Term Quality

Quotes: "Use when first adding Ginkgo to a repo, bootstrapping a suite, or integrating a *testing.T-based library" plus named identifiers (Ginkgo, Gomega, suite_test.go, testify, gomock, *testing.T). These are exactly the phrases a user would naturally say when they need this skill, including synonyms (adding/bootstrapping/integrating) and file-level identifiers (suite_test.go, xxx_test).

5 / 5

Distinctiveness Conflict Risk

Clear niche: one-time Ginkgo setup ("Wire Ginkgo into a Go package", "first adding Ginkgo to a repo") with triggers distinct from authoring/running concerns, which are explicitly deferred to sibling skills. Minimal overlap risk — a user mentioning bootstrapping a Ginkgo suite or Ginkgo/testify integration unambiguously wants this skill.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

onsi/ginkgo

Path

plugins/ginkgo/skills/setup/SKILL.md

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.