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

64

Quality

76%

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-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is efficient, actionable, and well-structured, giving copy-paste-ready commands and a clear CI workflow with checkpoints. It would reach the top tier by replacing placeholder arguments with at least one fully resolved example command.

Suggestions

Resolve at least one placeholder (e.g. show a concrete `--package frb_example/dart_minimal` invocation) so the Quick Reference has a fully concrete worked example.

Tighten the CI Discipline prose (e.g. 'CI is slow and often queues for a long time') into a single directive sentence to improve token efficiency.

Add an explicit validation checkpoint for the push step, such as confirming the PR check status command, to make the workflow sequence fully checklisted.

DimensionReasoningScore

Conciseness

The body is lean with a direct command table and only the necessary explanation (e.g. the flaky-web-test note and concrete setup commands); a small amount of prose in CI Discipline could be trimmed, keeping it just short of fully lean.

4 / 5

Actionability

It provides concrete, executable commands throughout (./frb_internal test-*, rustup target add, curl wasm-pack) that are mostly copy-paste ready; minor gaps come from unresolved placeholders like <path> and <name> rather than fully concrete examples.

4 / 5

Workflow Clarity

The CI Discipline section lays out a clear sequence (run local tests scaled to blast radius, push, monitor GitHub Actions to terminal state, inspect failures and fix or report flaky, run the review gate) with explicit checkpoints and a feedback loop, with only minor validation gaps.

4 / 5

Progressive Disclosure

No bundle files exist, and the skill is a short, well-organized single-purpose document under ~65 lines with clear section headers and inline cross-skill references (frb-dev-env, frb-pr-review), satisfying the simple-skill exception for well-organized content.

5 / 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 is concise, third-person-free in voice, and includes a clear 'Use when' trigger with specific scenarios. The 'what' side is slightly thin and could enumerate more concrete actions to reach the top anchor.

DimensionReasoningScore

Specificity

Names the domain ('run tests locally in flutter_rust_bridge') and two concrete scenarios ('run tests', 'debugging test failures'), but lists only one to two actions rather than a comprehensive set, matching the anchor for naming the domain with limited actions.

3 / 5

Completeness

It has an explicit 'Use when' clause covering when to invoke it and an implicit-but-clear 'what' (run tests locally in flutter_rust_bridge); the 'when' is concrete while the 'what' is a bit thin, fitting the anchor where both are present but one could be more specific.

4 / 5

Trigger Term Quality

Includes natural phrases users would say such as 'run tests locally', 'debugging test failures', and 'before pushing', with good coverage; a few synonyms or common variants are missing, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Tied to a specific named project (flutter_rust_bridge) with distinct triggers, giving it a clear niche with minimal conflict risk against 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.