CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

timeouts-and-async

Make Ginkgo specs interruptible and test asynchronous behavior — SpecContext/context.Context cancellable nodes, NodeTimeout/SpecTimeout/GracePeriod, the --timeout flag, Abort and SIGINT behavior, Gomega Eventually/Consistently (the func(g Gomega) form, .WithContext), and the defer GinkgoRecover() rule for goroutines. Use when a spec hangs or times out, polls for eventual consistency, tests channels/streams/processes, launches goroutines, or needs a deadline.

Quality

93%

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 tight, expert-level reference that packs genuinely non-obvious Ginkgo/Gomega pitfalls (deadline() behavior, leaked-goroutine pollution, g-vs-global Expect, GinkgoRecover) into lean, well-sectioned prose with concrete code for each scenario. The main headroom is in making examples fully self-contained and anchoring the cross-skill pointers to concrete, resolvable targets.

Suggestions

Make the code examples copy-paste runnable: replace the `case <-time.After(time.Hour): ...` ellipsis with a real statement and define or briefly introduce the example fixtures (book, publisher, gmail/jane) so snippets compile conceptually on first read.

Convert the `ginkgo:decorators` / `ginkgo:debugging-failures` / `ginkgo:ci` pointers into explicit file paths or links (or state the convention once, e.g. "ginkgo:X means sibling skill file X.md") so navigation doesn't depend on an undocumented naming convention.

For the async-assertion workflow, add a short ordered checklist (pass ctx positionally or via .WithContext → use func(g Gomega) for inner assertions → poll channels with Eventually instead of blocking receives) to give the multi-rule guidance a single explicit sequence.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it defers the failure mental model to `ginkgo:overview`, never explains what Ginkgo or contexts are, and delivers non-obvious rules ("ctx.Deadline() does NOT report the node's deadline", leaked-goroutine pollution) in single sentences. Every token earns its place, matching the lean anchor-5 example.

5 / 5

Actionability

Guidance is mostly executable — a real `select`/`ctx.Done()` snippet, `Eventually(ctx, c).WithTimeout(...)`, `ginkgo --timeout=DURATION`, and a complete goroutine pattern — but minor gaps remain: `case <-time.After(time.Hour): ...` uses an ellipsis placeholder, and examples reference undefined receivers (`book`, `publisher`, `gmail`, `jane`), so they're not fully copy-paste ready. Not level 3 because the code is real Go, not pseudocode, and covers the common cases.

4 / 5

Workflow Clarity

Sequences that exist are precise and unambiguous — the timeout cascade ("cancels the current node, runs DeferOnFailure callbacks, then AfterEach/AfterAll/DeferCleanup") and the SIGINT escalation ladder (2nd interrupt skips cleanup, 3rd bails) — and per-scenario rules like "Always make blocking code respond to ctx.Done()" are clear. It falls short of level 5 because the skill is a scenario reference rather than a checkpointed workflow, so there are no explicit validate/verify feedback loops (none are strictly required here since no destructive or batch operations are involved).

4 / 5

Progressive Disclosure

Good structure: scenario-organized sections, a summary decorator table, inline code kept short, and a "See also" section with one-level-deep pointers ("Decorator reference → ginkgo:decorators", "Progress reports → ginkgo:debugging-failures", "--timeout and friends → ginkgo:ci") that are clearly signaled. It does not reach level 5 because the `ginkgo:*` cross-references are a naming convention with no resolvable bundle files in this skill's directory (no references/, scripts/, or assets/ exist), so navigation depends on an external convention rather than verifiable paths.

4 / 5

Total

17

/

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: it pairs a comprehensive, concrete capability list with an explicit and natural "Use when..." trigger clause, all in third person with framework-specific terms that make confusion with other skills unlikely. No vague language, buzzwords, or padding are present.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities — "SpecContext/context.Context cancellable nodes, NodeTimeout/SpecTimeout/GracePeriod, the --timeout flag, Abort and SIGINT behavior, Gomega Eventually/Consistently (the func(g Gomega) form, .WithContext), and the defer GinkgoRecover() rule for goroutines" — covering the domain comprehensively with no material gaps, matching the top anchor rather than the 'minor gaps' level 4.

5 / 5

Completeness

Both questions are answered explicitly: a detailed third-person 'what' (interruptible specs, async testing with named APIs) followed by an explicit "Use when..." clause with five concrete trigger conditions, exactly matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

"Use when a spec hangs or times out, polls for eventual consistency, tests channels/streams/processes, launches goroutines, or needs a deadline" captures the natural phrasings a user would actually say, with synonyms spread across the what-clause too (async behavior, timeouts, polling).

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — Ginkgo/Gomega timeout and async testing — with named framework-specific constructs (SpecContext, GinkgoRecover, Eventually/Consistently) that no other plausible skill would trigger on, giving minimal conflict 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/timeouts-and-async/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.