CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-prepare-pr

Use when about to create a PR or push changes in flutter_rust_bridge to ensure code generation is up to date

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-prepare-pr/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 a well-structured orchestration skill that leans correctly on sibling skills for detail, with concrete commands and a clear sequenced workflow; its main weaknesses are minor diagram/checklist redundancy and validation that relies on CI rather than explicit local feedback loops.

DimensionReasoningScore

Conciseness

The body is lean and delegates detail to sibling skills rather than explaining known concepts, though the ASCII workflow diagram and the Quick Checklist duplicate the same step sequence.

4 / 5

Actionability

Concrete commands and paths are provided (./frb_internal lint --fix, precommit-integrate, sync-cargokit-copies, integration_template path), but the actual generation commands are deferred to other skills rather than being copy-paste ready here.

4 / 5

Workflow Clarity

An explicit 8-step workflow and a 10-item checklist with REQUIRED/Optional markers give a clear sequence, though validation is largely deferred to CI rather than expressed as a local validate-fix-retry loop.

4 / 5

Progressive Disclosure

Well-organized sections (Overview, Workflow, Quick Checklist, What CI Will Do, Related Skills) with clearly signaled one-level-deep references to sibling skills and no nested/ buried references.

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, uses an explicit 'Use when' trigger, and is highly distinct, but its 'what' statement is narrow — it advertises only codegen freshness while the skill also covers lint, tests, review gates, and bug-fix reproduction reports.

Suggestions

Broaden the 'what' clause to mention the full readiness scope, e.g. '...to ensure code generation is up to date, lint passes, and the PR review gate has run'.

Add one or two trigger synonyms (e.g. 'open a PR', 'submit a PR') to improve natural-term coverage.

Consider noting the bug-fix reproduction-report requirement in the description so the trigger matches that scenario too.

DimensionReasoningScore

Specificity

Names the domain (flutter_rust_bridge PRs/pushes) and one concrete goal (ensure code generation is up to date), but only covers a single action rather than a comprehensive set.

3 / 5

Completeness

Both 'what' (ensure code generation is up to date) and 'when' (about to create a PR or push changes) are explicit, but the 'what' is narrow and omits lint, tests, and review-gate duties the skill actually performs.

4 / 5

Trigger Term Quality

Natural trigger phrases like 'create a PR', 'push changes', and 'flutter_rust_bridge' are present, though a few synonyms (e.g. 'open PR', 'submit PR') are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (PR readiness in the flutter_rust_bridge repo with a codegen-up-to-date trigger) with minimal overlap 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.