land

Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/land/SKILL.md

Quality

Content

70%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 highly actionable, well-sequenced workflow with strong validation and feedback loops, but it is dense and repetitive with no progressive disclosure of reference material into separate files. Tightening repetition and splitting the long reference sections would materially improve it.

Suggestions

De-duplicate the preflight command, the handoff-note format, and the `[codex]` reply rules — state each once and reference it from the other sections to cut noticeable repetition.

Move the detailed Review Handling and Failure Handling sections into one-level-deep reference files (e.g. references/review-handling.md, references/failure-handling.md) and link to them from the body, since the skill is well over 50 lines.

Fill the actionability gaps: replace the placeholder conflict-resolution comment block with the concrete `pull`/`push` skill invocations, and specify the exact "backend checks" and "smoke/runtime checks" commands used in the conservative fallback.

Dimension	Reasoning	Score
Conciseness	Content is operational rather than conceptual, but the preflight command, handoff-note format, and `[codex]` reply rules are each repeated verbatim several times across Steps, Commands, and dedicated sections, adding clear padding that could be tightened.	3 / 5
Actionability	Provides copy-paste-ready shell and `gh api` commands with documented exit codes, but the conflict-resolution block is left as placeholder comments and step 6's "backend checks" / "smoke/runtime checks" are unspecified, leaving minor gaps.	4 / 5
Workflow Clarity	An 18-step numbered sequence with explicit validation checkpoints (preflight exit codes 0/6, merge-state checks), feedback loops (fail → logs → fix → commit → push → re-run), and clear gates against merging with outstanding review.	5 / 5
Progressive Disclosure	Well-sectioned with clear headers, but at ~330 lines it is a monolithic SKILL.md with no bundle files; the lengthy Review Handling and Failure Handling reference material is inlined rather than split into one-level-deep reference files.	3 / 5
	Total	15 / 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 strong, third-person description that concretely states both the skill's actions and its use-when triggers with minimal fluff. The main weakness is minor overlap risk from the generic term "merge" and slight coverage gaps.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "monitoring conflicts, resolving them, waiting for checks, and squash-merging when green" — but omits review-feedback handling from the description, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ("Land a PR by monitoring conflicts... squash-merging when green") and when ("use when asked to land, merge, or shepherd a PR to completion") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases "land, merge, or shepherd a PR to completion" map well to what a user would say, though "shepherd" is slightly colloquial and a few common variants are absent.	4 / 5
Distinctiveness Conflict Risk	Clear PR-landing niche with distinct triggers, but the generic verb "merge" creates minor overlap risk with a potential standalone merge/push skill.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: karanhudia/borg-ui
Path: .codex/skills/land/SKILL.md
Commit: c7f32d1

Reviewed: 1 day 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.