CtrlK
BlogDocsLog inGet started
Tessl Logo

merge-ready

Take a branch from "code exists (or is about to)" to "ready for the maintainer's final review" — multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR. Use whenever the user says a feature/fix/branch should be "merge ready", asks to get changes ready for review, or appends this to a build request ("build X and make it merge-ready").

78

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

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.

The content is a tight, actionable, well-sequenced workflow with explicit checkpoints and a validation loop. It assumes Claude's competence and stays free of redundant explanation. Strong across all content dimensions.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no explanatory filler about concepts Claude already knows (git, PRs, CI); every line earns its place, matching the 'lean and efficient' anchor rather than the padded 2.

3 / 3

Actionability

Provides concrete, executable guidance throughout — specific git commands, a defined per-axis subagent structure with severity buckets, and explicit PR-description requirements — making it copy-ready rather than vague direction.

3 / 3

Workflow Clarity

A clear six-phase numbered sequence (0–5) with explicit 'Checkpoint' markers and a fix→ci:check→re-run feedback loop in step 4, satisfying the explicit-validation-and-feedback anchor; not the checkpoint-missing 2.

3 / 3

Progressive Disclosure

A single self-contained workflow organized into well-signaled numbered sections with no nested references; per the simple-skill guidance this is appropriately structured and not a monolithic wall of text needing to be split.

3 / 3

Total

12

/

12

Passed

Description

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

The description clearly and concisely states the skill's concrete actions and gives explicit, natural-language trigger conditions. Voice is appropriately third person with no over-claims. It is a strong, distinctive skill description.

DimensionReasoningScore

Specificity

Enumerates concrete actions — 'multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR' — matching the 'lists multiple specific concrete actions' anchor; it is not merely naming a domain as a 2 would.

3 / 3

Completeness

States both what the skill does (the pipeline) and explicit when guidance via 'Use whenever the user says…', satisfying the what-AND-when-with-explicit-triggers anchor; a 2 would omit or only imply the when.

3 / 3

Trigger Term Quality

Uses natural user phrasings ('merge ready', 'get changes ready for review', 'build X and make it merge-ready') that a user would actually say, giving good coverage of common variations rather than just one.

3 / 3

Distinctiveness Conflict Risk

'merge-ready' occupies a distinct niche tied to a maintainer-review workflow with specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
every-app/open-seo
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.