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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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, dense reference: executable commands throughout, zero padding, correct precedence rules, and a dedicated 'Catching filtering mistakes' section that supplies the validation feedback loop. The only structural improvement would be splitting the label query/set-operator and semver reference tables into a bundle file to slim the main SKILL.md.

Suggestions

Move the label-filter operator table, label-set operation table, and SemVer details into a references/ file, keeping a one-line pointer plus a couple of common examples in the body.

State the --sem-ver-filter version assumptions (e.g., where the version values come from at runtime) explicitly to preempt the most likely misuse.

Dimension	Reasoning	Score
Conciseness	The body is lean and telegraphic — dense tables, short code blocks, bolded rules — and assumes Claude's competence (e.g., 'Marks a spec/container as under development. Nothing can override `Pending`'). No section explains concepts Claude already knows; every token carries information, matching the top anchor.	5 / 5
Actionability	Guidance is fully executable and copy-paste ready: 'ginkgo --label-filter="network && !slow"', 'ginkgo unfocus', 'ginkgo --fail-on-empty --label-filter mytypo ./...', exact flag forms like 'FILE_REGEX:LINE1-LINE2 (half-open)', and the operator tables for label queries and set operations.	5 / 5
Workflow Clarity	As a single-purpose reference the action is unambiguous, and it includes explicit validation checkpoints: 'ginkgo --dry-run -v --label-filter=Q shows what a filter selects without running', '--fail-on-empty' catches a typo'd filter, and focused suites exit non-zero so CI catches committed focus — a real feedback loop for filtering mistakes.	5 / 5
Progressive Disclosure	Sections are well-organized with clear headers and one-level, clearly signaled references to sibling skills ('Decorator specifics live in `ginkgo:decorators`; label-driven CI in `ginkgo:ci`') and upstream docs. However no bundle files exist and everything — full label-operator/set-op tables, semver details — is inline in ~118 lines; content arguably could be split, so it fits the 'good structure with minor organization gaps' anchor rather than 'appropriately split'.	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: it comprehensively and concretely lists the skill's capabilities, includes an explicit and well-phrased trigger clause, and is tightly scoped to Ginkgo spec filtering. Its only weakness is jargon-heavy phrasing that leaves a few natural synonyms uncovered.

Suggestions

Add a few natural user synonyms (e.g., 'exclude', 'tag', 'filter', 'pending specs') alongside the technical terms to improve trigger coverage.

Trim the long flag enumeration slightly in favor of plain-language capability verbs, keeping the detailed flags in the body.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete mechanisms — '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' — comprehensive coverage with no real gaps, matching the top anchor rather than the 'minor gaps' level below.	5 / 5
Completeness	Clearly answers 'what' (run a subset of a Ginkgo suite via the listed mechanisms) and has an explicit, concrete when-clause: 'Use when you want to run, skip, focus, label, or version-gate specs, or debug why specs were or weren't selected.'	5 / 5
Trigger Term Quality	'run, skip, focus, label, or version-gate specs' and 'debug why specs were or weren't selected' are natural phrases users would say, but the description leans heavily on technical jargon (PIt/XIt, SemVerConstraint, --focus-file) and omits common synonyms like 'exclude', 'tag', 'filter tests', or 'pending tests'.	4 / 5
Distinctiveness Conflict Risk	'Ginkgo suite' pins a clear, narrow niche (spec filtering in one specific framework), making it highly distinguishable from other testing or task-runner skills with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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/filtering/SKILL.md
Commit: 510c8d5

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.