meta-pre-commit-quality-gate

Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

80%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 concise, well-structured overview body that provides concrete fallback commands and assumes Claude's competence. Its main weakness is that the batch-operation validation logic (the BLOCK/APPROVE arbitration) is encoded in the frontmatter composition rather than restated as explicit checkpoints in the body, capping workflow clarity.

Suggestions

Add a brief body section restating the arbitration rule as an explicit validation checkpoint (e.g. 'If ANY gate returns FAIL → BLOCK; only APPROVE when all three PASS') so the batch workflow's validation is visible without reading the frontmatter.

Surface the per-gate PASS/FAIL contract in the body (the one-line reply format each sub-agent must return) so a reader can verify gate outputs without inspecting the composition steps.

Clarify the fallback ordering as a validation chain (e.g. 'stop and report on the first failing gate') rather than only listing the three commands 'in order'.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows (it never explains what ruff/mypy/pytest are); every line earns its place, matching the score-5 anchor rather than 4 (no over-explanation to trim).	5 / 5
Actionability	The Fallback section gives copy-paste-ready commands ('uv run ruff check src tests', 'uv run mypy src/opensquilla --show-error-codes', 'uv run pytest -q'), but the primary orchestration lives in the frontmatter rather than the body, leaving minor gaps versus the fully-self-contained score-5 anchor.	4 / 5
Workflow Clarity	A rough sequence is present (three gates in parallel then arbitrate; fallback lists ruff→mypy→pytest in order), but the batch-operation validation/BLOCK-arbitration logic is in the frontmatter, so the body itself has only implicit checkpoints — the batch-operation cap holds this at 3 rather than 4.	3 / 5
Progressive Disclosure	The body is under 50 lines with no external bundle files (references/scripts/assets absent) and is organized into clear sections (Trigger surface, Fallback), so the simple-skill exception yields a score of 5 for well-organized structure without external references.	5 / 5
	Total	17 / 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 specific, third-person description that clearly states both what the skill does (run ruff/mypy/pytest in parallel over the staged diff and arbitrate a verdict) and when to use it (before local commits). It is distinctive and uses natural trigger terms, with only minor room for additional synonyms.

Dimension	Reasoning	Score
Specificity	Names the three concrete gates ('ruff + mypy + pytest'), 'in parallel over the staged diff', and 'arbitrate a single BLOCK/APPROVE verdict' — multiple specific actions with comprehensive coverage of the gate set, matching the score-5 anchor rather than 4 (no real coverage gaps).	5 / 5
Completeness	Explicitly answers what ('Run three quality gates ... then arbitrate a single BLOCK/APPROVE verdict') and when ('Use before committing changes locally when you want a comprehensive pre-commit gate ...'), matching the score-5 anchor with a concrete trigger clause; not 4 because the 'when' is explicit and specific.	5 / 5
Trigger Term Quality	Includes natural developer terms ('pre-commit', 'staged diff', 'committing changes', ruff/mypy/pytest) but lacks synonyms or file-extension variants, so it sits above the score-3 anchor yet below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — a pre-commit gate over the staged diff arbitrating BLOCK/APPROVE with named tools — giving it distinct triggers and minimal overlap risk, matching the score-5 anchor.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/exp/meta-pre-commit-quality-gate/SKILL.md
Commit: 94ac35e

Reviewed: 3 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.