CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

merge-sweep

Thin Codex skill shim for node_pr_lifecycle_orchestrator. Use for org-wide PR inventory, triage, merge, or fix sweeps.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/onex/skills/merge-sweep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 actionable with a concrete dispatch command, an argument table, and clear payload/result contracts, but it is held back by triple duplication of the command/topic metadata, a missing example payload, and no post-run validation or recovery guidance for what is a batch merge operation. Organization is serviceable but the generated runtime-truth block belongs in a deduplicated or split-out form.

Suggestions

Include a complete example JSON payload (with correlation_id, run_id, and representative argument values) so the dispatch command is copy-paste ready instead of a '<json-payload>' placeholder.

Deduplicate the command name and command/terminal topic listings that currently appear in the Runtime truth section, the node contract metadata, and the Contract section, or move the generated runtime-truth metadata into a reference file.

Add post-run validation and feedback-loop guidance for the batch merge workflow: how to inspect prs_skipped and phase outcomes, what to do when ok is false or only some PRs merged, and when to re-run with fix_only.

DimensionReasoningScore

Conciseness

The body is dense rather than padded, but the command name and command/terminal topics are repeated verbatim in three places ("Runtime truth" adapter section, node contract metadata, and the "Contract" section), and the inline evidence-wire-schema detail ("runtime-evidence/v2", binding fields) could be tightened or deduplicated. This fits the mostly-efficient-but-could-be-tightened anchor rather than the minor-trims anchor 4.

3 / 5

Actionability

The dispatch section gives a concrete executable command ("env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name ... --timeout-ms 300000"), an argument table with defaults, and explicit payload field mapping plus result-interpretation rules. It falls short of copy-paste-ready anchor 5 because the payload is a '<json-payload>' placeholder with no complete example payload.

4 / 5

Workflow Clarity

The sequence (map arguments → build payload with correlation_id/run_id → dispatch → interpret output) is present with a compile-only preflight and dry_run/verify options, but this is a batch merge operation and there is no post-run validation or feedback loop — no guidance on reviewing prs_skipped, handling partial failures, or retrying. Per the batch/destructive-operation guideline, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

The single file has clear sections (Arguments, Dispatch, Contract, Output), but the ~40-line generated "Runtime truth" metadata block is inline content that would fit better in a reference file, the same topic/command data is duplicated across sections, and the referenced scripts/run_codex_runtime_request.py has no counterpart in the skill bundle. This matches the some-structure-but-could-be-better-organized anchor.

3 / 5

Total

13

/

20

Passed

Description

75%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 solid description with an explicit 'Use for' trigger clause and several concrete PR-lifecycle actions. Its main weakness is leading with internal implementation jargon ("Thin Codex skill shim for node_pr_lifecycle_orchestrator") instead of user-facing capability language, and it lacks common synonym variations like "pull requests".

DimensionReasoningScore

Specificity

The description lists several concrete actions ("org-wide PR inventory, triage, merge, or fix sweeps") matching the several-specific-actions anchor, but the lead-in "Thin Codex skill shim for node_pr_lifecycle_orchestrator" describes implementation plumbing rather than a capability, keeping it below the comprehensive anchor 5.

4 / 5

Completeness

Both parts are present: an explicit trigger clause ("Use for org-wide PR inventory, triage, merge, or fix sweeps") and a what (the PR lifecycle actions), satisfying the both-present anchor. It is not a 5 because the 'what' is clouded by the shim/orchestrator jargon rather than stated as concrete trigger phrases.

4 / 5

Trigger Term Quality

It contains the natural terms a user would say when needing this skill ("PR", "merge", "triage", "fix", "sweeps", "org-wide"), matching the good-coverage anchor, though common variations like "pull requests" or "repo" are missing and the first sentence is internal jargon.

4 / 5

Distinctiveness Conflict Risk

"org-wide PR inventory, triage, merge, or fix sweeps" carves a clear niche with distinct triggers, but generic terms like "merge" leave minor overlap risk with everyday PR/merge skills, fitting the mostly-distinct anchor rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

OmniNode-ai/omnimarket

Path

plugins/onex/skills/merge-sweep/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.