frb-feature-flag

Use when adding or testing flutter_rust_bridge feature flags, especially flags that require coverage for both enabled and disabled states or should have package-level config plus item-level #[frb(...)] overrides.

Quality

85%

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

92%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 tight, well-structured instruction-only skill that gives concrete file paths and mechanism guidance with no wasted tokens. Its only gap is the absence of executable code examples, which is acceptable for an instruction-only skill but keeps actionability just below the top anchor.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or re-explanation of concepts Claude already knows — every line is direct guidance, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	Concrete, actionable guidance naming specific artifacts ('flutter_rust_bridge.yaml', the CLI, 'frb_example/pure_dart', item-level '#[frb(...)]' overrides); as an instruction-only skill it is mostly executable with only minor gaps, fitting the 4 anchor below the fully copy-paste-ready 5.	4 / 5
Workflow Clarity	A simple, single-purpose skill under 50 lines with clearly sequenced API-surface and test-coverage guidance and no destructive/batch operations requiring validation, so the simple-skill exception applies and clarity is unambiguous.	5 / 5
Progressive Disclosure	Well under 50 lines with no need for external references (none of references/scripts/assets are present) and cleanly organized sections, satisfying the guideline that simple skills can score 5 with well-organized sections alone.	5 / 5
	Total	19 / 20 Passed

Description

78%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 specific, well-triggered, and clearly distinct, explicitly pairing a 'Use when' clause with concrete capability statements about both-state coverage and config/override handling. The only shortfall is that trigger keyword coverage is strong rather than exhaustive.

Suggestions

Add a couple of natural synonyms (e.g. 'toggling', 'enabling/disabling flags') to push trigger_term_quality toward exhaustive coverage.

Tighten the 'what' clause into a crisp capability list first, then the 'Use when' trigger, to mirror the top completeness anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'adding or testing flutter_rust_bridge feature flags', 'coverage for both enabled and disabled states', 'package-level config plus item-level #[frb(...)] overrides' — with only minor gaps in full flag-operation coverage, fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive 5 or the 1-2-actions 3.	4 / 5
Completeness	Explicit 'Use when...' trigger plus a clear 'what' (feature flags needing both-state coverage and config/override handling) — both present with the 'when' concrete but slightly elaborated rather than maximally explicit, fitting the 4 anchor above the 3 (which lacks 'when').	4 / 5
Trigger Term Quality	Good natural coverage with 'adding or testing ... feature flags', 'coverage', and 'enabled and disabled states', plus the domain name 'flutter_rust_bridge'; it lacks only a few synonyms, matching the 'good keyword coverage; a few natural terms missing' anchor and not the near-complete 5.	4 / 5
Distinctiveness Conflict Risk	A tightly scoped niche — flutter_rust_bridge feature flags with both-state coverage and #[frb(...)] override handling — gives clear distinct triggers and minimal conflict risk, matching the 'clear niche with distinct triggers' anchor.	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-feature-flag/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.