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 sdev-ci-waiter to monitor CI until the PR is ready.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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-structured orchestration skill with a clear multi-phase workflow, strong validation checkpoints, and excellent progressive disclosure through subskill delegation. Minor conciseness redundancy and deferred execution detail keep actionability and conciseness just below perfect.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive with no concept over-explanation, but sdev-ci-waiter usage is described both in step 1 and again in the Automation Rules section, a minor redundancy that could be tightened.	4 / 5
Actionability	Concrete specifics abound (PR title templates, tools/manual_tests/NAME.md, frb_example/pure_dart gate, 'Close #1234'), but much executable detail is intentionally deferred to subskills rather than given inline, leaving minor gaps.	4 / 5
Workflow Clarity	Eight numbered phases are clearly sequenced with explicit validation gates (reproduction gate, Final Placement Gate, review gate, stop conditions) and a CI failure feedback loop (diagnose -> fix -> commit -> push -> monitor).	5 / 5
Progressive Disclosure	The skill is itself an overview that delegates to one-level-deep subskills, phase-mapped ('Read these when entering the matching phase') and explicitly non-duplicative, giving easy navigation with no nested references.	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, well-scoped description that clearly states both what the skill does and when to use it, anchored to a distinct flutter_rust_bridge niche. The only gap is minor trigger-term breadth (PR not spelled out, a few synonyms missing).

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('develop the change, add regression coverage, prepare and open a PR, and use sdev-ci-waiter to monitor CI'), giving comprehensive end-to-end coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both halves: 'Use when implementing...' states when, and the action list ('develop... add regression coverage... prepare and open a PR... monitor CI') states what, with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural triggers 'GitHub issue, bug fix, or feature' plus 'PR' and 'CI' cover what users say, but 'PR' is not spelled out and variants like 'pull request' or 'tests' are missing, so it stops just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'flutter_rust_bridge end-to-end' niche and the 'sdev-ci-waiter' tool name carve a clear, distinct trigger space with minimal overlap risk against generic implementation skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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-issue-to-green-pr/SKILL.md
Commit: 8f2ab1b

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

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.