CtrlK
BlogDocsLog inGet started
Tessl Logo

running

Run Ginkgo suites with the ginkgo CLI — run, -r, -p, --dry-run, watch, build (precompiled .test binaries), generate, outline, unfocus, labels, version; spec randomization (--randomize-all/--randomize-suites/--seed); running multiple suites (--keep-going/--skip-package/--compilers); previewing (--dry-run, PreviewSpecs); and parameterizing a suite via env vars or init()-registered flags after -- plus GinkgoConfiguration() overrides. Use when running suites locally, precompiling, watching for changes, or parameterizing a run from the command line. For a CI configuration see ginkgo:ci.

74

Quality

91%

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

86%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 dense, highly actionable reference that assumes Claude's competence and consistently provides executable commands and code. Structure and cross-link navigation are strong; it loses only minor points for a few trimmable asides and the absence of explicit validation checkpoints.

DimensionReasoningScore

Conciseness

Lean and largely efficient — every section delivers executable flag/command detail — but a few explanatory asides (e.g. 'only the CLI does parallelism and profile aggregation', 'a niche orchestration escape hatch') could be trimmed.

4 / 5

Actionability

Fully executable throughout: concrete `ginkgo` invocations, a complete PreviewSpecs Go example, and copy-paste-ready env-var and init()-flag patterns covering the common cases.

5 / 5

Workflow Clarity

Sections are clearly sequenced by task (running, randomizing, multi-suite, previewing, configuring) with explicit gotchas, but there is no validation/recovery checkpoint for the rebuild-via-precompiled-binary or config-mutation flows.

4 / 5

Progressive Disclosure

Well-organized into topical sections with consistent one-level-deep cross-links to sibling ginkgo skills (→ ginkgo:ci, :parallelism, :filtering, etc.) and an external docs URL; no bundle files exist to verify further.

4 / 5

Total

17

/

20

Passed

Description

96%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 comprehensively names the running capabilities and gives explicit trigger guidance with a clear use-when clause. Slightly jargon-dense in its trigger phrasing, but highly distinct from sibling ginkgo skills.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'run, -r, -p, --dry-run, watch, build', 'spec randomization', 'PreviewSpecs', 'parameterizing a suite via env vars or init()-registered flags' — comprehensive coverage of the running surface.

5 / 5

Completeness

Explicitly answers both what (the full list of running capabilities) and when ('Use when running suites locally, precompiling, watching for changes, or parameterizing a run from the command line').

5 / 5

Trigger Term Quality

Includes natural terms like 'running suites locally', 'precompiling', 'watching for changes', 'parameterizing a run from the command line', but is somewhat jargon-heavy and could add a few plainer synonyms.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to the Ginkgo CLI running surface and explicitly points elsewhere ('For a CI configuration see ginkgo:ci'), minimizing overlap with sibling ginkgo 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.