CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

merge-train

Serially land a batch of green PRs through the forge's own merge API — migration-aware ordering, update-branch for stale PRs, wait for the post-merge workflows between merges, then run /worktree-cleanup. Invoke as `/merge-train` (discover all green PRs) or `/merge-train <PR#> [<PR#>…]` (explicit batch). Operator-invoked only; complements /pr-iterate, which never merges.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is merge-train in agranado2k/tic-tac-toe-with-agentic-sdlc

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strongly operational skill body: every step is backed by executable gh/git commands, the batch-merge workflow is sequenced with unusually thorough validation and failure branches, and external authority is clearly delegated. Minor deductions for trimmable rationale asides and a sample merge command that hardcodes a method the skill defers to another document.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanation of general concepts Claude already knows, but several rationale asides could be trimmed ("a local rebase would strip signatures, which is the usual reason a repo forbids rebase merges", "an untagged bump is a release no consumer can reach… the kit's own does, in its self-host suite's F3"). Not 5: these instances of over-explanation keep it short of lean; not 3: most of the rationale is repo-specific policy Claude could not know, not padding.

4 / 5

Actionability

Nearly fully executable guidance: real, copy-paste-ready commands for every phase (`gh pr list --state open --json …`, `gh api -X PUT "repos/{owner}/{repo}/pulls/$PR/update-branch"`, `gh pr checks "$PR" --watch`, `gh run watch <databaseId>`). Not 5: the sample `gh pr merge "$PR" --merge` hardcodes a method the skill itself says is mandated elsewhere (`constitution/local-workflow.md`), a minor copy-paste hazard.

4 / 5

Workflow Clarity

Clear five-step sequence (assemble → order → present plan → land each with sub-steps a–d → after batch) with extensive validation checkpoints: green-check verification, BEHIND detection, `--watch` on re-runs, explicit failure branches for 4b/merge-rejected/4d, and hard rule 6 (failed post-merge workflow stops the train). The hard-rules checklist and skip-to-/pr-iterate feedback loop match the top anchor for a batch operation.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-sectioned file with a dedicated Cross-references section pointing one level deep to real repo artifacts (`constitution/local-workflow.md`, `docs/adr/INDEX.md`) with what each provides. Not 5: the body is ~150 lines and monolithic — the ordering rationale and merge-method policy could arguably live in separate reference files; not 3: structure and signaling are clear, not buried.

4 / 5

Total

17

/

20

Passed

Description

83%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 highly specific, well-delimited description that names every phase of the operation and explicitly distinguishes itself from sibling skills. Its only weaknesses are mild jargon ("the forge's own merge API") and a "when" clause expressed as invocation syntax rather than natural user-need triggers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Serially land a batch of green PRs", "migration-aware ordering", "update-branch for stale PRs", "wait for the post-merge workflows between merges", "then run /worktree-cleanup" — covering the full workflow comprehensively. Not 4: coverage has no minor gaps; every phase of the operation is named.

5 / 5

Completeness

The "what" is explicit and concrete, and the "when" is addressed via explicit invocation guidance ("Invoke as `/merge-train` (discover all green PRs) or `/merge-train <PR#> [<PR#>…]"; "Operator-invoked only"), so the missing-trigger cap does not apply. Not 5: the when is phrased as invocation mechanics rather than concrete situational trigger phrases a user would say.

4 / 5

Trigger Term Quality

Good natural keyword coverage — "land a batch of green PRs", "merge", "stale", "post-merge workflows" — but phrases like "the forge's own merge API" lean jargon-y and common synonyms (e.g. "pull request" spelled out, "CI checks") are missing. Not 5: lacks the synonym/variation breadth of the top anchor.

4 / 5

Distinctiveness Conflict Risk

"complements /pr-iterate, which never merges" and "Operator-invoked only" explicitly delimit the niche against the closest related skill and prevent auto-trigger conflicts. Clear niche (serialized batch landing through the merge API) with minimal conflict risk.

5 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/guards.config.sh)

Warning

Total

15

/

16

Passed

Repository

agranado2k/tic-tac-toe-haskell

Path

.agents/skills/merge-train/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.