CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frb-test

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

Quality

75%

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

86%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 excellent operational reference: fully executable commands for every change type, concrete environment setup, and genuinely non-obvious project knowledge (flaky web tests, Docker sandbox detection, CI queue discipline). The only deductions are time-sensitive pinned versions outside a legacy section and a workflow that is implied by section order rather than explicitly sequenced.

DimensionReasoningScore

Conciseness

The body is lean — a command table plus terse, non-obvious operational notes (Docker --no-sandbox, flaky web tests) with no explanations of concepts Claude already knows. Time-sensitive version pins ("nightly-2025-02-01") and the wasm-pack curl installer are not placed in a legacy/deprecated section, which keeps it from the top anchor.

4 / 5

Actionability

Every row of the quick-reference table is a copy-paste-ready `./frb_internal ...` command covering all common change types, and the web-test requirements give exact rustup, rust-src, wasm-pack, and browser setup commands with the Docker-specific flag — fully executable with no gaps.

5 / 5

Workflow Clarity

A workable sequence is present (choose tests by blast radius → run and understand locally → push → monitor CI to terminal state → fix or report, then the frb-pr-review gate) with real feedback loops (rerun flaky web tests, inspect failing CI job logs). It falls short of the top anchor because the process is spread across prose sections rather than an explicit ordered sequence with checkpoints at each step.

4 / 5

Progressive Disclosure

The body is a single-topic, well-organized quick reference (~60 lines) with clear section headers, and its only references — `frb-dev-env` and `frb-pr-review` — are sibling skills, clearly signaled in place; no bundle files exist to descend into, so all content is appropriately placed at this level.

5 / 5

Total

18

/

20

Passed

Description

52%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 has a strong, explicit trigger clause with natural phrasing and a well-anchored niche, but it omits any statement of what the skill actually provides, which caps completeness and overall utility. Adding a one-line capability summary (e.g., mapping change types to specific local test commands) and broader trigger synonyms would lift it substantially.

Suggestions

Lead with a 'what' clause before the trigger, e.g. "Maps FRB change types (Rust, Dart, Flutter, web) to specific local test commands. Use when needing to run tests locally in flutter_rust_bridge or when debugging test failures before pushing."

Add common trigger variations users would naturally say — "CI", "flaky tests", "unit tests", "Rust packages", "Dart example" — to improve trigger-term coverage from good to comprehensive.

Clarify the relationship to CI in the description (local tests as the fast feedback loop before relying on slow CI), so it is distinguishable from a generic CI-monitoring skill.

DimensionReasoningScore

Specificity

"run tests locally in flutter_rust_bridge" and "debugging test failures" name the domain plus 1-2 concrete actions, matching the anchor for partial action coverage; it does not list several actions (not 4) and is more than minimal/generic (not 2).

3 / 5

Completeness

The description is an explicit, specific 'when' ("Use when needing to run tests locally... or when debugging test failures before pushing") but never states what the skill does — the command mapping, web-test setup, and CI discipline are entirely invisible. This matches the anchor where only 'when' is present without 'what', and it is not the anchor-3 case, which is the reverse (clear what, weak when).

2 / 5

Trigger Term Quality

Natural phrases like "run tests", "test failures", and "before pushing" plus the domain keyword give good keyword coverage, but common variations users would say ("CI", "flaky", "unit tests", "Dart", "Rust") are missing, so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"flutter_rust_bridge" anchors a clear niche with distinct triggers, but "debugging test failures before pushing" is generic enough to overlap with general test-running or CI/PR-review skills in other repositories, giving minor overlap risk with closely related skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fzyzcjy/flutter_rust_bridge

Path

.claude/skills/frb-test/SKILL.md

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.