release-digest

Post a "what's changed since the last release" recap to the release Slack channel for final QA. Groups merged PRs by author and classifies each as feature / bug fix / task. Use when the user wants a release recap, a changelog since the last tag, or to prep QA before cutting a release from main.

Quality

94%

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

88%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 well-structured, highly actionable workflow skill with concrete commands, an exact output template, and real validation checkpoints for an outward-facing post. The only soft spot is mild verbosity in the classification guidance.

Suggestions

Tighten the classification section: the model-catalog-as-Task rule is stated in the bucket definition, repeated as its own bold paragraph, and again in the decision order — consolidate to one canonical statement plus the decision-order line.

Consider moving the full Slack-template formatting rules (italics/underscore gotchas, excluded_prs rendering) into a short reference snippet or collapsing the per-rule bullets, since the worked example already demonstrates most of them.

The script path in the body (`.agents/skills/release-digest/scripts/gather_changes.py`) differs from the bundle layout (`scripts/gather_changes.py`); confirm the deployed path so the copy-paste command resolves as written.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and tightly procedural, but the classification section re-emphasizes the model-catalog-as-Task rule across the decision order and residual-bucket paragraphs in ways that could be trimmed without losing the signal.	4 / 5
Actionability	Fully executable: a concrete gather-script command (verified to exist), an exact Slack mrkdwn template with literal placeholders, the channel ID, and the named MCP tool — copy-paste ready for the common case.	5 / 5
Workflow Clarity	Four phases are clearly sequenced with explicit validation checkpoints (pr_count==0 stop, unresolved_prs warning, user confirmation before posting) and a closing checklist — the batch/outward-facing operation has the feedback loops the rubric requires.	5 / 5
Progressive Disclosure	Well-organized into phases with the complex git/gh logic correctly externalized into one one-level-deep script reference; the long inline classification rules are justified as core decision logic but keep this just short of a clean overview-only body.	4 / 5
	Total	18 / 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.

A strong, third-person description that concisely states concrete capabilities and gives explicit, multi-synonym trigger guidance. Both the 'what' and 'when' are clearly answered with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Post a recap to the release Slack channel', 'Groups merged PRs by author', 'classifies each as feature / bug fix / task' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what (post/group/classify) and when ('Use when the user wants a release recap, a changelog since the last tag, or to prep QA before cutting a release') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers natural synonyms users would say — 'release recap', 'changelog since the last tag', 'prep QA', 'cutting a release' — with several phrasings of the same intent.	5 / 5
Distinctiveness Conflict Risk	A narrow niche (release-channel QA recap, git-range change classification) with distinct triggers that no other skill would plausibly fire on; minimal conflict risk.	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/release-digest/SKILL.md
Commit: ff39535

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