CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

parallelism

Run Ginkgo suites in parallel — ginkgo -p / --procs, the separate-process (not goroutine) model, SynchronizedBeforeSuite/SynchronizedAfterSuite vs BeforeSuite, GinkgoParallelProcess() for sharding ports/tmpdirs/databases, building a binary once via gexec, piping child-process output to GinkgoWriter, and what N processes actually cost (compilation vs teardown, and the fixed ~1s --race adds per suite — GORACE=atexit_sleep_ms=0). Use when parallelizing a suite, speeding up integration tests, auditing why a parallel run is slow, fixing parallel-only flakes/races, sharding external resources, or choosing between BeforeSuite and SynchronizedBeforeSuite.

Quality

97%

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

93%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 dense, expert-level reference that trusts the reader: executable commands and complete Go examples for every pattern, plus genuinely non-obvious diagnostics (the flat per-process --race teardown cost) unavailable from general knowledge. The only gap is that guidance is organized topically rather than as a sequenced workflow with explicit checkpoints.

Suggestions

workflow_clarity: Add a short ordered diagnostic checklist for the auditing use case (e.g., 1. precompile with `ginkgo build -r`, 2. rerun and compare suite gaps, 3. set GORACE=atexit_sleep_ms=0 only if races are spec-found, 4. record why the sleep was disabled) so the audit path reads as a sequence with explicit checkpoints.

workflow_clarity: Include one explicit validation step after adopting SynchronizedBeforeSuite — e.g., assert on process #1 that the shared resource is reachable from a second process before fan-out — to give the setup pattern a verify-early checkpoint.

DimensionReasoningScore

Conciseness

Assumes Claude's competence throughout — it never explains what Ginkgo or a test framework is — and every section delivers non-obvious curated knowledge (atexit_sleep_ms semantics, the output-interceptor hang, "a build cost can't be flat across package size, and a per-process cost must be"). Not 4: even the discursive sentences carry diagnostic value rather than padding, so there is nothing meaningful to trim.

5 / 5

Actionability

Copy-paste ready throughout: shell commands ("ginkgo -p", "GORACE=atexit_sleep_ms=0 ginkgo -r -p --race", "ginkgo build -r"), a complete executable SynchronizedBeforeSuite example with DeferCleanup, the gexec.Build once-and-share-path pattern, and three concrete sharding snippets. Not 4: the examples are executable and cover the common cases (flags, setup, sharding, child-process output).

5 / 5

Workflow Clarity

Decision points are explicit — a BeforeSuite vs SynchronizedBeforeSuite table, a DB strategy list by cost, and symptom→fix guidance ("pass in series but fail under -p" → shard the singleton) with a concrete audit verification method ("precompile with ginkgo build -r so compilation is excluded by construction"). Not 5: the organization is topical rather than a sequenced workflow, and there are no explicit validate-then-proceed checkpoints; not 3: error-recovery guidance and decision criteria are explicit, not implicit.

4 / 5

Progressive Disclosure

Well-organized single-file skill (~110 lines) with no content that clearly belongs in a separate file; cross-skill links (ginkgo:overview, ginkgo:ci, ginkgo:decorators, ginkgo:timeouts-and-async) are clearly signaled inline and collected in a Related section, one level deep. No bundle files exist, so nothing is buried or nested.

5 / 5

Total

19

/

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.

An exemplary description: third-person, densely specific about capabilities (flags, APIs, env vars), with an explicit Use-when clause covering the full range of natural user intents from setup to debugging. Distinct within the Ginkgo skill family with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple named concrete actions and APIs — "ginkgo -p / --procs", "SynchronizedBeforeSuite/SynchronizedAfterSuite vs BeforeSuite", "GinkgoParallelProcess() for sharding ports/tmpdirs/databases", "building a binary once via gexec", "piping child-process output to GinkgoWriter" — with comprehensive coverage of the parallelization niche. Not 4: coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both: a dense "what" (flags, APIs, cost model, GORACE=atexit_sleep_ms=0) and an explicit "Use when..." clause with six concrete trigger phrases. Not 4: the "when" is fully explicit, not merely present.

5 / 5

Trigger Term Quality

The "Use when" clause supplies the natural phrases users would actually say: "parallelizing a suite", "speeding up integration tests", "auditing why a parallel run is slow", "fixing parallel-only flakes/races", "sharding external resources". Not 4: no meaningful natural term for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche — Ginkgo suite parallelization — with Ginkgo-anchored triggers (SynchronizedBeforeSuite, ginkgo -p, GinkgoParallelProcess) that no generic Go-testing or CI skill would claim. Not 4: minimal, not minor, overlap risk.

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