CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-issue-to-green-pr

Use when implementing a GitHub issue, bug fix, or feature in flutter_rust_bridge end-to-end: develop the change, add regression coverage, prepare and open a PR, and use the user's tom-ci skill to monitor CI until the PR is ready.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-orchestrated, clearly sequenced workflow with strong validation gates and progressive disclosure through subskill delegation. The main weakness is redundancy across sections and execution detail being delegated rather than supplied inline.

Suggestions

Consolidate the tom-ci waiting guidance, which is restated in sections 1, 7, and the Automation Rules, into one canonical statement and reference it from the other phases.

State the Final Placement Gate (dart_minimal → pure_dart migration) once and reference it from the PR-preparation step instead of repeating the check in both section 4 and section 5.

Add one concrete copy-paste starting point for the reproduction phase — e.g. a skeleton tools/manual_tests/NAME.md or an example intentional-red-CI ci_filter invocation — so that phase has an executable anchor rather than only delegating to subskills.

DimensionReasoningScore

Conciseness

The body is lean and delegates detail to subskills rather than padding, but the tom-ci waiting guidance is restated across sections 1, 7, and Automation Rules, and the dart_minimal→pure_dart migration check is repeated in sections 4 and 5, so it sits just below the lean 5 anchor.

4 / 5

Actionability

Concrete guidance is present — specific paths (tools/manual_tests/NAME.md, frb_example/pure_dart), PR title templates, and `git status --short` — but most executable detail is delegated to subskills rather than given inline, leaving minor gaps versus copy-paste-ready instruction.

4 / 5

Workflow Clarity

An 8-step sequence with explicit validation gates (reproduction-before-fix, Final Placement Gate, review gate), a CI feedback loop (fail → diagnose → fix → push → re-monitor), and a stop-conditions checklist, matching the 5 anchor; the destructive/batch cap does not apply because validation is present.

5 / 5

Progressive Disclosure

The skill is a clear overview that points to one-level-deep subskills, each paired with the phase when it should be read, and explicitly avoids duplicating their instructions — textbook progressive disclosure even though no bundle files exist.

5 / 5

Total

18

/

20

Passed

Description

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

A strong, specific description that clearly states both the workflow it performs and the trigger conditions for use, scoped to a distinct niche. Trigger-term coverage is good but could add a few more natural synonyms to reach the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "develop the change, add regression coverage, prepare and open a PR, and use the user's tom-ci skill to monitor CI" — giving comprehensive coverage of the end-to-end workflow, matching the 5 anchor.

5 / 5

Completeness

Explicitly answers both what (develop → regression coverage → PR → CI monitoring) and when ("Use when implementing a GitHub issue, bug fix, or feature in flutter_rust_bridge end-to-end") with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural terms a user would say are present ("GitHub issue", "bug fix", "feature", "open a PR", "monitor CI") with some synonym variation, but a few common phrasings like "handle end-to-end" or "make a PR" are absent, sitting just below the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped to a flutter_rust_bridge end-to-end issue-to-PR workflow with CI monitoring via tom-ci, a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

19

/

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.