CtrlK
BlogDocsLog inGet started
Tessl Logo

filtering

Run a subset of a Ginkgo suite — Pending/PIt/XIt, runtime Skip, programmatic Focus/FIt (and ginkgo unfocus), Label with the --label-filter query language and label sets, suite-level labels, SemVerConstraint/--sem-ver-filter, --focus/--skip and --focus-file/--skip-file, the filtering precedence rules, and --fail-on-pending/--fail-on-empty. Use when you want to run, skip, focus, label, or version-gate specs, or debug why specs were or weren't selected.

76

Quality

94%

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

88%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, well-structured reference with executable examples throughout, a clear precedence ordering, and built-in mistake-catching verification flags. It is mostly lean and highly actionable, with only minor conciseness and progressive-disclosure gaps.

DimensionReasoningScore

Conciseness

Largely lean and assumes competence (e.g. terse precedence rules, compact tables), but a few sentences restate obvious behavior and the operator tables plus prose overlap slightly, leaving minor trimming opportunities. Not a 5 because some explanatory clauses (e.g. restating that comma equals OR both in text and table) are lightly redundant.

4 / 5

Actionability

Provides copy-paste-ready Go and bash examples for every mechanism (Pending, Skip, Focus, label-filter queries, label sets, semver, file filters) with exact flag syntax and concrete invocations covering the common cases.

5 / 5

Workflow Clarity

The 'Precedence' section gives an explicitly numbered, ordered sequence of how filters combine, and 'Catching filtering mistakes' supplies verification commands (--fail-on-pending, --fail-on-empty, --dry-run) that act as validation checkpoints for the filtering workflow.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and one-level-deep cross-skill pointers (ginkgo:decorators, ginkgo:ci) plus an external docs link, but there are no bundle reference files present and some detail that could live in a reference (full label-set operator semantics, CLI filter forms) is inlined. Good structure with minor organization gaps.

4 / 5

Total

18

/

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.

A dense, specific description that enumerates concrete filtering mechanisms and pairs them with an explicit 'Use when' trigger clause. It is comprehensive, uses third person, and carries minimal conflict risk.

DimensionReasoningScore

Specificity

Lists numerous concrete actions (Pending/PIt/XIt, runtime Skip, programmatic Focus/FIt, Label with --label-filter, SemVerConstraint/--sem-ver-filter, --focus/--skip, --focus-file/--skip-file, precedence rules, --fail-on-pending/--fail-on-empty) with comprehensive coverage of the filtering domain.

5 / 5

Completeness

Explicitly answers 'what' (the enumerated filtering mechanisms) and 'when' via a concrete 'Use when you want to run, skip, focus, label, or version-gate specs, or debug why specs were or weren't selected' trigger clause.

5 / 5

Trigger Term Quality

Includes the natural verbs users would say ('run, skip, focus, label, or version-gate specs', 'debug why specs were or weren't selected') alongside the specific CLI flags and decorator names, giving comprehensive coverage of natural and technical terms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (Ginkgo spec filtering) with highly domain-specific triggers and flag names, making conflict with other skills minimal.

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.

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.