CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-pr-chain-split

Use when an FRB PR contains independently landable work that should be extracted into predecessor PRs and connected as a GitHub PR chain without wasting full automatic CI.

73

Quality

90%

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

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.

A well-structured, highly actionable skill body that sequenced a complex PR-chain workflow with concrete commands, explicit validation checkpoints, and clean cross-skill references. Only minor conciseness trim opportunities around mechanism explanations.

DimensionReasoningScore

Conciseness

Largely lean and imperative-driven, assuming Claude's competence (no explanation of FRB, PR chains, or gh), with a few mechanism-explaining clauses such as the labeled-run concurrency description that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready, executable commands throughout (gh stack init/submit/link, gh pr edit --add-label, ./frb_internal plan-ci, git merge-base --is-ancestor) covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced seven-section process with explicit validation before destructive operations (compare tree/delta before pushing, --force-with-lease only after checks) and a dedicated completion-checks checklist.

5 / 5

Progressive Disclosure

Well-organized into focused sections with one-level-deep, clearly signaled pointers to sibling skills (frb-prepare-pr, frb-ci-filter); no nested references and no monolithic wall of text.

5 / 5

Total

19

/

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 strong, specific description that explicitly covers both what the skill does and when to invoke it, using third-person imperative voice and domain-natural trigger terms. Minor room for more enumerated action detail and synonym coverage.

DimensionReasoningScore

Specificity

Names the FRB PR domain and several concrete actions ('extracted into predecessor PRs', 'connected as a GitHub PR chain', 'without wasting full automatic CI'), but the actions are stated at a workflow-purpose level rather than enumerated comprehensively.

4 / 5

Completeness

Explicitly answers what ('extracted into predecessor PRs and connected as a GitHub PR chain without wasting full automatic CI') and when ('Use when an FRB PR contains independently landable work') with a concrete trigger clause.

5 / 5

Trigger Term Quality

Includes natural domain terms a reviewer would say ('FRB PR', 'predecessor PRs', 'GitHub PR chain', 'full automatic CI') with good coverage, though a few synonymous phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (FRB PR chain splitting with CI conservation) with distinct triggers and minimal overlap with other skills.

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.