frb-lint

Use when you need to run lint, format, or clippy checks in flutter_rust_bridge

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

87%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 clean, highly actionable single-purpose skill with excellent conciseness and structure. Its only meaningful gap is the absence of a validation/verification step for the auto-fixing batch command, which caps workflow clarity.

Suggestions

Add a verification checkpoint after "./frb_internal lint --fix", e.g. instruct to review the resulting diff and run the test suite before committing, so the batch auto-fix has a feedback loop.

Briefly note what to do when a lint check fails (fix and re-run, or report the unfixable finding) to give the workflow an explicit error-recovery path.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — a compact command table and a four-item list with no concept explanation or padding; every token earns its place and it assumes Claude's competence.	5 / 5
Actionability	Provides copy-paste-ready, fully executable commands (e.g. "./frb_internal lint --fix") covering the common dart/rust splits, matching the anchor for fully executable guidance with specific examples.	5 / 5
Workflow Clarity	The recommended "./frb_internal lint --fix" is a batch operation that auto-modifies files across the project, yet the skill provides no validation/verification checkpoint (e.g. review the diff or run tests); per the rubric's destructive/batch cap this limits the score to 3 even though the single action is otherwise unambiguous.	3 / 5
Progressive Disclosure	Under 50 lines with well-organized sections (Quick Reference, What Lint Includes) and a single clearly-signaled one-level reference to the frb-dev-env skill; no nested or buried references, and no bundle files are needed.	5 / 5
	Total	18 / 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.

A concise, well-scoped description that clearly states what the skill does and when to use it, anchored to a specific project. It is strong but not maximal because the trigger guidance and action coverage could be slightly more comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain (flutter_rust_bridge) and three concrete actions — "run lint, format, or clippy checks" — matching the anchor that lists several specific actions with minor gaps in coverage; not a 5 because coverage is not comprehensive (e.g. the dart/rust split is omitted).	4 / 5
Completeness	It answers both what (run lint/format/clippy checks) and when ("Use when you need to run lint, format, or clippy checks in flutter_rust_bridge"), but the when-clause largely restates the what rather than offering distinct trigger scenarios, matching the 4 anchor; not a 5 because the trigger guidance is not enriched with concrete alternative phrasings.	4 / 5
Trigger Term Quality	"lint", "format", and "clippy" are natural terms a user would say, plus the domain keyword "flutter_rust_bridge"; a few natural synonyms (e.g. "check", "analyze", "tidy") are missing, so it sits below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to "flutter_rust_bridge" with distinct lint/format/clippy triggers, giving it a clear niche with minimal conflict risk against 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-lint/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.