frb-upgrade-flutter

Upgrade flutter_rust_bridge to a new Flutter stable release. Use when changing Flutter/Dart versions, devcontainer Docker images, CI/post-release pins, generated Flutter scaffolds, or platform compatibility.

Quality

89%

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

Quality

Content

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

An exceptionally lean, actionable orchestration skill with a well-sequenced multi-step workflow and explicit validation checkpoints. The only weakness is that all operational detail lives inline in SKILL.md with no bundle files to split out deeper material.

Suggestions

Move the detailed version-inventory file lists and ripgrep patterns into a references/ file (e.g. references/version-inventory.md) and link to it from section 2, keeping SKILL.md as a tighter overview.

Extract the per-step validation commands behind sections 7-8 into a scripts/ or references/ checklist so the inline body stays a high-level routing layer.

Consider a brief references/compatibility-migrations.md for the platform-specific workaround guidance referenced in section 8, so that detail is one level deep rather than implied.

Dimension	Reasoning	Score
Conciseness	The body is lean, imperative, and free of concept explanation — it never explains what Flutter or flutter_rust_bridge is, and every bullet is directive, assuming Claude's competence; each token earns its place.	5 / 5
Actionability	Concrete, executable guidance throughout — copy-paste-ready `rg -n` ripgrep commands, an explicit file inventory (`.devcontainer/Dockerfile`, `.github/workflows/ci.yaml`, etc.), named toolchain variables (`FRB_MAIN_FLUTTER_VERSION`), and a numbered validation sequence cover the common cases.	5 / 5
Workflow Clarity	A clear 9-section sequence with explicit validation checkpoints — the ordered validation list in section 7 ("Validate in this order: 1…6"), the dependency-ordered CI triage in section 8, and the independent review gate in `frb-pr-review` — plus a feedback loop via `frb-fix-ci`.	5 / 5
Progressive Disclosure	Well-organized into numbered sections with clearly signaled one-level-deep references to sibling skills ("Read `frb-dev-env` before…"), but the operational detail is dense and fully inline with no bundle files (references/, scripts/, assets/ are absent), leaving minor organization gaps versus the cleanly split anchor 5.	4 / 5
	Total	19 / 20 Passed

Description

82%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, third-person description that clearly states what the skill does and when to use it with concrete trigger scenarios. The main limitation is that the "what" names only a single upgrade action rather than enumerating several concrete actions.

Suggestions

Expand the "what" beyond a single action by listing several concrete operations the skill performs (e.g. update toolchain pins, regenerate Flutter scaffolds, synchronize CI and post-release pins), matching the multi-action coverage of the specificity anchor 4-5.

Add natural synonyms and file/extension triggers (e.g. pubspec.yaml, .github/workflows, CargoKit) to the "Use when" clause to broaden keyword coverage toward the trigger_term_quality anchor 5.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — "Upgrade flutter_rust_bridge to a new Flutter stable release" — but offers only that single action, matching the anchor for naming a domain with 1-2 concrete actions rather than the multi-action coverage of a 4 or 5.	3 / 5
Completeness	It explicitly answers both what ("Upgrade flutter_rust_bridge to a new Flutter stable release") and when ("Use when changing Flutter/Dart versions, devcontainer Docker images, CI/post-release pins, generated Flutter scaffolds, or platform compatibility") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"Use when changing Flutter/Dart versions, devcontainer Docker images, CI/post-release pins, generated Flutter scaffolds, or platform compatibility" gives good keyword coverage across natural trigger scenarios, but lacks synonyms and file extensions (e.g. pubspec.yaml, .github) that would lift it to a 5.	4 / 5
Distinctiveness Conflict Risk	The flutter_rust_bridge upgrade niche is highly specific with distinct triggers tied to Flutter/Dart version changes and CI pins, giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 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: fzyzcjy/flutter_rust_bridge
Path: .claude/skills/frb-upgrade-flutter/SKILL.md
Commit: 8f2ab1b

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