CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-approve

Approve a GitHub pull request, inferring the target from context when no PR is given. Use when the user invokes `$pr-approve`, asks to approve a PR, or approves a pull request mentioned earlier in the conversation.

Quality

95%

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

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-only skill body: fully executable gh-based workflow with tight sequencing, pre-action validation, user confirmation, and per-item failure handling, all at minimal token cost. Organization is clean and self-contained with nothing that belongs in bundle files. No weaknesses identified.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: no explanation of what gh, GitHub, or pull requests are; every line is instruction (commands, field lists, derivation rules, card templates). Matches the 'every token earns its place' anchor; there is nothing padded to trim.

5 / 5

Actionability

All guidance is copy-paste executable: exact gh commands with explicit --json field lists, jq filters, and literal card/confirmation templates. Deriving states (lifecycle, approval status, checks) from named JSON fields leaves no ambiguity about how to execute, matching the fully-executable anchor.

5 / 5

Workflow Clarity

A clear 5-step sequence (resolve → fetch metadata → confirm → approve → report) with explicit validation checkpoints: state derivation (merged/closed/open), checks status, prior-approval detection, and mandatory user confirmation before any approval. Error recovery is specified ("If gh refuses... report that specific failure and continue with the rest"), satisfying the feedback-loop expectation for a batch-capable operation.

5 / 5

Progressive Disclosure

This is a single-file, single-purpose skill with no bundle files (references/, scripts/, assets/ absent) and no external references needed. Content is appropriately contained in well-organized, clearly headed sections with no dangling file references, which merits the top score under the simple-skill provision.

5 / 5

Total

20

/

20

Passed

Description

87%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 crisp, third-person description that states exactly what the skill does and gives three explicit, natural trigger conditions including the slash-command invocation. The only gap is modest synonym coverage for approval phrasing. It compares favorably to the good examples in both completeness and distinctiveness.

DimensionReasoningScore

Specificity

"Approve a GitHub pull request, inferring the target from context when no PR is given" names the domain and concrete actions (approval plus contextual target inference) that fully cover this single-purpose skill's scope. It lists only 1-2 discrete actions rather than multiple, so it sits between the 'several specific actions' (4) and '1-2 concrete actions' (3) anchors, clearly above 3.

4 / 5

Completeness

Explicitly answers "what" ("Approve a GitHub pull request, inferring the target from context when no PR is given") and "when" ("Use when the user invokes $pr-approve, asks to approve a PR, or approves a pull request mentioned earlier in the conversation") with concrete trigger phrases. This matches the top anchor exactly; the 4 anchor's weaker/implicit 'when' does not apply.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "asks to approve a PR", "approves a pull request" — plus the explicit "$pr-approve" invocation trigger, giving good coverage of PR/pull-request phrasing. A few natural variants (e.g., "LGTM", "greenlight a PR") are missing, keeping it below the comprehensive-synonyms anchor of 5.

4 / 5

Distinctiveness Conflict Risk

The PR-approval niche is distinct from adjacent skills (review, merge, comment) because the approve action and its triggers are verb-specific, and "inferring the target from context" scopes it to already-mentioned PRs. Minimal conflict risk, matching the clear-niche anchor; not merely 'mostly distinct' (4).

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phatblat/dotfiles

Path

.agents/skills/pr-approve/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.