CtrlK
BlogDocsLog inGet started
Tessl Logo

merge

Wait for a Remotion pull request to become mergeable, handle merge conflicts, distinguish genuine CI failures from flakes, rerun flaky checks through the flake skill, and merge the PR. Use when asked to run /merge, merge a current PR after checks pass, or shepherd a Remotion PR through CI to merge.

79

Quality

100%

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

100%

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

A tight, command-driven workflow that tells Claude exactly what to run and when, with explicit checkpoints and recovery loops for both genuine failures and flakes. It stays lean and delegates detail to clearly-linked sibling skills rather than ballooning inline.

DimensionReasoningScore

Conciseness

The body is lean: it issues direct `gh` commands without explaining what GitHub, CI, or merge conflicts are, assuming Claude's competence and earning every token.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands such as `gh pr view --json ...`, `gh pr checks --watch --interval 30`, and `gh pr merge --squash --delete-branch` rather than vague direction.

3 / 3

Workflow Clarity

A clearly sequenced loop with explicit validation checkpoints — stop on non-CI blockers, merge only when checks pass and mergeable — plus feedback loops (fix→run→push→restart and flake→rerun→restart) for error recovery.

3 / 3

Progressive Disclosure

A ~50-line single-purpose skill with well-organized sections (Loop, CI Failures) and clearly signaled one-level-deep links to sibling skills (`pr-ready`, `flake`); no bundle files are needed and none are missing.

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, third-person description that names concrete capabilities and pairs them with explicit natural-language triggers. It answers both what and when without padding or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'handle merge conflicts, distinguish genuine CI failures from flakes, rerun flaky checks... and merge the PR' — matching the top anchor for listing several specific actions.

3 / 3

Completeness

Explicitly answers what (wait for mergeable, handle conflicts, distinguish genuine failures, rerun flakes, merge) and when ('Use when asked to run /merge, merge a current PR after checks pass, or shepherd a Remotion PR through CI to merge').

3 / 3

Trigger Term Quality

'Use when asked to run /merge, merge a current PR after checks pass, or shepherd a Remotion PR through CI to merge' gives natural terms users would say ('/merge', 'merge a PR', 'CI'); not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to Remotion PR merge-shepherding with the '/merge' trigger, occupying a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
remotion-dev/remotion
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.