CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-pr-review

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

64

Quality

75%

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-pr-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is concise, well-structured, and provides a clear review workflow with explicit validation checkpoints and a stop condition. The only minor gap is the lack of concrete mechanics for spawning subagents.

Suggestions

Add a brief concrete example of how to spawn the review subagents (e.g. the agent tool invocation or prompt template) to lift actionability toward 5.

DimensionReasoningScore

Conciseness

Lean prose with no over-explanation of concepts Claude already knows; every section earns its place and assumes Claude's competence.

5 / 5

Actionability

Concrete guidance with specific focus lists and required finding fields, plus pointers to sdev-pass-test; minor gaps in the mechanical details of how to spawn subagents.

4 / 5

Workflow Clarity

Clear sequenced gate with two review paths and an explicit stop-condition checklist (no unresolved findings, no unjustified weakening, CI green) acting as validation checkpoints.

5 / 5

Progressive Disclosure

A focused, well-sectioned single-purpose skill under 50 lines with clear navigation; external skill references are one level deep and clearly signaled.

5 / 5

Total

19

/

20

Passed

Description

57%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 specific to a clear niche and names concrete review actions, but it lacks an explicit 'Use when...' trigger clause and natural trigger phrasings, which caps completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when treating a flutter_rust_bridge PR as ready, especially after CI-driven fixes or generated drift.'

Include natural phrasings a user would say, such as 'sign off on a PR' or 'check a PR is ready to merge'.

Expand the action list slightly (e.g. mention checking generated drift, CI workarounds) to lift specificity toward 4-5.

DimensionReasoningScore

Specificity

Names the domain ('flutter_rust_bridge PR') and two concrete actions ('subagent checks for correctness and test weakening'), but coverage is not comprehensive enough for a 4.

3 / 5

Completeness

The 'what' is clear but there is no explicit 'Use when...' trigger clause; the 'when' is only weakly implied by 'before treating it as ready', which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like 'PR', 'review', 'correctness', and 'test weakening' appear, but common natural phrasings users would say (e.g. 'is this PR ready', 'sign off on this PR') are missing.

3 / 5

Distinctiveness Conflict Risk

Scoped to a single niche ('flutter_rust_bridge PR') with clear distinct triggers and minimal conflict risk with other skills.

5 / 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.

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.