CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-fix-main-ci

Use when flutter_rust_bridge CI fails on the default branch/main/master, especially to distinguish ordinary CI repair from a regression introduced after a previously green default-branch commit.

70

Quality

85%

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

82%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, concise instruction skill with concrete commands and a clear two-path decision model. Its main gaps are placeholder reproduction commands and implied rather than explicit validate-fix-retry loops.

Suggestions

Make the bisect/reproduction validation loop explicit (e.g., 'reproduce at red, confirm green baseline passes, then iterate') to push workflow_clarity to 5.

Replace placeholder SHAs in the git examples with a concrete worked example or a note on how to obtain green/red SHAs from the workflow run.

Reference sibling skills with their skill path or a short hint of what they cover so navigation is unambiguous.

DimensionReasoningScore

Conciseness

Lean and efficient; it delegates detail to sibling skills (frb-fix-ci, tom-ci, frb-prepare-pr) and avoids restating concepts Claude already knows, with every section earning its place.

5 / 5

Actionability

Provides concrete commands (git log/diff --stat), explicit classification lists, and specific PR expectations, but reproduction examples rely on placeholders (<green-sha>..<red-sha>) leaving minor gaps.

4 / 5

Workflow Clarity

The Regression Workflow is a clear numbered sequence with a bisect fallback and a validation checkpoint (reproduce at red but not green, question 4), though the validate->fix->retry loop is implied rather than fully explicit.

4 / 5

Progressive Disclosure

Well-organized into distinct sections (Choose a Path, Regression Workflow, What Not To Do, PR Expectations) with signaled sibling-skill references and no nested bundles, but the body slightly exceeds the simple-skill 50-line threshold and references skills by name without paths.

4 / 5

Total

17

/

20

Passed

Description

87%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 tightly scoped, well-triggered description that clearly states both what the skill does and when to invoke it. It is distinctive and uses natural trigger language with only minor synonym gaps.

DimensionReasoningScore

Specificity

Names the domain (flutter_rust_bridge CI on the default branch) and concrete actions — 'ordinary CI repair' vs 'a regression introduced after a previously green default-branch commit' — matching the 'lists several specific actions; minor gaps' anchor rather than the less comprehensive 3.

4 / 5

Completeness

Explicitly answers both 'what' (distinguish ordinary CI repair from a post-green regression) and 'when' ('Use when flutter_rust_bridge CI fails on the default branch/main/master') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases a user would say ('CI fails on the default branch/main/master', 'regression') with good coverage, though it leans on the project name rather than enumerating synonyms like 'build broke on main'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — default-branch FRB CI failure disambiguation — and is clearly separable from the broader frb-fix-ci skill, with minimal conflict risk.

5 / 5

Total

18

/

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.