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.

1.90x

Quality

76%

Does it follow best practices?

Impact

95%

1.90x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

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

The body is a thorough, actionable PR-landing playbook with strong feedback loops and concrete gh commands, but it is longer than necessary due to cross-section repetition and keeps reference-grade material inline rather than splitting it into bundled files.

Suggestions

Dedupe the Codex-review acknowledgement and 'commit/push skill' instructions into a single section that the other steps reference, to cut repetition and length.

Move the gh api endpoint reference (review comments, issue comments, in_reply_to rules) into a references/ file and link to it one level deep, improving progressive disclosure and token efficiency.

Either add the referenced land_watch.py to a scripts/ bundle or reword the reference so it does not point to a file that is not shipped with the skill.

Dimension	Reasoning	Score
Conciseness	Operational and assumes Claude's intelligence, but Codex-review acknowledgement and 'commit with the commit skill, push with the push skill' recur across Commands, Failure Handling, and Review Handling, adding repetition that could be tightened.	3 / 5
Actionability	Provides concrete executable gh commands and exact gh api endpoints with flags (e.g. --squash, in_reply_to) plus a watcher exit-code table; minor gaps remain where some command blocks are comment placeholders rather than copy-paste code.	4 / 5
Workflow Clarity	Clear numbered sequence with explicit validation ('Confirm the full gauntlet is green locally before any push') and feedback loops (fail -> pull logs -> fix -> commit -> push -> re-run), but steps 10-14 intermix policy rules with procedural sequence and the manual-watch vs async-helper branching is not crisply sequenced.	4 / 5
Progressive Disclosure	Headers give some structure, but the detailed Codex review-handling API reference (~60 lines) is inlined rather than split out, and the only referenced script (.codex/skills/land/land_watch.py) is not present in the bundle (references/scripts/assets are all absent).	3 / 5
	Total	14 / 20 Passed

Description

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

The description is concise, concrete, and clearly states both what the skill does and when to use it with natural trigger phrases. It is well above average with only minor synonym-coverage and overlap gaps.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'monitoring conflicts, resolving them, waiting for checks, and squash-merging when green' — giving comprehensive coverage of the landing workflow.	5 / 5
Completeness	Explicitly answers both what ('Land a PR by ...') and when ('use when asked to land, merge, or shepherd a PR to completion') with concrete trigger phrases.	5 / 5
Trigger Term Quality	'use when asked to land, merge, or shepherd a PR to completion' gives strong natural phrases users actually say, but misses synonyms like 'ship' or 'close a PR'.	4 / 5
Distinctiveness Conflict Risk	'Land/shepherd a PR to completion' is a distinct niche, but the shared trigger 'merge' carries minor overlap risk with generic git-merge workflows.	4 / 5
	Total	18 / 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: openai/symphony
Path: .codex/skills/land/SKILL.md
Commit: 8001b52

Reviewed: 23 days 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.