CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

debugging-failures

Diagnose a failing Ginkgo suite as an agent — always run with --json-report into a predictable temp/gitignored location, read the terminal verdict line, then use jq to extract structured failure details (name, message, file:line, panic value, captured logs). Covers the panicked-vs-failed trap, panic locations pointing into the Go runtime, parallel output interleaving, reproducing with --seed, and progress reports for hangs. Use when a suite failed and you need to know why. Also invokable as /ginkgo:debugging-failures.

Quality

95%

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 excellent single-file skill: lean, densely actionable, and sequenced as a clear diagnostic workflow with feedback loops. The only structural gap is that the ~100-line body keeps reference-grade material (the jq filters and schema facts) inlined rather than split into a reference file.

Suggestions

Move the jq filter library and/or the schema-facts list into a references/ file (e.g. references/filters.md), keeping only the workhorse failure-extraction filter inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — it never explains what Ginkgo, jq, or Go are — and every line delivers non-obvious knowledge (e.g. the ~9x token cost of the raw JSON, that --json-report does not suppress console output).

5 / 5

Actionability

Guidance is fully executable: a copy-paste ginkgo invocation, five tested jq filters targeting the real schema, concrete signal names (SIGUSR1/SIGINFO), and specific flag combinations covering the common diagnostic cases.

5 / 5

Workflow Clarity

The workflow is explicitly numbered (run once, read the terminal verdict, jq-query if failures, clean up) with a conditional checkpoint, and the "Reproduce, then narrow" section plus the three-traps section form a genuine feedback loop for error recovery. The destructive/batch cap does not apply since diagnosis is read-only.

5 / 5

Progressive Disclosure

Sections are well-organized and external pointers (ginkgo:writing-specs, ginkgo:reporting, docs URL) are one level deep and clearly signaled, but at ~100 lines the jq filter library and schema-facts block are reference-grade material inlined in the main file, with no bundle files used to split them out.

4 / 5

Total

19

/

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 description: concrete action pipeline, explicit use-when trigger, and a clearly bounded Ginkgo-specific niche. The only weakness is that a few natural trigger synonyms (e.g. "flaky", "test failure") are absent.

Suggestions

Add one or two common user phrasings such as "flaky" or "test failure" to the trigger coverage so it matches the ways users naturally describe a failing suite.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — run with --json-report to a predictable location, read the terminal verdict line, jq-extract name/message/file:line/panic value/captured logs, reproduce with --seed, use progress reports for hangs — giving comprehensive coverage with no gaps.

5 / 5

Completeness

It explicitly answers both what (the full JSON + jq diagnostic workflow and the traps it covers) and when ("Use when a suite failed and you need to know why") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural phrases like "failing Ginkgo suite", "suite failed", "panicked", and "hangs" are present, but common user variations such as "flaky", "test failure", or "CI" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and tool-specific (Ginkgo suite diagnosis with JSON reports), with triggers anchored on Ginkgo failure terminology, so overlap with generic testing or debugging skills is minimal.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

onsi/ginkgo

Path

plugins/ginkgo/skills/debugging-failures/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.