frb-code-generation

Use when modifying Rust APIs, codegen, generated examples, or platform scaffolds in flutter_rust_bridge to select generation commands and preserve source-of-truth and convergence rules

Quality

78%

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-code-generation/SKILL.md

Quality

Content

82%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 is a lean, command-driven reference with a strong Quick Reference table and genuine convergence/validation feedback loops. Its only real gaps are that the workflow is rule-structured rather than a crisp ordered sequence, and a few dense advisory passages could be trimmed or split out.

Suggestions

Add a short numbered "Generation workflow" sequence (identify change type → run narrowest owning generator → re-run and require clean diff → validate non-Generate jobs) so the convergence rules read as an explicit ordered process.

Consider moving the OHOS Integrate Composition and Provenance detail tables into a references file, keeping SKILL.md as an overview that links one level deep.

Tighten or remove the most abstract advisory sentences (e.g. the "formatter-unstable intermediate text" clause) to lift conciseness toward fully lean.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no explanatory padding about what codegen or FRB is) and stays rule-and-command oriented, but a few dense sentences (e.g. "Do not hand formatter-unstable intermediate text to a different generation lane") and repeated "source of truth" phrasing could be tightened.	4 / 5
Actionability	The Quick Reference table maps each change type to a copy-paste-ready `./frb_internal ...` command with concrete file paths, and the rules cite specific paths and commands, fully covering the common generation cases.	5 / 5
Workflow Clarity	Explicit validation checkpoints are present ("Run the owning generation command a second time and require a clean diff. A single successful run is not convergence" and the suspect-output validation rule), but the body is rule-organized rather than a single numbered sequence, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and is well-organized into a Quick Reference table and clearly headed Important Rules subsections, with other skills (frb-dev-env, frb-fix-ci, frb-cargokit) signaled inline; some detailed sections (OHOS Integrate Composition, Provenance) could plausibly live in separate references.	4 / 5
	Total	17 / 20 Passed

Description

73%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 well-targeted to a specific FRB codegen niche with an explicit "Use when" trigger and low conflict risk. Its main weakness is that the capability statement blends concrete actions with abstract rule-preservation language, slightly diluting specificity and completeness.

Suggestions

Lead the description with the concrete capability (e.g. "Selects the minimal flutter_rust_bridge generation command for a given Rust/API/scaffold change") before the rule-preservation clause.

Add natural trigger synonyms such as "regenerate" or "rebuild generated code" alongside "codegen".

Tighten "preserve source-of-truth and convergence rules" into a more capability-like verb phrase so the "what" reads as an action rather than a constraint.

Dimension	Reasoning	Score
Specificity	The description names the domain precisely ("modifying Rust APIs, codegen, generated examples, or platform scaffolds in flutter_rust_bridge") and gives one concrete action ("select generation commands"), but the remaining actions ("preserve source-of-truth and convergence rules") are constraints rather than concrete operations, leaving it short of comprehensive coverage.	3 / 5
Completeness	It explicitly answers "when" via "Use when modifying Rust APIs, codegen, generated examples, or platform scaffolds" and gives a "what" ("select generation commands and preserve source-of-truth and convergence rules"), though the "what" leans on abstract rule phrasing rather than crisp capability statements.	4 / 5
Trigger Term Quality	Terms like "Rust APIs", "codegen", "generated examples", "platform scaffolds", and "flutter_rust_bridge" are natural vocabulary a contributor would use, with good coverage; a few common synonyms (e.g. "regenerate", "rebuild") are absent.	4 / 5
Distinctiveness Conflict Risk	The trigger is tightly scoped to flutter_rust_bridge generation workflows, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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-code-generation/SKILL.md
Commit: 0876e2e

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.