kiln-prerelease-check

Run the Kiln pre-release smoke test suite plus the standard CI checks (checks.sh), diagnose every prerelease test that broke (and why), and write a clean readable report with recommended actions. Read-only — it never edits code. Use when the user wants to validate a release candidate, run prerelease tests, or asks for a "prerelease check / smoke / audit".

Quality

88%

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

77%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 highly actionable, well-sequenced workflow with strong validation feedback loops, but it is a long monolithic document whose repeated guardrail emphasis and inline report template leave room for tightening and for splitting detailed material into one-level-deep reference files.

Suggestions

Consolidate the 'read-only / make no edits' guardrail into one authoritative statement in Global rules and have phase-level mentions reference it instead of restating it six times.

Move the ~80-line report template and the Phase 4c coverage table into reference files (e.g. references/report_template.md, references/coverage.md) with a one-line pointer from Phase 5, reducing the monolithic SKILL.md body.

Trim verbose justifications such as the Phase 4a retry rationale down to imperative guidance, trusting Claude to follow the stated retry rules without the extended motivation.

Dimension	Reasoning	Score
Conciseness	It assumes Claude's competence (no basic-concept padding) and is dense with operational detail, but the read-only guardrail is restated six times across phases and several justification passages (e.g. the Phase 4a retry rationale) could be tightened.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout — `uv run ./checks.sh --agent-mode`, the `--runprerelease` pytest invocation, an inline Python status-check script, grep pipelines, and node-id retry commands — with exact paths, env vars, and a concrete report template.	5 / 5
Workflow Clarity	Six explicitly sequenced phases with validation checkpoints (exit-code capture, retry→reclassify feedback loop, mandatory staleness sweep even on green runs, coverage audit) and a final checklist; the batch-operation validation cap does not apply because verification is pervasive.	5 / 5
Progressive Disclosure	Good section/phase structure, but the skill is monolithic at ~425 lines with no bundle/reference files; the ~80-line report template and the coverage table are inlined content that would be better split into referenced files.	3 / 5
	Total	16 / 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.

An exemplary description: concrete actions, an explicit 'Use when…' clause with multiple natural synonyms, a read-only boundary, and named artifacts that make the niche unambiguous. It cleanly hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Run the Kiln pre-release smoke test suite plus the standard CI checks (checks.sh)', 'diagnose every prerelease test that broke (and why)', 'write a clean readable report with recommended actions' — with comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what (run smoke suite + checks.sh, diagnose breaks, write report) and when ('Use when the user wants to validate a release candidate, run prerelease tests, or asks for a "prerelease check / smoke / audit"') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms a user would actually say: 'prerelease check / smoke / audit', 'validate a release candidate', 'run prerelease tests'.	5 / 5
Distinctiveness Conflict Risk	A clear niche — Kiln pre-release smoke testing with named artifacts (checks.sh, @pytest.mark.prerelease) — yields distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	20 / 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: Kiln-AI/Kiln
Path: .agents/skills/kiln-prerelease-check/SKILL.md
Commit: ff39535

Reviewed: ~20 hours 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.