CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

81%

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

78%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, self-contained instruction skill: lean, actionable, with a clearly sequenced regression workflow and effective anti-pattern guidance. The only meaningful gap is the absence of an explicit post-fix validation step confirming the repair turns CI green before the PR is opened.

DimensionReasoningScore

Conciseness

Lean, imperative prose with no concept explanations Claude already knows ('Check the latest relevant run, not stale status', 'Do not chase downstream job failures...'). Minor trim opportunities: the opening sentence restates the frontmatter description and 'A default-branch failure is often a regression' is a mild explanatory aside.

4 / 5

Actionability

Provides executable git commands ('git log --oneline --decorate <green-sha>..<red-sha>'), named jobs to prioritize ('Generate', 'Integrate', 'Generate Internal'), and the concrete reproduction command ('./frb_internal ...'). Falls short of fully copy-paste ready because some steps are directional ('Study what changed', 'Fix the source of the regression').

4 / 5

Workflow Clarity

The Regression Workflow is a clearly numbered 1-6 sequence with a conditional checkpoint ('If the range is broad or the culprit is unclear, bisect') and a reproduction-verification question ('Does the failure reproduce at the red commit but not at the green baseline'). Missing one explicit validation step: confirming CI is green again after the fix before preparing the PR.

4 / 5

Progressive Disclosure

Self-contained skill with no bundle files; every section is appropriately sized and nothing that belongs in a separate file is inlined. References to peer skills ('frb-fix-ci', 'tom-ci', 'frb-prepare-pr') are clearly signaled by name, and the section organization (Choose a Path, Regression Workflow, What Not To Do, PR Expectations) makes navigation trivial.

5 / 5

Total

17

/

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 distinct, well-targeted description with explicit trigger conditions and a clear niche. Its main weakness is that the 'what' side is thin — the user learns when to invoke it but little about what the skill will actually do.

Suggestions

State one or two concrete actions the skill performs, e.g. 'Compares the nearest green default-branch run to the failing commit and bisects the range to fix the regression at its source.'

Add common trigger synonyms such as 'broken build', 'CI red on main', or the abbreviation 'frb' to widen natural-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('flutter_rust_bridge CI fails on the default branch/main/master') and one concrete capability ('to distinguish ordinary CI repair from a regression'), but does not enumerate the skill's actual actions such as comparing green/red baselines or bisecting, so coverage is not comprehensive.

3 / 5

Completeness

The 'when' is explicit and specific ('Use when flutter_rust_bridge CI fails on the default branch/main/master'), and a 'what' is present ('to distinguish ordinary CI repair from a regression'), but the what is a single distinguishing clause rather than a concrete statement of the skill's actions.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('CI fails', 'default branch', 'main', 'master', 'regression', 'green'), but misses common synonyms like 'broken build', 'CI red on main', or the 'frb' abbreviation.

4 / 5

Distinctiveness Conflict Risk

Clear niche: FRB default-branch CI failures with explicit regression-vs-ordinary-repair disambiguation, which minimizes overlap with generic CI-repair skills.

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-fix-main-ci/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.