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

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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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-organized reference dense with executable code and sound diagnostic heuristics. The main lever is trimming the explanatory narrative to lift conciseness, since the technical content is already strong.

Suggestions

Tighten narrative scaffolding (e.g. 'This is the one thing to internalize', 'Going parallel is cheap, but not free', 'That flatness is the tell') into terse directives so conciseness approaches a 5.

Add one explicit validation/retry checkpoint where a workflow is implied — e.g. after sharding by GinkgoParallelProcess(), confirm the previously-flaky spec now passes under -p — to lift workflow clarity.

If the cost-analysis or integration-pattern sections grow further, consider splitting them into a reference file so progressive disclosure has true one-level-deep file navigation.

Dimension	Reasoning	Score
Conciseness	Dense and information-rich with executable commands and code, but retains narrative scaffolding Claude does not strictly need ('This is the one thing to internalize', 'That flatness is the tell') that could be trimmed.	4 / 5
Actionability	Fully executable bash commands (ginkgo -p, GORACE=atexit_sleep_ms=0 ginkgo -r -p --race) and Go snippets (SynchronizedBeforeSuite, gexec.Build, index-based sharding) are copy-paste ready and cover the common cases.	5 / 5
Workflow Clarity	Clear topical progression with diagnostic checkpoints (precompile to isolate compilation cost, the flatness tell, shard-the-singleton fix for -p flakes); not a destructive/batch skill so the validation cap does not apply, but no explicit validate-to-retry loop keeps it below 5.	4 / 5
Progressive Disclosure	Well-sectioned single file with clearly signaled one-level-deep cross-skill links (ginkgo:running, ginkgo:ci, etc.) and no nested references; good structure and easy navigation, but no bundle file splitting to justify a 5.	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 clearly states both capability and use-conditions for a narrow domain. Trigger-term quality is strong but stops just short of comprehensive synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — ginkgo -p/--procs, SynchronizedBeforeSuite vs BeforeSuite, GinkgoParallelProcess() sharding, gexec one-time build, GinkgoWriter piping, and the N-process cost model — with comprehensive coverage and no real gaps.	5 / 5
Completeness	Explicitly answers both what (the detailed action list) and when ('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') with concrete triggers.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'parallelizing a suite', 'speeding up integration tests', 'parallel run is slow', and 'parallel-only flakes/races' give good coverage, though a few natural variants are missing and the domain has no file extensions to round it out to a 5.	4 / 5
Distinctiveness Conflict Risk	Ginkgo parallel-suite execution is a tight, specific niche with distinct triggers and minimal overlap risk with other skills.	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/parallelism/SKILL.md
Commit: 9f94149

Reviewed: 22 hours 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.