fluid-release

Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the schedule and repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.

Quality

92%

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

85%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 highly actionable with well-structured progressive disclosure and a clear, validated release workflow. Its main weakness is redundancy around the autonomous fallback procedure, which inflates the token budget without adding guidance.

Suggestions

Consolidate the three repeated descriptions of the GitHub-issue fallback (autonomous mode requirements, blocker handling, and 'Autonomous Mode: Fallback to Issues') into a single canonical section that the others link to.

Merge the duplicated auto-detect and phase-completion guidance that appears in both 'Auto-detecting release state' and 'Behavior by Mode' to reduce repetition.

Move the human-steps list and checkpoints table closer to the workflow selection so the operational sequence reads as one continuous flow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and actionable, but the fallback-to-GitHub-issue procedure is restated three times (autonomous mode requirements, blocker handling, and a dedicated fallback section) and autonomous-mode guidance recurs across sections, which could be consolidated.	3 / 5
Actionability	Provides copy-paste-ready git/gh/pnpm/flub commands, a CI-safe alternatives table, exact working-branch naming conventions, and concrete PR title formats covering the common release cases.	5 / 5
Workflow Clarity	Phases are sequenced with a state-detection decision table, an interactive-vs-autonomous checkpoint table, and explicit validation (readiness check, release-blocking issue/PR gate) before proceeding on this batch operation.	5 / 5
Progressive Disclosure	The body is a clear overview that points to four real one-level-deep reference files via a phase-to-reference selection table, with all referenced paths verified to exist and easy to navigate.	5 / 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.

The description is specific, trigger-rich, and clearly states both capabilities and activation conditions in third person. It is a strong model of a well-formed skill description with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—'release prep, branching, version bumps, changelogs, release notes, and type test baselines' plus auto-detection and issue fallback—giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (the listed release activities) and 'when' via a concrete 'Triggers on ...' clause with specific trigger phrases.	5 / 5
Trigger Term Quality	Triggers on natural user phrases and synonyms—'release', 'do the release', 'release status', 'version bump', 'release notes', 'changelog', 'release branch', 'release engineering'—matching how a user would actually ask.	5 / 5
Distinctiveness Conflict Risk	Scoped to the 'Fluid Framework client release group' with a distinct, niche trigger set, making collision with unrelated skills unlikely.	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: microsoft/FluidFramework
Path: .claude/skills/fluid-release/SKILL.md
Commit: f02e424

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