CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-stack

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.

80

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%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 exemplary instruction skill body: concise, fully actionable, with sequenced workflows that include validation and error-recovery feedback loops, and a clean one-level-deep reference structure whose files all exist.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: no generic explanations of git or PRs, every line teaches a non-obvious behavior (TTY detection, exit codes, merge semantics). Every token earns its place.

5 / 5

Actionability

Fully executable copy-paste-ready commands for setup, the core loop, sync, and merge, plus a concrete JSON schema for parsing `view --json` and an explicit always/never-run command table covering common cases.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation and feedback loops: the Exit 3 recovery loop, the sync-divergence ("Sync aborted") handling, the unstack-then-retry checkout flow, and the all-or-nothing merge semantics.

5 / 5

Progressive Disclosure

Clear overview in SKILL.md with three well-signaled one-level-deep references (stack-design.md, commands.md, troubleshooting.md), each mapped to a specific trigger; all referenced files exist in the bundle and content is appropriately split.

5 / 5

Total

20

/

20

Passed

Description

100%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 model description: concrete actions, natural trigger terms, explicit what-and-when guidance, and a well-scoped niche with low conflict risk. It is also appropriately concise.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout") and the split/isolate action, giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers what ("Manages stacked PRs and splits multi-part work into reviewable branches") and when ("Use for..." plus "whenever a user mentions a stack... or when a stack is checked out") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers the natural terms users say ("stack", "split", "branch layers", "dependent PRs", "gh stack", "stack is checked out") including the exact CLI invocation and common synonyms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (stacked PRs with gh-stack) with distinct triggers; minimal risk of conflicting with ordinary PR skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Arize-ai/phoenix
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.