CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-develop-feature

Use when fixing bugs, adding regression tests, adding new features, when compilation is slow, or when learning twin test naming conventions in flutter_rust_bridge

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a well-structured, highly actionable workflow with explicit validation checkpoints and feedback loops. It is held back only by mild repetition and the lack of any external bundle split despite exceeding ~200 lines.

Suggestions

Dedupe the "Check your user-level remote-testing rules" note into a single callout instead of repeating it after each codegen step.

Extract the Architecture and Common Mistakes sections into reference files under references/ to reduce SKILL.md length and improve progressive disclosure.

Consolidate the repeated dart_minimal→pure_dart gate messaging so it is stated once prominently and only cross-referenced elsewhere.

DimensionReasoningScore

Conciseness

The body is mostly tight tables and concrete commands with no basic-concept padding, but the remote-testing note is repeated three times and the dart_minimal→pure_dart gate is restated across several sections, offering minor trimming.

4 / 5

Actionability

Concrete file paths (e.g. frb_example/pure_dart/rust/src/api/my_feature.rs) and copy-paste commands (e.g. ./frb_internal test-dart-native --package frb_example/pure_dart) plus the TwinNormal suffix table make the guidance fully executable across the common cases.

5 / 5

Workflow Clarity

Phases are explicitly sequenced with a graphviz workflow diagram, a Final Placement Gate checklist that validates readiness ("If any of these checks fail, return to Phase 2"), and feedback loops (iterate until pass, debug→all tests pass).

5 / 5

Progressive Disclosure

No bundle files exist, so all content is inline, but it is well-sectioned with one-level-deep, clearly signaled pointers (Related Skills, the contributing overview doc); a few inline blocks (architecture, common mistakes) could be split out.

4 / 5

Total

18

/

20

Passed

Description

75%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 a strong, mostly concrete trigger list with an explicit Use-when clause and a clear domain niche. Its main weakness is folding the "what" into the "when" rather than naming the skill's distinctive technical workflow actions.

DimensionReasoningScore

Specificity

Lists several concrete actions scoped to flutter_rust_bridge ("fixing bugs, adding regression tests, adding new features, ... learning twin test naming conventions"), but states trigger conditions rather than the underlying technical workflow actions, leaving minor gaps.

4 / 5

Completeness

An explicit "Use when ..." clause answers "when" and the listed activities answer "what", but the "what" is folded into the trigger list rather than stated as a distinct capability, so it is not maximally explicit.

4 / 5

Trigger Term Quality

Natural developer phrases like "when compilation is slow", "adding regression tests", and "twin test naming conventions" give good keyword coverage, though a few synonyms or file/extension variants are missing.

4 / 5

Distinctiveness Conflict Risk

The flutter_rust_bridge scope plus "twin test naming conventions" carve a clear niche, but generic "fixing bugs / adding new features" triggers carry minor overlap risk with the related frb-* skills.

4 / 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.