CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-test

Use when needing to run tests locally in flutter_rust_bridge, or when debugging test failures before pushing

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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 an efficient, highly actionable quick-reference with concrete commands and a clear CI-discipline workflow including checkpoints. Minor trims to prose and a slightly tighter section split would push conciseness and progressive disclosure to the top anchors.

Suggestions

Tighten the CI Discipline paragraph into bullets to remove prose padding and improve conciseness.

Consider splitting the Web Tests requirements block into a short reference list or keep it as-is but verify it stays under the simple-skill line for a higher progressive_disclosure score.

DimensionReasoningScore

Conciseness

The body is lean with a dense quick-reference table and no padding about concepts Claude already knows, but the CI Discipline prose could be trimmed slightly, keeping it just below the fully-lean anchor.

4 / 5

Actionability

Commands are fully executable and copy-paste ready ('./frb_internal test-rust-package --package frb_rust', rustup/curl install lines, '--no-sandbox' and '/.dockerenv' details) and cover the common change-type cases.

5 / 5

Workflow Clarity

A clear sequence is present (map change type to test, run locally, push, monitor CI to terminal state, run review gate) with explicit checkpoints like 'monitor GitHub Actions until terminal state' and the review gate; minor validation gaps remain.

4 / 5

Progressive Disclosure

The single self-contained file is well-organized into clear sections with no nested references and no content that obviously belongs in a separate file; at ~64 lines it sits just past the simple-skill threshold, so it lands at 4 rather than 5.

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 pairs an explicit 'Use when...' trigger with a specific named tool and concrete actions, giving it strong completeness and distinctiveness. Specificity is adequate but only lists a couple of actions.

Suggestions

Add one or two more concrete actions (e.g., 'verify a fix', 'run a single affected package') to lift specificity toward comprehensive coverage.

Include a natural synonym or file/term variation users might say (e.g., 'CI', 'unit tests') to round out trigger terms.

DimensionReasoningScore

Specificity

Names the domain (flutter_rust_bridge) and 1-2 concrete actions ('run tests locally', 'debugging test failures') but coverage is not comprehensive, matching the anchor for domain plus 1-2 actions.

3 / 5

Completeness

Both a 'what' (run tests locally / debug test failures in flutter_rust_bridge) and an explicit 'when' ('Use when needing to run tests locally... or when debugging test failures') are present, though the 'what' is slightly light.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ('run tests', 'debugging test failures', 'before pushing') plus the specific tool name, giving good keyword coverage with only minor synonyms missing.

4 / 5

Distinctiveness Conflict Risk

Naming the specific tool flutter_rust_bridge carves a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

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.