CtrlK
BlogDocsLog inGet started
Tessl Logo

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, and piping child-process output to GinkgoWriter. Use when parallelizing a suite, speeding up integration tests, fixing parallel-only flakes/races, sharding external resources, or choosing between BeforeSuite and SynchronizedBeforeSuite.

69

Quality

84%

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

76%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-structured reference with executable code and clean cross-skill navigation. It is organized as a patterns guide rather than a sequenced workflow with explicit validation checkpoints, which caps workflow clarity at the midpoint.

Suggestions

Trim framing prose ('This is the one thing to internalize', the opening hook) to push conciseness toward fully lean.

Add a short numbered diagnostic sequence for parallel-only flakes (run -p → identify colliding singleton → shard by GinkgoParallelProcess → re-run) with an explicit verify step to raise workflow clarity.

Consider splitting the integration-patterns section into a separate reference file if the skill grows, to keep the overview lean.

DimensionReasoningScore

Conciseness

Dense and free of basic-concept padding, but framing lines like 'This is the one thing to internalize' and the opening hook ('earns its keep') could be trimmed without losing meaning.

4 / 5

Actionability

Provides executable bash flags (ginkgo -p, --procs=4, watch -p) and complete, copy-paste Go examples (SynchronizedBeforeSuite, gexec.Build, GinkgoParallelProcess sharding) covering the common cases.

5 / 5

Workflow Clarity

Organized as topical patterns rather than a sequenced workflow; the parallel-only-flake diagnostic is present but validation checkpoints are only implicit, fitting the midpoint anchor.

3 / 5

Progressive Disclosure

A well-sectioned single file with clearly signaled one-level cross-skill references (→ ginkgo:running) and external doc links; no nested or buried references.

4 / 5

Total

16

/

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 strong, specific description that clearly enumerates concrete capabilities and pairs them with an explicit 'Use when' trigger clause covering natural user phrasing. Its only weakness is the heavy sprinkling of API names that slightly dilute the natural trigger terms.

DimensionReasoningScore

Specificity

Lists six concrete capabilities — 'ginkgo -p / --procs', 'SynchronizedBeforeSuite/SynchronizedAfterSuite vs BeforeSuite', 'GinkgoParallelProcess() for sharding ports/tmpdirs/databases', 'building a binary once via gexec', and 'piping child-process output to GinkgoWriter' — comprehensive and specific rather than vague.

5 / 5

Completeness

Explicitly states what it does (the capability list) and when to use it via the 'Use when parallelizing a suite, speeding up integration tests, fixing parallel-only flakes/races...' clause, matching the top anchor.

5 / 5

Trigger Term Quality

'parallelizing a suite', 'speeding up integration tests', 'fixing parallel-only flakes/races', and 'sharding external resources' are natural user phrases, but the heavy API names mixed in keep it just shy of the fully comprehensive top anchor.

4 / 5

Distinctiveness Conflict Risk

A narrow Ginkgo-parallelism niche with distinctive triggers; minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
onsi/ginkgo
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.