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

83%

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

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.

A highly actionable, well-structured skill body that maps change types to concrete commands and includes validation and convergence checkpoints for a generative workflow. It is only slightly limited by minor repetition and a few sub-rules that could be externalized into reference files.

Suggestions

Deduplicate the validation rule (stated both in the Overview blockquote and as the standalone 'Validation rule' line) to tighten conciseness.

Make implicit checkpoints explicit in the Root Documentation Fan-Out and Integrate Template Drift sections (e.g., add a 'verify generated docs match' or 'confirm template is the source' validation step).

Consider moving the OHOS Integrate Composition and Generated Output Provenance tables into a reference file referenced one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence, with no padding explaining what flutter_rust_bridge or codegen is; minor repetition (the validation rule appears in both Overview and as a standalone statement) keeps it just short of fully lean.	4 / 5
Actionability	Provides copy-paste-ready commands throughout ('./frb_internal precommit-generate', 'generate-internal-rust', 'precommit-integrate') and a Quick Reference table mapping every change type to a concrete command, fully covering the common cases.	5 / 5
Workflow Clarity	The Generation Convergence section gives a clear sequenced workflow with explicit validation ('Run the owning generation command a second time and require a clean diff') and the OHOS section has failure-rollback checkpoints; a few checkpoints elsewhere are implicit rather than spelled out.	4 / 5
Progressive Disclosure	Well-organized into Overview, Quick Reference, and topical rule sections with no nested references and no bundle files needed; at ~96 lines some detailed sub-rules (OHOS composition, provenance table) could live in separate reference files, leaving minor organization gaps versus an ideal split.	4 / 5
	Total	17 / 20 Passed

Description

83%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, trigger-explicit description that clearly states both what the skill does and when to use it, with concrete domain-specific keywords. It is slightly held back by abstract phrasing around 'source-of-truth and convergence rules' and minor overlap with sibling FRB skills.

Suggestions

Replace the abstract 'preserve source-of-truth and convergence rules' with a more concrete action verb phrase (e.g., 'pick the narrowest owning generator and verify a clean second-run diff') to lift specificity.

Add one or two natural synonyms a user might say (e.g., 'regenerate', 'flutter_rust_bridge codegen') to round out trigger-term coverage.

Clarify the boundary versus frb-fix-ci in the description (e.g., 'for command selection, not CI failure diagnosis') to reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete change types ('modifying Rust APIs, codegen, generated examples, or platform scaffolds') and concrete actions ('select generation commands and preserve source-of-truth and convergence rules'), but 'preserve source-of-truth and convergence rules' is somewhat abstract jargon, leaving minor gaps versus a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both 'what' ('select generation commands and preserve source-of-truth and convergence rules') and 'when' ('Use when modifying Rust APIs, codegen, generated examples, or platform scaffolds in flutter_rust_bridge') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good keyword coverage with natural terms a flutter_rust_bridge contributor would say ('Rust APIs', 'codegen', 'generated examples', 'platform scaffolds', 'flutter_rust_bridge'); a few common variations or synonyms are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (flutter_rust_bridge codegen command selection) with distinct triggers, but shares the FRB domain with sibling skills like frb-fix-ci and frb-cargokit, creating minor overlap risk rather than minimal conflict.	4 / 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-code-generation/SKILL.md
Commit: 8f2ab1b

Reviewed: ~1 hour 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.