rebase

Rebase an OpenMeter branch onto another branch and handle repo-specific gotchas like sequential migrations, atlas.sum conflicts, Ent regeneration, and targeted verification.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-3

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

A tight, highly actionable rebase runbook with executable commands, a clearly sequenced workflow including a verification checkpoint, and well-organized single-file structure. It assumes Claude's competence and adds only repo-specific gotchas that Claude would not already know.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — it assumes Claude's knowledge (no explaining what git rebase or migrations are) and every section earns its place; the few prose lines like 'Why:' and 'In practice...' add genuine rationale rather than padding.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands throughout — 'make generate', 'atlas migrate --env local diff <migration-name>', 'atlas migrate --env local hash', 'direnv exec . atlas migrate ...', and a concrete test command — matching the 'fully executable' anchor.	3 / 3
Workflow Clarity	Multi-step rebase process is clearly sequenced (Before rebasing → Standard flow → conflict sub-flows → Verification) with an explicit validation checkpoint ('run the smallest relevant test slice') and error-recovery guidance for destructive migration rewriting.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single SKILL.md is well-organized into clear one-level sections (Before rebasing, Migration conflicts, atlas.sum conflicts, Ent, Verification) with no nested references, which earns 3 per the simple-skill scoring note.	3 / 3
	Total	12 / 12 Passed

Description

82%Weight 40%Scale 1-3

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 specific, distinctive description that names concrete actions and natural trigger terms, but it omits an explicit 'Use when...' clause, which limits its completeness. Adding a brief trigger condition would round it out.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when rebasing an OpenMeter branch, especially onto origin/main') to satisfy the completeness 'when' requirement.

Consider mirroring the body's trigger phrasing in the description so the frontmatter alone signals when to invoke the skill.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete gotchas — 'sequential migrations, atlas.sum conflicts, Ent regeneration, and targeted verification' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers 'what does this do' but lacks any explicit 'when to use it' trigger clause; per the rubric a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes natural terms a user needing this skill would say — 'rebase', 'branch', 'migrations', 'atlas.sum conflicts', 'Ent regeneration', 'verification' — with good coverage rather than generic jargon.	3 / 3
Distinctiveness Conflict Risk	The OpenMeter-specific niche (atlas.sum, Ent regeneration, sequential migrations) gives it a clear, distinct trigger unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: openmeterio/openmeter
Path: .agents/skills/rebase/SKILL.md
Commit: 5936703

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.