CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

overview

The Ginkgo mental model for writing Go tests — the one idea that explains everything (Ginkgo builds a spec tree at construction time, then runs it) and its consequences for how you write specs, plus spec independence and the node taxonomy. Use this first when you start working with Ginkgo in a project, or to decide how to approach a Ginkgo task. Routes to the other ginkgo:* skills.

Quality

86%

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

78%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 well-crafted orientation skill: lean, information-dense, built around one explanatory idea, with explicit concrete rules and an unambiguous routing table to sibling skills for depth. The main improvement levers are trimming the small amount of known background in the intro and making the core declare/initialize rule concrete with a minimal code snippet.

Suggestions

Trim or repurpose the opening sentence's BDD/Gomega framing — it restates what Claude already knows — so the body starts directly with the mental model and CLI preference.

Add a minimal 5-8 line code snippet contrasting wrong (initialize in Describe body) vs. right (declare in container, initialize in BeforeEach) to make the skill's central rule copy-paste concrete.

Either fold the two-sentence 'Parallelism Model' section into the spec-independence rationale or drop it in favor of its existing routing pointer to ginkgo:parallelism, removing the one stub section.

DimensionReasoningScore

Conciseness

The body is dense and nearly every line delivers a non-obvious Ginkgo-specific fact or routing pointer, assuming competence throughout. The minor trimmable instance is the opening framing "Ginkgo is an expressive BDD-style testing framework for Go, paired with the Gomega matcher library" — background Claude already knows — which places it at the 4 anchor rather than the 5 anchor's every-token-earns-its-place.

4 / 5

Actionability

Guidance is concrete and directive rather than vague: "Declare in the container, initialize in BeforeEach", "Put assertions in It or BeforeEach", "a goroutine that might fail needs defer GinkgoRecover()", "Strongly prefer ginkgo over go test", plus specific flags (--randomize-all, -p, --focus). It stays below the 5 anchor because there are no copy-paste code examples of the core rules, relying instead on prose directives with API names.

4 / 5

Workflow Clarity

The two-phase model is clearly sequenced (1. tree construction, 2. run), consequences are ordered logically, and the "Where to go next" section maps tasks to skills unambiguously. It does not reach the 5 anchor's explicit validation checkpoints/feedback loops, and the thin two-sentence "Parallelism Model" section is more a stub than a step — but no risky operations exist that would require validation, so no cap applies.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body is a lean ~50-line overview that defers all depth via clearly signaled, one-level-deep pointers ("→ ginkgo:writing-specs" etc.) collected in a dedicated routing section. This matches the 5 anchor — clear overview, well-signaled references, easy navigation — and the well-organized-sections exception for short skills without external files also applies.

5 / 5

Total

17

/

20

Passed

Description

87%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 strong description: it states a concrete, differentiated scope, includes an explicit 'Use when' trigger clause, and clearly positions itself as the entry point of a skill family. The only soft spot is keyword coverage that omits a few natural synonyms (Gomega, BDD, node names) that users might say.

DimensionReasoningScore

Specificity

The description names several concrete topics — "Ginkgo builds a spec tree at construction time, then runs it", "spec independence and the node taxonomy", and "Routes to the other ginkgo:* skills" — rather than vague filler. It falls short of the 5 anchor because the items are conceptual themes of an orientation skill rather than a comprehensive list of concrete actions, and above the 3 anchor since it goes well beyond 1-2 generic actions.

4 / 5

Completeness

Both halves are explicit: the "what" is stated concretely (mental model of tree construction then running, its consequences, spec independence, node taxonomy, routing) and the "when" uses a concrete trigger clause — "Use this first when you start working with Ginkgo in a project, or to decide how to approach a Ginkgo task." This matches the 5 anchor's explicit what-and-when with concrete trigger phrases; no cap applies since the Use-when clause is present.

5 / 5

Trigger Term Quality

Natural trigger terms are present and repeated: "Ginkgo", "writing Go tests", "Ginkgo in a project", "Ginkgo task", "specs" — exactly what a user would say. A few natural variations are missing (e.g., "Gomega", "BDD", "Describe/It/Context"), which keeps it below the 5 anchor's comprehensive synonym coverage but clearly above the 3 anchor.

4 / 5

Distinctiveness Conflict Risk

"Ginkgo" is a clear niche trigger repeated throughout, giving minimal conflict risk with non-Ginkgo skills, and the explicit positioning ("Use this first... Routes to the other ginkgo:* skills") resolves overlap with its own sibling skills. Fits the 5 anchor (clear niche, distinct triggers) rather than the 4 anchor's "minor overlap risk".

5 / 5

Total

18

/

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/overview/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.