CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frb-pr-review

Review a flutter_rust_bridge PR before treating it as ready, including subagent checks for correctness and test weakening.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/frb-pr-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, well-sequenced review process with concrete subagent briefs, mandated finding formats, and an explicit stop-condition gate. Its weaknesses are small: an unexplained empty heading, no concrete commands for fetching diffs or CI status, and no explicit fix-then-re-review loop.

Suggestions

Remove the empty '# 1 Human SoT' heading (and renumber) — it is organizational noise with no content.

Add an explicit fix-then-re-review step to the Stop Condition so the feedback loop closes (e.g., 'after fixing, re-run both subagent reviews before declaring readiness').

Include one concrete command for obtaining the PR diff and CI status (e.g., `gh pr diff` / `gh pr checks`) to make the subagent briefs copy-paste executable.

DimensionReasoningScore

Conciseness

The ~36-line body is lean and assumes Claude's competence — it never explains what a PR or CI is, and every bullet carries instruction. Minor trims remain: the empty '# 1 Human SoT' heading is pure noise, and the opening sentence partially restates the frontmatter description, which keeps it just below anchor 5 ('every token earns its place').

4 / 5

Actionability

Guidance is concrete and executable for a process skill: exact subagent briefs ('inspect the PR diff against the PR base', 'Focus on real behavior bugs, stale generated output, incorrect CI workarounds...'), required finding format ('file paths, line numbers, impact, and suggested fix'), and deliverable contents. It stays below anchor 5 because no actual commands are given (e.g., how to obtain the PR diff or check CI status), a minor gap for a copy-paste-ready workflow.

4 / 5

Workflow Clarity

The sequence is clear — two parallel subagent reviews, then a conclusion with mandated contents — and the Stop Condition ('Do not call the PR ready until...') is an explicit validation gate with a fix directive ('restore unjustified weakening and fix the underlying failure'). It falls short of anchor 5 because there is no explicit re-review iteration after fixes and no concrete step for verifying CI status.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the under-50-line body is organized into a Review Gate and a Stop Condition with no nested references, which would normally merit a 5 under the simple-skill note. The stray '# 1 Human SoT' heading with no content is a minor organization gap, matching anchor 4.

4 / 5

Total

16

/

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.

A concise, third-person description with a clearly identifiable niche and decent natural trigger terms. Its main weakness is that the capability list is compressed to a generic 'review' plus two named checks, and the 'when' is a single narrow phrase rather than concrete trigger conditions.

Suggestions

Enumerate 2-3 more concrete review actions in the description itself (e.g., 'check for stale generated output, incorrect CI workarounds, and coverage-only changes') to lift specificity.

Add an explicit 'Use when...' clause with concrete triggers such as 'after CI-driven fixes, Flutter upgrades, generated drift, or broad merge conflict resolution' to strengthen completeness.

Include common trigger variations users would naturally say — 'pull request', 'CI green', 'merge readiness' — to broaden trigger term coverage.

DimensionReasoningScore

Specificity

"Review a flutter_rust_bridge PR" names the domain clearly and the description does cite concrete mechanisms ("subagent checks for correctness and test weakening"), but the overall action is a generic 'review' with only 1-2 concrete sub-actions and no coverage of what the review examines (e.g., stale generated output, CI workarounds, coverage drift). This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') rather than anchor 4, which expects several specific listed actions.

3 / 5

Completeness

The 'what' is clear (review a flutter_rust_bridge PR with correctness and test-weakening subagent checks) and a 'when' is explicitly stated ("before treating it as ready"), so this is not the anchor-3 case of a missing/only-implied when. However, the when is narrow — the richer triggers (CI-driven fixes, Flutter upgrades, generated drift) live only in the body — so it does not reach anchor 5's concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural terms a user would say are present: "flutter_rust_bridge", "PR", "review", "ready", "correctness", "test weakening". This is comparable to anchor 4 ('good keyword coverage; a few natural terms missing') — common variations like "pull request", "CI", or "merge" are absent, keeping it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"flutter_rust_bridge PR" is a clear niche with distinct triggers; the highly specific project name makes it very unlikely to fire for the wrong skill, matching anchor 5. It is well above anchor 4 ('mostly distinct; minor overlap risk') because the domain qualifier is unambiguous.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fzyzcjy/flutter_rust_bridge

Path

.claude/skills/frb-pr-review/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.