CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-fix-merge-conflict

Use when resolving merge or rebase conflicts in flutter_rust_bridge, especially conflicts involving generated files after master/main changed independently from a PR branch.

76

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, command-driven skill body with a well-sequenced workflow, explicit validation, and clear cross-skill navigation. It assumes Claude's intelligence and avoids both verbosity and basic-concept padding.

DimensionReasoningScore

Conciseness

The body is lean and operational, assuming Claude's competence (no explanations of what merge conflicts or flutter_rust_bridge are); framing such as "treated as a stale artifact from two independently valid histories" earns its place by conveying the needed mental model rather than padding.

3 / 3

Actionability

It provides concrete, copy-paste-ready commands throughout ("git diff --name-only --diff-filter=U", "./frb_internal precommit-generate", "git checkout --ours -- <generated-path>"), matching the fully-executable anchor.

3 / 3

Workflow Clarity

A clearly numbered sequence (steps 1-6) is paired with explicit validation commands ("git diff --check", "git status --short") and error-recovery hints ("Do not stop after the internal generator when CI errors mention missing methods"), satisfying the validation-checkpoint requirement.

3 / 3

Progressive Disclosure

Content is well-organized into clear sections with one-level-deep, clearly-signaled cross-skill references ("Read frb-code-generation", "read frb-fix-ci"); no bundle files are present or needed, and there is no nested-reference indirection.

3 / 3

Total

12

/

12

Passed

Description

90%

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 focused, well-constructed description with an explicit trigger and strong distinctiveness. Its only weakness is specificity: it names one primary action rather than enumerating multiple concrete capabilities.

Suggestions

Add one or two more concrete actions the skill performs (e.g. "classify unmerged files, regenerate stale generated outputs, validate the merged tree") to lift specificity toward the level-3 anchor.

DimensionReasoningScore

Specificity

It names a concrete domain and action ("resolving merge or rebase conflicts in flutter_rust_bridge" ... "conflicts involving generated files") but describes essentially one action rather than multiple distinct concrete actions, so it stops short of the level-3 anchor.

2 / 3

Completeness

Both "what" (resolving merge/rebase conflicts) and "when" are explicit via the "Use when resolving merge or rebase conflicts ..." trigger, with an added "especially" clause sharpening the trigger condition.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered: "merge or rebase conflicts", "generated files", "flutter_rust_bridge", and "PR branch" are phrasings a user would actually say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (flutter_rust_bridge merge/rebase conflicts on generated files after master/main divergence) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.