CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

71%

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

67%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.

A well-structured orchestration skill: concrete commands, clearly sequenced REQUIRED/optional steps, and explicit verification checkpoints for the integrate/cargokit edge cases. Its main costs are the duplicated step list (Workflow diagram vs. Quick Checklist) and the thin inline command for the most important step, code generation, which is fully delegated to another skill.

Suggestions

Drop either the Workflow ASCII diagram or the Quick Checklist — they cover the same steps; keep the checklist since it carries the REQUIRED/conditional labels.

Inline the actual code-generation command(s) (or a one-line 'run ./frb_internal ...' equivalent) instead of only 'Read frb-code-generation skill, run commands if needed'.

Move the cargokit-submodule and CI-filter prose details into frb-cargokit / frb-ci-filter and keep one-line pointers here.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific facts Claude cannot know (frb_internal commands, template paths, CI workflow names) and explains no general concepts. However, the Workflow ASCII diagram and the Quick Checklist enumerate the same steps twice, which is a clear tightening opportunity, matching anchor 3 ('could be tightened') rather than anchor 4.

3 / 5

Actionability

Gives copy-paste-ready commands with conditions ('./frb_internal lint --fix', './frb_internal precommit-integrate', './frb_internal sync-cargokit-copies') plus concrete paths like 'frb_codegen/assets/integration_template/'. Not 5 because the primary step — code generation — says only 'Read frb-code-generation skill, run commands if needed' with no command inline.

4 / 5

Workflow Clarity

A numbered checklist with REQUIRED/conditional labels, a stated core principle (Generate → Lint → Commit → PR), and explicit checkpoints (confirm the template is the change source, run the review gate before readiness, verify output-only diffs are intentional). Not 5 because fail → fix → re-validate loops are delegated to other skills rather than shown inline.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body is well-sectioned with pointers to sibling skills that are one level deep and clearly signaled, including a Related Skills section with one-line descriptions. Not 5 because some prose detail (the cargokit-submodule and CI-filter paragraphs) duplicates content that belongs in the referenced skills.

4 / 5

Total

15

/

20

Passed

Description

61%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 ('Use when about to create a PR or push changes in flutter_rust_bridge') and good distinctiveness from the project scoping, but it undersells what the skill does — code generation, linting, reproduction reports, and a review gate are all core per the body, none of which appear. Adding a short 'what' clause covering those actions would lift both completeness and specificity.

Suggestions

Add a leading 'what' clause enumerating the skill's actions, e.g. 'Runs code generation, lint --fix, and the PR review gate, and attaches reproduction reports for bug fixes.'

Include a few more natural trigger variations such as 'pull request' or 'open a PR' to broaden keyword coverage.

Mention lint/test readiness in the description so it does not read as codegen-only.

DimensionReasoningScore

Specificity

Names the domain ('create a PR or push changes in flutter_rust_bridge') and one concrete purpose ('ensure code generation is up to date'), matching anchor 3. Not 4 because the description lists none of the other concrete actions the body shows are central (lint --fix, reproduction reports, review gate); not 2 because the named action is specific rather than generic.

3 / 5

Completeness

The 'when' is explicit ('Use when about to create a PR or push changes'), but the 'what' is only a purpose clause — 'to ensure code generation is up to date' — and omits what the skill actually does. It sits between anchor 3 and anchor 4: the when is stronger than anchor 3 implies, but the what is thinner than anchor 4 requires.

3 / 5

Trigger Term Quality

'create a PR', 'push changes', 'flutter_rust_bridge', and 'code generation' are natural phrases a user would say, giving good keyword coverage. Not 5 because common variations like 'pull request' or 'open a PR' are missing.

4 / 5

Distinctiveness Conflict Risk

Scoping to the named project 'flutter_rust_bridge' gives a clear niche with minimal conflict risk. Not 5 because the trigger verbs ('create a PR', 'push changes') are generic PR-workflow phrases that could fire for other repos' PR skills.

4 / 5

Total

14

/

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-prepare-pr/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.