CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-gates

This skill should be used when the user asks to "open a PR", "prepare for review", "address review comments", "run gates", or "verify before pushing" in this repository. Enforces preflight/gate workflow, migration safety, and review-evidence closure.

74

Quality

93%

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

92%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 exemplary instruction-only skill body: lean, well-sectioned, with a mandatory gated sequence, explicit error-recovery rules, and a concrete handoff checklist. Its only gap is that some verification-oriented directives point at categories of commands rather than naming specific ones.

DimensionReasoningScore

Conciseness

Every line is a directive with no concept explanation, padding, or restatement of what Claude already knows (e.g. "Do not push when any gate is red", "Never edit an existing file in `migrations/"). Lean and efficient; each token earns its place.

5 / 5

Actionability

Concrete executable commands are present (`just preflight`, `just gate-pr`), but several directives remain placeholders — "Targeted verification command", "Run targeted tests in addition to broad gate runs" — rather than specific runnable commands or examples. Not 5 because the guidance is not uniformly copy-paste ready; not 3 because the core flow commands are real and executable.

4 / 5

Workflow Clarity

The "Mandatory Flow" is a numbered sequence with explicit validation checkpoints (gates red → no push) and a feedback loop for error recovery ("If the same command fails twice in one session, stop rerunning and switch to root-cause debugging"), plus a concrete recovery rule for migration flags. Not 4 because both the checkpoints and the retry/recovery loop are explicit.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no external material needed, and it is organized into clean one-glance sections (flow, review closure, async changes, migrations, handoff). Per the simple-skill guideline, well-organized sections with no reference indirection score 5; there are no buried or nested references.

5 / 5

Total

19

/

20

Passed

Description

91%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 pairs an explicit trigger clause containing five natural quoted phrases with a compact statement of what the skill enforces, all in third person with no fluff. The only weakness is mild overlap risk with generic code-review skills and a 'what' that names domains rather than enumerating actions.

DimensionReasoningScore

Specificity

"Enforces preflight/gate workflow, migration safety, and review-evidence closure" lists several specific action areas with only minor gaps in coverage. Not 5 because the 'what' stays at the level of named domains rather than enumerating the concrete actions within each.

4 / 5

Completeness

Both parts are explicit: the 'what' ("Enforces preflight/gate workflow, migration safety, and review-evidence closure") and the 'when' ("when the user asks to ... in this repository") with concrete trigger phrases. Not 4 because the 'when' clause is fully explicit rather than only approximately stated.

5 / 5

Trigger Term Quality

Five quoted natural phrases users would actually say — "open a PR", "prepare for review", "address review comments", "run gates", "verify before pushing" — give comprehensive coverage. Not 4 because no significant natural term for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

"run gates", the preflight workflow, and migration safety carve a distinct niche, but "address review comments" and "prepare for review" could also match general code-review skills. Mostly distinct with minor overlap risk against closely related skills.

4 / 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
spacedriveapp/spacebot
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.