CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frb-fix-ci

Use when CI fails in flutter_rust_bridge - before deep investigation

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

71%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 content is highly actionable and workflow-driven, with concrete commands, validation checkpoints, and repo-specific knowledge that Claude could not infer. Its main weaknesses are redundancy (core rules restated in several sections) and a monolithic single-file layout where reference files would reduce context load.

Suggestions

Consolidate the repeated rules — hand-edit prohibition, cargokit submodule patching, and precommit-generate escalation each appear in 2-3 sections; state each once and cross-reference it.

Move the dependency graph, the escalation protocol, and the per-failure-type deep dives into files under references/ and keep SKILL.md as a triage overview with well-signaled one-level-deep links.

Gate the destructive "git reset --hard HEAD && git clean -fdx" with an explicit check that the remote workspace holds no uncommitted work worth preserving.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious repo-specific knowledge rather than concepts Claude already knows, but key rules are repeated across sections — "do not hand-edit generated files" appears about five times, and cargokit patching, precommit-generate escalation, and Apple-scaffold handling each appear two to three times in near-verbatim form. Mostly efficient but clearly could be tightened, matching anchor 3.

3 / 5

Actionability

Commands are copy-paste ready and cover the common cases: "gh run rerun --failed", "./frb_internal lint --fix" with its exact sub-command breakdown, "git reset --hard HEAD && git clean -fdx", and reproducing the exact CI command ("./frb_internal test-dart --package frb_example/pure_dart"). Decision thresholds are also concrete ("after two similar package-level sync fixes, the burden of proof switches").

5 / 5

Workflow Clarity

The numbered Triage Order gives a clear sequence with validation checkpoints (read latest run, compare against total_count, match toolchain versions, clean workspace before reproduction) and feedback loops (rerun-then-flaky check, escalation after two similar syncs). Anchor 5 is missed by a minor gap: the destructive "git reset --hard HEAD && git clean -fdx" is recommended without an explicit pre-check for uncommitted or valuable work in the remote workspace.

4 / 5

Progressive Disclosure

Section headers are clear, but no bundle files exist — the mermaid dependency graph, the escalation protocol, and the per-failure-type deep dives are all inlined in a ~320-line SKILL.md. This matches anchor 3: some structure, but content that would fit better in separate reference files is inline.

3 / 5

Total

15

/

20

Passed

Description

40%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 has a clear, distinctive trigger niche but omits the skill's capabilities entirely — it says when to use the skill without saying what it does. Adding one sentence of concrete actions (rerun flaky jobs, apply CI diffs, run lint --fix) would lift both completeness and specificity significantly.

Suggestions

Add a 'what' clause listing concrete capabilities, e.g. "Triage and fix flutter_rust_bridge CI failures with lazy fixes: rerun failed jobs, apply CI-provided diffs, regenerate outputs, run lint --fix."

State the actions explicitly so specificity rises from domain-only to 3-4 concrete actions.

Include common trigger variations such as "build failing" or "CI red" alongside "CI fails".

DimensionReasoningScore

Specificity

The description names the domain ("CI fails in flutter_rust_bridge") but states no concrete actions — there is no verb describing what the skill actually does (rerun, apply diffs, fix lints). It is above anchor 1 (which lacks even a domain) but below anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

Only the 'when' is present ("Use when CI fails in flutter_rust_bridge"); the 'what' — what the skill does — is entirely absent. This exactly matches anchor 2 ('only when is present without what') and is below anchor 4, which requires both.

2 / 5

Trigger Term Quality

"CI fails" and "flutter_rust_bridge" are natural phrases a user would say, but common variations like "build failing", "tests failing", or "red pipeline" are missing, matching anchor 3 (some relevant keywords, missing common variations).

3 / 5

Distinctiveness Conflict Risk

"CI fails in flutter_rust_bridge" carves a clear niche and "before deep investigation" hints at ordering versus frb-debugging, but several sibling skills (frb-debugging, frb-fix-merge-conflict) cover adjacent CI-failure territory, leaving minor overlap risk per anchor 4 rather than the minimal risk of anchor 5.

4 / 5

Total

11

/

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