mflux-release

Prepare a release in mflux (version bump, changelog, contributors, uv lock) without tagging/publishing. Use when preparing a release branch or release PR.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/mflux-release/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.

The content is an efficient, mostly-executable release-prep checklist with clean structure. Its main weakness is workflow clarity: for a release/batch operation, validation is optional rather than an enforced checkpoint, so it lacks the feedback loop the rubric expects.

Suggestions

Make validation a mandatory checkpoint in the release flow rather than optional (e.g., run `just test-fast`/`just build` and only commit `Release <version>` when they pass), adding an explicit validate-fix-retry loop.

Tighten the contributor-sourcing step with a single concrete `gh` query example and a fallback rule, so the procedure is closer to copy-paste ready.

Clarify how to obtain <last-version> (e.g., `git tag --list 'v.*' --sort=-v:refname | head -1`) so the git log command is executable without manual lookup.

Dimension	Reasoning	Score
Conciseness	The body is a lean checklist that assumes Claude's competence and avoids explaining git/changelog basics; the gh/web fallback sub-bullets add some length but each earns its place, matching the efficient-but-slightly-trimmable anchor 4.	4 / 5
Actionability	Provides concrete executable commands (git log --oneline v.<last-version>..HEAD, uv lock, just test-fast, gh pr list --state merged) and exact URLs, but placeholders like <owner>/<repo> and the procedural contributor-sourcing step require substitution and judgment, leaving minor gaps versus copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The release steps are clearly sequenced as a checklist, but this is a batch/release operation and validation/sanity checks are marked optional with no validate-fix-retry feedback loop, so the missing-validation cap holds it at 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, and well-organized with clear section headers (When to Use, Instructions) and no bundle files, so the simple-skill exception applies and structure is unambiguous.	5 / 5
	Total	16 / 20 Passed

Description

87%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.

The description is strong: it states concrete release-prep actions, an explicit scope boundary, and a clear Use-when trigger. Its only soft spot is trigger-term breadth and action specificity, where a few more synonyms or fully verbalized actions would push it from good to comprehensive.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions in parentheses ("version bump, changelog, contributors, uv lock") plus an explicit boundary ("without tagging/publishing"), but contributors and lock are named as nouns rather than fully spelled-out actions, leaving minor coverage gaps versus the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what ("Prepare a release in mflux ... without tagging/publishing") and when ("Use when preparing a release branch or release PR") with concrete trigger phrases, matching the anchor 5.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user would say ("preparing a release branch or release PR", "Prepare a release") with good keyword coverage, though it omits some common synonyms or file/term variations that would reach the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (mflux release prep) with distinct triggers and an explicit non-goal boundary (no tagging/publishing), minimizing overlap with other skills.	5 / 5
	Total	18 / 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: filipstrand/mflux
Path: .cursor/skills/mflux-release/SKILL.md
Commit: 1430b27

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