release-please-development

This skill should be used when the user asks to "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", or mentions release-please, semantic versioning, or monorepo versioning.

1.39x

Quality

73%

Does it follow best practices?

Impact

92%

1.39x

Average score across 3 eval scenarios

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/toolkit/skills/release-please-development/SKILL.md

Quality

Content

72%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-organized, mostly executable skill body with excellent progressive disclosure and concise, copy-paste-ready single-package setup; the main gap is the absence of validation/verification checkpoints in the release workflow, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints to the setup/run workflow, e.g. after creating the release PR verify it was opened, and after merge confirm the GitHub release, tag, and version-file updates were created as expected.

Show a minimal multi-package (monorepo) config inline since the description promotes monorepo versioning as a primary trigger, instead of only linking it out.

Remove the duplicate "See Also" reference list (or repurpose it) since it repeats the same three links already given in "Quick Reference".

Dimension	Reasoning	Score
Conciseness	The body is lean, uses compact tables and complete code blocks, and avoids explaining concepts Claude already knows; the only trimming opportunity is the "See Also" section, which duplicates the top-of-file "Quick Reference" links.	4 / 5
Actionability	Setup provides copy-paste-ready, complete config JSON, manifest JSON, and a full GitHub Actions workflow YAML covering the common single-package case; the multi-package pattern emphasized in the description is only linked out rather than shown inline, leaving a minor gap.	4 / 5
Workflow Clarity	The "Basic Setup" and "How It Works" sections give a clear sequenced process, but there are no validation or verification checkpoints for an automated release flow that creates GitHub releases, tags, and mutates version files, capping this dimension at 3 per the destructive/batch-operations guidance.	3 / 5
Progressive Disclosure	SKILL.md is a well-structured overview pointing to three real one-level-deep reference files (single-package.md, multi-package.md, configuration.md), each clearly signaled in both Quick Reference and See Also, with detailed content appropriately split out.	5 / 5
	Total	16 / 20 Passed

Description

73%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, trigger-rich description that clearly signals when to invoke the skill and targets a distinct niche, with only minor weakness in that the skill's capabilities are expressed through user-request phrasing rather than an explicit declarative capability statement.

Dimension	Reasoning	Score
Specificity	The description names the domain (release-please, versioning, changelog, releases) and conveys several concrete actions through quoted trigger phrases like "configure automated releases", "manage version numbers", and "add changelog automation", but it lacks an independent explicit capability statement and is not comprehensive.	3 / 5
Completeness	The "when" is exemplary and explicit ("should be used when the user asks to..." with a concrete trigger list), and the "what" is conveyed through the same quoted action phrases, though the capability is implied via triggers rather than stated as a standalone declarative.	4 / 5
Trigger Term Quality	Strong natural-language trigger coverage including "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", plus tool/concept terms like "release-please", "semantic versioning", and "monorepo versioning"; a few synonyms or variants are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	A clear niche around the specific release-please tool and semantic/monorepo versioning, with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 4 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: dwmkerr/claude-toolkit
Path: plugins/toolkit/skills/release-please-development/SKILL.md
Commit: 4316684

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.