CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

87%

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

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.

A focused, well-structured reference with executable code and commands and strong decision guidance. It leans efficient and uses cross-skill pointers to avoid duplication, with only minor verbosity and no bundled reference files to fully exercise progressive disclosure.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no beginner explanations of what a spec is), with a few trimmable asides such as 'Under the hood Ginkgo runs serial specs last, on process #1' that keep it just short of fully efficient.

4 / 5

Actionability

Fully executable: copy-paste-ready Go decorator blocks and concrete CLI commands ('ginkgo --until-it-fails -p --randomize-all', 'ginkgo --flake-attempts=3') covering the common cases plus specific rerun semantics.

5 / 5

Workflow Clarity

Sections are clearly sequenced (Serial → Ordered → OncePerOrdered → gotchas → SpecPriority → flake expose/tolerate) with decision guidance ('Prefer one It + By by default — Reach for Ordered when...'), though it lacks explicit validate-fix-retry loops; this is a reference skill rather than a destructive batch workflow so the cap does not apply.

4 / 5

Progressive Disclosure

Well-organized into clear sections with cross-references to sibling skills (e.g. '→ ginkgo:decorators') deferring details rather than inlining them, but no separate reference files exist so it cannot fully demonstrate one-level-deep file splitting.

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 strong, specific description that clearly states capabilities and provides explicit 'Use when...' triggers across multiple scenarios. Slightly dense with decorator names, but that density reflects the skill's genuine scope.

DimensionReasoningScore

Specificity

Names the domain and enumerates many concrete actions/decorators — 'Serial, Ordered containers with BeforeAll/AfterAll/ContinueOnFailure, OncePerOrdered, SpecPriority' and 'FlakeAttempts/--flake-attempts, MustPassRepeatedly, --repeat, and --until-it-fails' — giving comprehensive coverage rather than minor gaps.

5 / 5

Completeness

Explicitly answers both 'what' (control ordering and manage flaky specs with named decorators) and 'when' via a concrete 'Use when...' clause listing multiple trigger scenarios.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say ('fixed order', 'once-per-group setup', 'a spec is flaky', 'hunt order-dependence') plus the CLI flags, but a few common synonyms/phrasings are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear narrow niche (Ginkgo ordering/flakes) with distinct, domain-specific triggers and 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.