CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prlanded

Verify a merged PR landed by content without orphaned late commits, post its `Review record` comment on the merged PR, and plan cleanup only when explicitly requested. Use after a PR merges into main.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

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

Excellent procedural content: terse, fully executable, and sequenced with real validation checkpoints and a safety gate on destructive cleanup. The only minor gap is reference hygiene — overlapping external links with fragile relative paths.

DimensionReasoningScore

Conciseness

The 15-line body is lean and imperative throughout — "Require an explicit `<pr>`", "Fetch `origin/main`, inspect `git rev-list --parents -n 1`" — with no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Fully executable guidance with copy-paste-ready commands and placeholders, covering both the two-parent merge case (`git merge-base --is-ancestor`, `git show --remerge-diff`) and the squash case (`git diff --stat`, `git patch-id --stable`), plus the `gh pr view` verification call.

5 / 5

Workflow Clarity

A clear 5-step sequence with an explicit validation checkpoint (verify `state` is `MERGED` with non-null `mergeCommit` and `mergedAt`), error recovery (fix-forward with a new PR if work was missed), and destructive operations gated on an explicit cleanup request.

5 / 5

Progressive Disclosure

The short body is well organized with clearly signaled one-level references to the workflow docs and detailed procedure, but the two overlapping external references use fragile `../../../` paths that escape the skill directory, and one points at another copy of SKILL.md, creating mild ambiguity about where authoritative detail lives.

4 / 5

Total

19

/

20

Passed

Description

92%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: it states three concrete capabilities in third person and gives an explicit, well-timed usage trigger. The only weakness is trigger synonym coverage, which is good but not exhaustive.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "Verify a merged PR landed by content without orphaned late commits", "post its `Review record` comment", "plan cleanup only when explicitly requested" — in third person, with comprehensive coverage of the skill's behavior.

5 / 5

Completeness

Explicitly answers both what (verify landing by content, post the Review record comment, gate cleanup on explicit request) and when ("Use after a PR merges into main") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural triggers like "merged PR", "PR merges into main", and "landed" are present and well-chosen, but common variations such as "pull request" spelled out or "check the PR landed" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (post-merge landing verification) with a timing-distinct trigger ("after a PR merges into main") that minimizes conflict risk even against closely related PR-workflow skills.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

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