land-pr

Land lossless-claw pull requests safely; use when asked whether a PR is ready, whether CI passes, to merge or land a PR, or to perform maintainer closeout after review.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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 high-quality, executable PR-landing playbook with concrete commands, strong validation checkpoints around a destructive merge, and a clear Do-Not guardrail section. Main weakness is minor over-explanation in a few prose lines rather than any structural gap.

Suggestions

Trim maintainer-common-sense prose like 'Maintainers own it.' where the preceding instruction already conveys the rule, to lift conciseness toward 5.

Consider moving the long `gh pr view`/`gh pr checks` field lists into a short reference snippet or a bundled script so the workflow prose stays scannable, improving progressive disclosure.

Soften the hard-coded absolute path '/Users/phaedrus/Projects/prompts/skills/autoreview/scripts/autoreview' to a discoverable or repo-relative invocation so the skill stays executable across machines.

Dimension	Reasoning	Score
Conciseness	Largely lean with no padding about what PRs or CI are, but a few lines over-explain maintainer common sense ('Do not expect external contributors to add Changesets metadata. Maintainers own it.') and could be trimmed. Not a 5 because some prose restates what the commands already imply.	4 / 5
Actionability	Provides copy-paste-ready `gh` commands with exact JSON fields and flags (`--squash --match-head-commit "$head"`), covering the common ready-to-merge cases including a deterministic wrapper and manual fallback.	5 / 5
Workflow Clarity	An 8-step sequence with explicit validation checkpoints — head-SHA pinning re-read before merge, checks must be complete on the pinned SHA, branch review only from a matching HEAD, abort if SHA changed — plus feedback loops for a destructive merge operation, satisfying the destructive-skill validation requirement.	5 / 5
Progressive Disclosure	A single-file skill with no bundle files (references/, scripts/, assets/ absent) and clean section structure (Workflow, Do Not). For a no-bundle skill this is well-organized; not a 5 only because there is no one-level-deep reference navigation to signal, which is appropriate but not exemplary for this dimension.	4 / 5
	Total	18 / 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 well-crafted description that names the domain, lists concrete actions, and provides explicit 'use when' triggers scoped to a single repository. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Land lossless-claw pull requests safely', check 'whether a PR is ready, whether CI passes', 'merge or land a PR', and 'maintainer closeout after review' — with only minor coverage gaps (e.g., the issue-cleanup sub-task is implied rather than enumerated).	4 / 5
Completeness	Explicitly states both what it does ('Land lossless-claw pull requests safely') and when to use it via a concrete 'use when asked whether...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Captures natural maintainer phrasing such as 'whether a PR is ready', 'whether CI passes', and 'merge or land a PR'; good coverage though it omits common synonyms like 'ship it' or 'is this green'.	4 / 5
Distinctiveness Conflict Risk	Scoped to the 'lossless-claw' repository with niche-specific triggers (maintainer closeout, CI-passes checks), giving it a clear niche and minimal conflict risk with general PR skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: Martian-Engineering/lossless-claw
Path: .agents/skills/land-pr/SKILL.md
Commit: db67593

Reviewed: 22 hours ago

Table of Contents

Discovery Implementation Validation

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.