CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 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

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 body delivers highly actionable, executable guidance with excellent workflow sequencing (state-detection table, checkpoints, validation, and fallback loops) and a clean one-level-deep reference structure. Its main weakness is redundancy: the fallback-to-issue procedure, remote preference, and pause behavior are each repeated multiple times, inflating token cost without adding information.

Suggestions

Consolidate the GitHub-issue fallback procedure, which is fully spelled out three times (autonomous mode requirements, blocker handling in Before Starting, and the Fallback to Issues section). State it once and cross-reference it from the other two locations.

Deduplicate the upstream/origin remote preference between Environment Detection and Key Context, and the pause-and-confirm behavior between Interactive Mode, the Commands section, and the Checkpoints table — keep the Checkpoints table as the single source of truth.

The auto-detection Steps 1-4 detail could move to a short reference file, leaving SKILL.md with just the state/action table, if further token savings are desired.

DimensionReasoningScore

Conciseness

Most of the body is dense, repo-specific operational content Claude cannot know (CI-safe command alternatives, branch naming, ADO pipeline definitions, remote selection), but it could be tightened: the GitHub-issue fallback procedure is spelled out in full three times (autonomous requirements, blocker handling, and the fallback section), and both the upstream/origin remote preference and the pause-and-confirm behavior are each restated 2-3 times. This exceeds the 'minor instances' of the score-4 anchor but is far from the padding of score 2.

3 / 5

Actionability

Fully executable throughout: exact commands like `git tag -l 'client_v*' --sort=-version:refname | head -1`, `gh pr list --repo microsoft/FluidFramework --search "release-prep/<VERSION>"`, and CI-safe alternatives such as `pnpm -r --include-workspace-root exec npm pkg set version=<VERSION>` cover the common cases copy-paste ready, with concrete placeholders. Matches the score-5 anchor; not 4 because no step requires the reader to invent commands.

5 / 5

Workflow Clarity

The multi-phase process is clearly sequenced: an auto-detection state table mapping repo state to the next action, 'Before Starting' readiness and blocker validation, a checkpoints table distinguishing interactive vs autonomous behavior, a human-steps checklist, and explicit error-recovery loops (fallback to a release-blocking GitHub issue, retry-on-next-run for unavailable npm packages). Validation checkpoints and feedback loops are explicit, matching score 5 rather than 4.

5 / 5

Progressive Disclosure

The body is an orchestration overview with three well-signaled, one-level-deep references (all three references/*.md files exist) presented in a table with when-to-use and CI-automatability context. Reference files link only sideways to each other or back to SKILL.md, with no nested content chains, and per-phase step detail is appropriately split out of the main file. Matches the score-5 anchor.

5 / 5

Total

18

/

20

Passed

Description

92%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 description: it states concrete capabilities across the full release lifecycle, gives an explicit trigger list with natural phrasing, and is tightly scoped to the Fluid Framework client release group. The only improvement space is broader trigger synonym coverage (e.g., publish, cut a release).

DimensionReasoningScore

Specificity

"minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines" lists multiple concrete actions with comprehensive coverage of the release lifecycle. Matches the score-5 anchor; score 4 would require minor coverage gaps, and none are evident within this domain.

5 / 5

Completeness

Explicitly answers both questions: the "what" (release prep, branching, version bumps, changelogs, release notes, type test baselines) and the "when" ("Triggers on 'release', 'do the release', 'release status', version bump, release notes, changelog, release branch, or release engineering"). Both are concrete and explicit, matching the score-5 anchor rather than the score-4 anchor where the 'when' is only implicitly present.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would say: "do the release", "release status", "version bump", "release notes", "changelog", "release branch", "release engineering". Good coverage, but common synonyms like "publish", "cut a release", or "ship" are missing, so it falls between the 4 and 5 anchors — closer to 4 since a few natural terms are absent.

4 / 5

Distinctiveness Conflict Risk

"Fluid Framework client release group" establishes a clear niche, and the triggers are specific to release engineering for this repo, so conflict risk with other skills is minimal. Not 4: there is no meaningful overlap with closely related skills since the domain and trigger vocabulary are narrowly scoped.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.