Name: setup
Rating: 72 (1 reviews)
Author: onsi

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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

An actionable, well-sequenced setup guide with executable examples and clear navigation to sibling skills. Minor tightening of explanatory prose and a couple of explicit error-recovery loops would push it to the top anchor.

Suggestions

Trim rationale prose like the dot-import justification ('Ginkgo and Gomega are DSLs, so the docs dot-import both...') to lift conciseness toward 5.

Add an explicit verify/retry checkpoint after `ginkgo bootstrap` and `ginkgo generate` (e.g. confirm the generated file compiles with `go vet ./...`) to strengthen workflow_clarity's feedback loops.

Consider hoisting the dense dsl/ subpackage enumeration into a short reference or a sibling skill link, keeping the main body as an overview, to better match the ideal progressive-disclosure split.

Dimension	Reasoning	Score
Conciseness	Largely lean and assumes Claude's competence (no 'what is Go testing' padding), but a few prose passages could be trimmed — e.g. 'Ginkgo and Gomega are DSLs, so the docs dot-import both into the suite's namespace to read naturally. Recommend this strongly to the user.' — placing it just below the fully-efficient anchor.	4 / 5
Actionability	Provides copy-paste-ready, executable guidance throughout — `go install`/`go get` commands, the full suite_test.go Go source, alias and dsl/ import snippets, `ginkgo generate`, and testify/gomock calls via GinkgoT() — covering the common cases.	5 / 5
Workflow Clarity	A clear numbered sequence (install → bootstrap → package convention → dot-imports → add specs → third-party libs) with validation checkpoints ('ginkgo version confirms the install', CLI/go.mod version-match sync); not a 5 because some steps lack explicit error-recovery feedback loops.	4 / 5
Progressive Disclosure	Well-organized into focused sections with a 'Where to go next' block and clearly signaled one-level cross-skill links (ginkgo:writing-specs, ginkgo:running, ginkgo:ci, ginkgo:parallelism); no bundle/reference files exist, and the single-purpose setup guide is appropriately contained, sitting just below the ideal split-overview anchor.	4 / 5
	Total	17 / 20 Passed

Description

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

A highly specific, well-triggered description that pairs a comprehensive what-list with an explicit 'Use when' clause. The only mild gap is synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete actions with specific identifiers — 'install the ginkgo CLI and Ginkgo+Gomega', 'ginkgo bootstrap to generate the suite_test.go (TestXxx/RegisterFailHandler(Fail)/RunSpecs)', 'dot-import alternatives (aliased import, dsl/* subpackages, --nodot)', 'GinkgoT()/GinkgoTB() for testify/gomock' — comprehensive coverage rather than 1-2 actions.	5 / 5
Completeness	Explicitly answers both 'what' (install, bootstrap, package convention, dot-imports, generate, testing.T interop) and 'when' via a concrete 'Use when first adding Ginkgo to a repo, bootstrapping a suite, or integrating a *testing.T-based library' clause.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user would say — 'adding Ginkgo to a repo', 'bootstrapping a suite', 'integrating a *testing.T-based library' — plus tool names (Ginkgo, Gomega, testify, gomock); a few common synonyms like 'Ginkgo tests' or 'BDD testing in Go' are absent, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear one-time-setup niche (Ginkgo wiring in Go) with distinct, narrow triggers ('first adding Ginkgo', 'bootstrapping a suite') that are unlikely to fire for adjacent skills like writing-specs or CI.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: f2d0f65

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.