CtrlK
BlogDocsLog inGet started
Tessl Logo

custom-rebase

Rebases Fusion Framework feature branches onto main and handles monorepo conflict traps. USE FOR: rebase this branch, refresh branch from main, fix pnpm-lock.yaml conflicts, resolve Version Packages conflicts, generate a rebase risk report. DO NOT USE FOR: dependency PR review, branch cleanup unrelated to rebase, or destructive reset without explicit approval.

90

1.50x
Quality

96%

Does it follow best practices?

Impact

95%

1.50x

Average score across 2 eval scenarios

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.

The body is a tightly structured, executable rebase runbook with explicit safety gates, a verification checkpoint before force-push, and a correctly referenced report-generation script. The only minor weakness is the density of the Changesets v3 rationale in step 4, which slightly trims conciseness.

Suggestions

Tighten step 4's Changesets v3 prose: lead with the one-command action (create one consolidated patch changeset for main-bumped packages) and move the historical pre.json.initialVersions rationale into a one-line aside.

Consider showing the exact consolidated-changeset file shape (a fenced .changeset/*.md example) so the manual changeset creation is copy-paste-ready like the other steps.

DimensionReasoningScore

Conciseness

Mostly lean command blocks and tables with no basic-concept padding, but step 4's Changesets v3 prose is dense and could be tightened slightly while preserving the version-specific rationale.

4 / 5

Actionability

Fully executable, copy-paste-ready bash commands throughout, a concrete conflict-resolution table with exact git/pnpm commands, and a real script invocation path covering the common cases.

5 / 5

Workflow Clarity

Clear Prepare→Rebase→Resolve→pre.json→Verify→Report sequence with explicit gates, a remote-diff plus --force-with-lease --dry-run validation checkpoint, and troubleshooting feedback loops, so validation is present despite the destructive nature.

5 / 5

Progressive Disclosure

Well-organized sections (When To Use, Required Gates, Workflow, Troubleshooting, Expected Output, Related Skills) with the one bundle script referenced one level deep via a clear command path and confirmed to exist at scripts/generate-rebase-report.cjs.

5 / 5

Total

19

/

20

Passed

Description

100%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 is exemplary: it states concrete capabilities, provides natural trigger phrases via an explicit USE FOR list, and draws a clear DO NOT USE FOR boundary. Every dimension hits the top anchor with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (rebase onto main, handle monorepo conflict traps, fix pnpm-lock.yaml conflicts, resolve Version Packages conflicts, generate a rebase risk report), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both WHAT ('Rebases Fusion Framework feature branches onto main and handles monorepo conflict traps') and WHEN ('USE FOR: ...') with concrete trigger phrases, plus a DO NOT USE FOR boundary.

5 / 5

Trigger Term Quality

Includes natural user phrases ('rebase this branch', 'refresh branch from main') plus file-extension terms (pnpm-lock.yaml), giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Clear Fusion Framework rebase niche with distinct triggers and an explicit 'DO NOT USE FOR' boundary separating it from dependency PR review and branch cleanup.

5 / 5

Total

20

/

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
equinor/fusion-framework
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.