CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reporting

Generate, consume, and enrich Ginkgo reports — console verbosity (-v/-vv/--trace/--no-color/--succinct), machine-readable reports (--json-report/--junit-report with --output-dir/--keep-separate-reports), programmatic reporting nodes (ReportAfterEach, ReportAfterSuite, CurrentSpecReport), AddReportEntry with ReportEntryVisibility, and profiling (--cover/--race/--cpuprofile/--memprofile). Use when you need a report file, custom suite-level reporting, attaching data to a spec, controlling console output, or profiling a suite.

Quality

97%

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

100%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.

The body is an exemplary reference skill: dense and token-efficient, fully executable commands and code, explicit decision guidance for the tricky cases (parallel report nodes, focused specs breaking profiles), and clean delegation of adjacent topics to sibling skills. Nothing scored below the top anchor.

DimensionReasoningScore

Conciseness

The body is lean and dense — flag tables, bolded gotchas, and Go snippets with no padding or explanations of concepts Claude already knows. Every non-obvious note earns its tokens ('Every machine-readable report embeds the full -vv timeline regardless of console verbosity', 'Focused specs break profiling'), matching the lean/efficient anchor.

5 / 5

Actionability

Guidance is fully executable: copy-paste commands ('ginkgo -r --json-report=report.json --output-dir=./.reports', the profiling invocation) and complete Go examples for CurrentSpecReport, ReportAfterSuite, and AddReportEntry cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Each task is unambiguous with explicit decision guidance ('never write a shared file from [ReportAfterEach] in parallel', 'ReportAfterSuite... is the safe place for custom suite-level report files', 'Subset with filters, not Focus'). No destructive or batch operations are involved, so no validation cap applies; the per-task guidance is clear enough to score at the top anchor for this reference-style skill.

5 / 5

Progressive Disclosure

The skill is self-contained (no bundle files) with well-organized sections and clearly signaled, one-level-deep delegation to sibling skills ('→ ginkgo:debugging-failures', '→ ginkgo:ci', '→ ginkgo:decorators'), keeping topics owned elsewhere out of this file. Navigation is easy, matching the top anchor.

5 / 5

Total

20

/

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: it enumerates concrete capabilities with specific flags and API names, uses third-person imperative voice, and closes with an explicit 'Use when...' clause covering concrete trigger scenarios. The only gap is a few plain-word synonyms (e.g., 'coverage', 'test results') that users might naturally say.

Suggestions

Include the natural word 'coverage' (e.g., 'test coverage') alongside the --cover flag so users asking about coverage in plain language trigger this skill.

Consider adding commonly-said phrases like 'test results' or 'CI report output' to the Use-when clause to round out trigger term coverage.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions with specific flags and APIs — 'console verbosity (-v/-vv/--trace/--no-color/--succinct)', 'machine-readable reports (--json-report/--junit-report with --output-dir/--keep-separate-reports)', 'programmatic reporting nodes (ReportAfterEach, ReportAfterSuite, CurrentSpecReport)', 'AddReportEntry with ReportEntryVisibility', and 'profiling (--cover/--race/--cpuprofile/--memprofile)' — which matches the comprehensive-coverage anchor, not the minor-gaps anchor at 4.

5 / 5

Completeness

It clearly answers 'what' (generate, consume, and enrich Ginkgo reports, with each capability enumerated) and explicitly answers 'when' with concrete trigger phrases: 'Use when you need a report file, custom suite-level reporting, attaching data to a spec, controlling console output, or profiling a suite.' This matches the top anchor exactly; the level-4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Natural phrases like 'report file', 'custom suite-level reporting', 'attaching data to a spec', 'controlling console output', and 'profiling a suite' appear alongside flag names users would quote, but a few natural synonyms are missing — e.g., the word 'coverage' itself (only the --cover flag appears) and terms like 'test results' or 'CI output'. This fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

'Ginkgo reports' names a clear niche with distinct triggers (report files, suite-level reporting, spec attachments, console output control, profiling), giving minimal conflict risk with other skills — matching the clear-niche anchor rather than the minor-overlap anchor at 4.

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