Conciseness

The body is lean and operational throughout — no 'what is Ginkgo' padding, terse sections like 'The three traps that bite agents' and 'Schema facts you need' deliver only non-obvious, empirically grounded detail. Every token earns its place; I could not identify a trimmable passage, so it fits the top anchor rather than the 'minor over-explanation' anchor below it.

Actionability

Fully executable end to end: the exact run command ("ginkgo -r -p --no-color --json-report=report.json --output-dir=.ginkgo-report"), five copy-paste-ready jq filters, exact JSON field names, and precise signal/flag guidance ("SIGUSR1 on Linux", "--poll-progress-after=120s"). Covers the common failure cases, matching the copy-paste-ready anchor rather than the minor-gaps anchor.

Workflow Clarity

The core workflow is an explicit numbered sequence (read terminal verdict → jq extraction only if failures → clean up) extended by a reproduce-focus-rerun narrowing loop. Checkpoints are mostly implicit (e.g., no check that the report file was written, no explicit re-validate step), which fits the 4 anchor 'clear sequence with most checkpoints; minor validation gaps' — not 5 because no explicit validation/feedback step exists, and not 3 because the sequence, conditionals, and cleanup are all explicit and the operation is non-destructive.

Progressive Disclosure

No bundle files exist, and the single ~95-line body is organized into clear, well-labeled sections with clearly signaled one-level-deep cross-links ("→ ginkgo:filtering", "→ ginkgo:timeouts-and-async") and a docs URL. This is good structure with a minor gap — the jq-filter catalog and schema facts are reference-shaped content kept inline — so it matches the 4 anchor rather than 5 (content not split) or 3 (structure is clear, nothing buried).

Specificity

The description lists multiple concrete actions — "always run with --json-report into a predictable temp/gitignored location", "read the terminal verdict line", "use jq to extract structured failure details (name, message, file:line, panic value, captured logs)" — with named fields, comprehensively covering the diagnostic procedure.

Completeness

It explicitly answers both what (the full JSON-first diagnostic procedure with named output fields) and when ("Use when a suite failed and you need to know why"), with a concrete trigger phrase — the clear match for the top anchor, not the weaker when-clause of the 4 anchor.

Trigger Term Quality

Good natural coverage — "failing Ginkgo suite", "suite failed", "panicked", "hangs", "--seed" — phrasings a Ginkgo user would actually say, but a few common variants ("test failure", "flaky", "Ginkgo test") are absent, matching the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive-synonyms anchor.

Distinctiveness Conflict Risk

Occupies a clear Ginkgo-specific niche (Ginkgo suites, --json-report, panicked specs, --seed reproduction) with distinct triggers and minimal risk of firing for unrelated skills; no closely related skill would collide on these terms.