CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

merge-ready

Get a branch ready for the maintainer's final review. Review it for security, simplicity, and billing abuse, fix what's real, get checks passing, and open or update the PR. Use whenever the user says a feature, fix, or 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").

Quality

88%

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

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

An efficient, well-sequenced instruction skill: exact commands, named stack invariants, an explicit local-checks validation gate, and a well-placed pointer to the repo's review guidelines. The main gaps are review criteria framed as questions rather than concrete checks and an only-implied error-recovery loop.

DimensionReasoningScore

Conciseness

The body is lean and every sentence instructs ("Fix what's real. Commit as you go."); it explains no concepts Claude already knows and even delegates judgment explicitly ("review it however you think best"). Every token earns its place, matching the 5 anchor.

5 / 5

Actionability

Concrete commands and specifics are present (`pnpm ci:check`, `pnpm test`, named SDKs TanStack/DataForSEO/Autumn/Cloudflare, the exact PR format and guidelines path). It stops short of 5 because the core review criteria are posed as open questions ("Is it secure?") rather than concrete, checkable guidance.

4 / 5

Workflow Clarity

A clear ordered sequence (merge origin/main, review everything, fix and commit, get checks passing locally, push, open/update the PR) with an explicit validation gate before push. It is not 5 because the fix-and-retry feedback loop ("Fix what's real... Get ... passing") is implied rather than an explicit validate→fix→re-run step.

4 / 5

Progressive Disclosure

This is a 19-line single-purpose skill with no bundle files and no need for external references, and its paragraphs are well-ordered with one clearly signaled one-level reference (docs/maintainers/review-guidelines.md). The simple-skill exception applies: this structure merits 5.

5 / 5

Total

18

/

20

Passed

Description

88%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 description: concrete action list, explicit 'Use whenever...' triggers with quoted user phrasings, and a distinct merge-preparation niche. The only gap is a few missing natural synonyms (e.g., "ready to merge") and slight overlap risk with general review skills.

DimensionReasoningScore

Specificity

"Review it for security, simplicity, and billing abuse, fix what's real, get checks passing, and open or update the PR" lists multiple concrete actions covering the entire workflow, matching the comprehensive-coverage anchor. Nothing is vague or padded.

5 / 5

Completeness

The 'what' is explicit and concrete (review for security/simplicity/billing abuse, fix, get checks passing, open or update the PR) and the 'when' is explicit with concrete trigger phrases ("Use whenever the user says a feature, fix, or branch should be 'merge ready'..."). Both are clearly answered, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases are present and quoted ("merge ready", "build X and make it merge-ready", "asks to get changes ready for review"), giving good keyword coverage. It falls short of the 5 anchor because common synonyms like "ready to merge" or "open/prepare the PR" are missing.

4 / 5

Distinctiveness Conflict Risk

The maintainer-handoff niche with billing-abuse review and the distinctive "merge ready" trigger give it a clear identity with minimal conflict risk. It sits at 4 rather than 5 because "asks to get changes ready for review" could overlap with generic code-review or PR skills.

4 / 5

Total

18

/

20

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.

Validation — 14 / 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

Path

.agents/skills/merge-ready/SKILL.md

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.