release

Prepare a lading release. Updates CHANGELOG.md, bumps version in Cargo.toml, updates Cargo.lock, commits, and creates a PR.

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/release/SKILL.md

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, highly actionable release runbook with a clear sequence and a destructive-operation guard, but its workflow clarity is capped by missing validation/feedback loops on the risky cargo check and PR/tag steps.

Suggestions

Add an explicit feedback loop after `cargo check` (e.g., if it fails, re-run after fixing Cargo.toml before staging) and a verification step confirming the lockfile version actually changed.

Include a brief error-recovery note for the tag/push step (e.g., what to do if `git push origin v<version>` is rejected due to a non-fast-forward) so the outward-facing steps have checkpoints.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no concept explanations (no padding about semver or Cargo.lock); every line instructs, matching the score-3 anchor of assuming Claude's competence.	3 / 3
Actionability	Provides fully executable commands (git checkout -b, cargo check, git tag -a, git push origin) plus concrete file targets and an exact commit message format, matching the score-3 anchor of copy-paste-ready guidance.	3 / 3
Workflow Clarity	Has a clear numbered 1-7 sequence and an explicit destructive-op guard ('NEVER use git push --tags') plus a confirm checkpoint, but lacks validation/feedback loops for risky outward-facing steps (e.g., what to do if cargo check fails, or verifying the PR was created), which per the scoring notes caps workflow_clarity at 2.	2 / 3
Progressive Disclosure	Under 50 lines, single-purpose, with no external references needed and well-organized titled sections, qualifying for the score-3 allowance for simple skills with no bundle files.	3 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, listing concrete release actions with clear artifacts, but it omits an explicit 'Use when...' trigger clause and has only moderate coverage of natural user phrasing.

Suggestions

Add an explicit trigger clause such as 'Use when preparing or cutting a lading release, bumping the crate version, or opening a release PR.' to reach score-3 completeness.

Broaden natural trigger terms to include user phrasings like 'cut a release', 'publish a new version', or 'make a release PR' rather than anchoring on the project name 'lading'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Updates CHANGELOG.md, bumps version in Cargo.toml, updates Cargo.lock, commits, and creates a PR'), matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Clearly states what it does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains some relevant terms (release, version, PR, CHANGELOG) but lacks breadth and natural-user phrasing variations like 'cut a release' or 'publish a new version'; 'Prepare a lading release' leans on the project name rather than natural triggers, so it sits at the score-2 level rather than the full coverage of score 3.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (the lading project release process) with concrete, distinct artifacts (CHANGELOG, Cargo.toml, Cargo.lock, PR), making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: DataDog/lading
Commit: 5761294

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