CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ordering-and-flakes

Control spec ordering and manage flaky specs — Serial, Ordered containers with BeforeAll/AfterAll/ContinueOnFailure, OncePerOrdered, SpecPriority, plus FlakeAttempts/--flake-attempts, MustPassRepeatedly, --repeat, and --until-it-fails. Use when specs must run in a fixed order, you need once-per-group setup, you're combining Serial+Ordered, a spec is flaky, or you want to hunt order-dependence with --until-it-fails -p --randomize-all.

Quality

92%

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

96%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 exceptionally lean, expert-level reference: executable examples, exact commands, and high-value gotchas with explicit decision rules for every feature. The only structural note is that the body is self-contained at ~100 lines with no reference files, which is defensible but leaves minor room to split detail out.

DimensionReasoningScore

Conciseness

Every section carries non-obvious Ginkgo semantics or gotchas ("BeforeAll/AfterAll are legal only inside an Ordered container", "--repeat=N runs 1+N times", "not compatible with go test --count") with zero padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Copy-paste-ready Go snippets (Ordered container with BeforeAll/DeferCleanup/DeferOnFailure, OncePerOrdered BeforeEach) and exact CLI invocations ("ginkgo --until-it-fails -p --randomize-all", "--repeat=N", "--flake-attempts=3") cover the common cases.

5 / 5

Workflow Clarity

Decision guidance is unambiguous ("Prefer one It + By by default", "Default to none — debug the flake", "use Ordered only when needed"), and each tool's semantics, failure behavior, and anti-patterns are stated explicitly. No destructive or batch operations require validation loops.

5 / 5

Progressive Disclosure

Well-organized sections that delegate depth to sibling skills ("The full decorator signatures → ginkgo:decorators"), but the ~100-line body has no bundle references and inlines detail (e.g. the FlakeAttempts × Ordered rerun interaction) that could live in a reference file.

4 / 5

Total

19

/

20

Passed

Description

83%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 dense, high-quality description that lists every capability concretely and pairs it with an explicit, multi-trigger "Use when" clause covering ordering, setup, and flake scenarios. The only weakness is that the framework (Ginkgo) is implicit rather than named, leaving slight overlap risk with closely related skills.

DimensionReasoningScore

Specificity

Enumerates the full capability set concretely: "Serial, Ordered containers with BeforeAll/AfterAll/ContinueOnFailure, OncePerOrdered, SpecPriority, plus FlakeAttempts/--flake-attempts, MustPassRepeatedly, --repeat, and --until-it-fails" — comprehensive coverage with no gaps.

5 / 5

Completeness

Explicitly answers both: what ("Control spec ordering and manage flaky specs" with every decorator/flag listed) and when ("Use when specs must run in a fixed order, you need once-per-group setup, you're combining Serial+Ordered, a spec is flaky, or you want to hunt order-dependence").

5 / 5

Trigger Term Quality

Natural phrases a user would say are all present: "specs must run in a fixed order", "a spec is flaky", "hunt order-dependence", "once-per-group setup", plus the exact tool names (Serial, Ordered, --flake-attempts).

5 / 5

Distinctiveness Conflict Risk

Ginkgo-specific decorator and flag names (OncePerOrdered, --until-it-fails) form a clear niche, but Ginkgo itself is never named and triggers like "a spec is flaky" could overlap a debugging-failures sibling skill — minor overlap risk, not minimal.

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

onsi/ginkgo

Path

plugins/ginkgo/skills/ordering-and-flakes/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.