CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quality-gates

Use when designing, wiring, debugging, or being blocked by quality-gate infrastructure — git hooks, lint matrices, exception files, complexity gates, Stop hooks. Defines the three-tier latency topology, the vacuous-green problem (gates must prove they FIRED), exception-file hygiene, and gate failure UX. verification-ratchet defines WHAT the checks are; this skill defines how the machinery that runs them stays honest.

Quality

81%

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

65%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, disciplined doctrine document: every token carries field-tested rules with concrete mechanisms and named tools, and it trusts the reader's competence. Its weaknesses are structural rather than substantive — it is a principles catalog with no sequenced workflow, and everything lives inline in one file with no progressive disclosure to reference material.

Suggestions

Add a short ordered workflow section (e.g., 1. audit existing gates for vacuous green → 2. place checks per the three-tier topology → 3. self-test each gate by injecting a regression → 4. run `just verify`) so a session repairing a gate system has a sequence with explicit checkpoints.

Split the incident catalog (the three vacuous-green field incidents and the core-innovation tripwire story) into a references/ file, keeping SKILL.md as the rules-plus-signals overview with a clearly linked one-level-deep reference.

Include one portable, copy-paste example of a hook header declaring BLOCKING vs ADVISORY checks and a gate self-test snippet, so the directives generalize beyond the originating frankensqlite/just workspace.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows; every section carries project-specific doctrine ("Probe for a dependency the way the dependency actually presents", "Stale exceptions fail the lint"). Minor tightening opportunities exist — the "Field origin" preamble and repeated restatements of the vacuous-green rule across the intro and bullets — but there is no padding or filler, so it sits above the '3' anchor's "some unnecessary explanation".

4 / 5

Actionability

Concrete, executable directives appear throughout: "just verify: fmt-check + lint + arch-lint + full tests + generated-docs build", "configured fail_on_skipped", "parse build metadata (cargo metadata)", "site-local #[allow(lint, reason = \"...\")]", "a verify script self-tests by injecting a known regression". It stops short of a 5 because several anchors are project-specific (frankensqlite, beads, `verify_<bead>.sh`) with no portable hook or script example to copy.

4 / 5

Workflow Clarity

The content is organized as parallel principles, not a sequenced process — there is no ordered workflow for designing or repairing a gate system (the closest thing is the three-tier commit/push/opt-in placement, which is a topology, not a sequence). Validation doctrine is pervasive, so this is not a '2', but a reader cannot follow numbered steps with checkpoints, capping it at 3.

3 / 5

Progressive Disclosure

The skill is a single 160-line file with no references/, scripts/, or assets/ directories and no pointers to external material; well-organized section headers keep it coherent, but content that would naturally split out (the incident catalog, the exception-file regime, hook examples) is all inlined in SKILL.md. That matches 'some structure ... content that should be separate is inline' rather than the well-split '4'.

3 / 5

Total

14

/

20

Passed

Description

87%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: explicit and specific trigger guidance, a concrete inventory of covered topics, and an explicit boundary statement against a related skill. The only weakness is that the capability side is phrased as concepts it "Defines" rather than actions it performs, which slightly limits specificity.

DimensionReasoningScore

Specificity

The description enumerates several concrete, domain-specific items — "git hooks, lint matrices, exception files, complexity gates, Stop hooks" and "three-tier latency topology, the vacuous-green problem ... gate failure UX" — rather than vague language. It falls short of a 5 because the only action verb is "Defines"; it lists concepts covered rather than comprehensively stating what the skill does for the user.

4 / 5

Completeness

Both halves are explicit: "Use when designing, wiring, debugging, or being blocked by quality-gate infrastructure" answers 'when' with concrete trigger phrases, and "Defines the three-tier latency topology, the vacuous-green problem ..., exception-file hygiene, and gate failure UX" answers 'what'. Not a 4 because the 'when' clause is already explicit and specific, not merely implied or generic.

5 / 5

Trigger Term Quality

Natural user phrasings are present: "designing, wiring, debugging, or being blocked by quality-gate infrastructure — git hooks, lint matrices, exception files, complexity gates, Stop hooks". A few commonly-said variants are missing (e.g., "pre-commit hooks", "CI checks", "build gates"), keeping it below the comprehensive-synonym bar of a 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche and even disambiguates against the closest sibling: "verification-ratchet defines WHAT the checks are; this skill defines how the machinery that runs them stays honest." Trigger terms (Stop hooks, exception files, lint matrices) are specific enough that conflict risk with generic linting/CI skills is minimal.

5 / 5

Total

18

/

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

igouss/gitweb-rs

Path

.claude/skills/quality-gates/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.