CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-lint

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

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/frb-lint/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, fully actionable, and well-organized for a simple single-purpose skill, with copy-paste-ready commands and no unnecessary explanation. Its only gap is the absence of a verification/review step for the batch auto-fix operation.

Suggestions

Add a short validation/review step after 'lint --fix', e.g. review the diff or re-run './frb_internal lint' to confirm no remaining findings before committing.

Briefly note how to interpret common lint/clippy failure output so Claude knows when to stop and fix versus proceed.

Clarify whether 'lint --fix' should be run before or after the dart/rust-specific commands, giving an explicit sequence for the batch operation.

DimensionReasoningScore

Conciseness

The body is lean and table-driven with no explanations of concepts Claude already knows; the single operational note is relevant rather than padded.

3 / 3

Actionability

Provides exact, copy-paste-ready executable commands ('./frb_internal lint --fix', 'lint-dart', 'lint-rust') with descriptions and a recommended default.

3 / 3

Workflow Clarity

The recommended command and breakdown give an unambiguous single action, but the batch auto-fixing 'lint --fix' operation has no validation or verification step for reviewing failures, capping it at 2.

2 / 3

Progressive Disclosure

A simple under-50-line skill with clean, well-organized sections (Quick Reference table and a What Lint Includes list) and no nested references; organization is appropriate for its size.

3 / 3

Total

11

/

12

Passed

Description

57%

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-scoped to a specific project with an explicit 'Use when' trigger and natural lint/format/clippy keywords, but it is a single clause that implies its capabilities rather than comprehensively and explicitly stating both what it does and when to use it.

Suggestions

Expand the capability half into concrete sub-actions, e.g. 'Run lint, format, dart analyze, and cargo clippy checks across the Dart and Rust code in flutter_rust_bridge.'

Add natural trigger variations users might say, such as 'fmt', 'analyze', or 'lint the Dart/Rust code', to broaden trigger coverage.

Separate the 'what' and 'when' into distinct clauses so both are explicitly stated rather than conflated in one 'Use when' sentence.

DimensionReasoningScore

Specificity

Names concrete actions ('run lint, format, or clippy checks') and a specific project domain, but the actions are tool-action categories rather than a comprehensive enumeration of the concrete sub-checks performed.

2 / 3

Completeness

An explicit 'Use when...' trigger covers the 'when', but the 'what does this do' is only implied through the same clause rather than stated separately, so both halves are not simultaneously explicit.

2 / 3

Trigger Term Quality

Includes natural terms users would say ('lint', 'format', 'clippy checks') but misses common variations such as 'fmt', 'analyze', and the dart/rust sub-commands.

2 / 3

Distinctiveness Conflict Risk

Scoping to the named 'flutter_rust_bridge' project gives a clear niche with distinct triggers, making it unlikely to fire for unrelated lint/format skills.

3 / 3

Total

9

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fzyzcjy/flutter_rust_bridge
Reviewed

Table of Contents

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.