frb-publish-release

Publish a flutter_rust_bridge release end to end: preflight checks, changelog preparation, frb_internal release publishing, released-version polling, CI babysitting, and post-release CI verification.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/frb-publish-release/SKILL.md

Quality

Content

92%

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

Highly actionable, lean content with an explicit sequenced workflow and strong validation checkpoints. The main gap is progressive disclosure: it is a single dense file that does not offload any detail to reference files.

Suggestions

Move the CI-gate allowlist and narrow exception conditions into a references file (e.g. references/ci_gate.md) and link to it from the Preflight section to shorten SKILL.md.

Add a one-line summary or table of contents at the top so the six-phase flow is scannable before the dense per-phase detail.

Dimension	Reasoning	Score
Conciseness	There is no exposition of concepts Claude already knows; the body is exact commands, the regex "^\d+\.\d+\.\d+(-beta\.\d+)?$", and operational guards throughout, so every token earns its place; it is above score 2 because nothing reads as padded or explanatory.	3 / 3
Actionability	Copy-paste-ready bash commands, exact regex, exact file paths (CHANGELOG.md, frb_dart/pubspec.yaml), and a concrete JSON shape for get-released-version make this fully executable; it exceeds score 2 because no guidance is pseudocode or abstract.	3 / 3
Workflow Clarity	Six numbered phases carry explicit validation gates ("Stop if any submodule path remains uninitialized", "Stop if the preflight fails", "Wait until every package has isReleased: true") plus a post-release failure-classification feedback loop, matching the score-3 anchor; it is above score 2 because checkpoints are explicit, not implicit.	3 / 3
Progressive Disclosure	Sections are well organized and sibling skills are referenced by name, but all detail (the CI-gate allowlist, the narrow exception conditions) is inline in one ~135-line file with no offloading to reference files, so it does not reach the score-3 'appropriately split' anchor.	2 / 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.

A specific, well-scoped release description with concrete named phases, but it omits an explicit 'Use when…' trigger clause and leans on some internal jargon, which limits trigger-term quality and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when publishing, cutting, or babysitting a flutter_rust_bridge release.'

Soften internal jargon ('frb_internal release publishing', 'released-version polling') or pair it with the natural phrasing a maintainer would actually say.

Dimension	Reasoning	Score
Specificity	"preflight checks, changelog preparation, frb_internal release publishing, released-version polling, CI babysitting, and post-release CI verification" lists multiple concrete release actions, matching the score-3 anchor; it is above score 2 because the actions are specific and enumerated rather than just naming a domain.	3 / 3
Completeness	It clearly states what the skill does across all phases, but lacks an explicit "Use when…" trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 2, so it cannot reach 3.	2 / 3
Trigger Term Quality	"Publish a flutter_rust_bridge release" is a natural trigger a maintainer would say, but internal terms like "frb_internal release publishing" and "released-version polling" are jargon and common variations (e.g. "cut/ship a release") are absent, so it stops at score 2 rather than 3.	2 / 3
Distinctiveness Conflict Risk	Scoped to "flutter_rust_bridge release end to end", a distinct niche with specific triggers unlikely to fire for unrelated skills; it is above score 2 because the product-qualified scope is unambiguous.	3 / 3
	Total	10 / 12 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: fzyzcjy/flutter_rust_bridge
Path: .claude/skills/frb-publish-release/SKILL.md
Commit: 1d5348b

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