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 ./src/omnimarket/adapters/codex/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 gives genuinely actionable dispatch guidance — a real command, payload contract, and error handling — and avoids teaching known concepts. It is held back by verbatim duplication between the generated runtime-truth block and the Contract section, the absence of a worked payload example, and a workflow that never sequences its safety mechanisms (compile-only, dry_run, verify) as explicit checkpoints for what is a destructive org-wide batch operation.

Suggestions

Deduplicate the Contract section against the generated runtime-truth block (or reduce it to a pointer), since the command name and both topics currently appear twice in the body.

Add one complete example payload JSON (e.g., a dry-run inventory sweep with correlation_id and run_id filled in) so the dispatch command is copy-paste ready.

Make validation an explicit ordered workflow for this batch/destructive skill: e.g., 1) --compile-only preflight, 2) dry_run=true sweep, 3) review output_payloads[0] counts, 4) live dispatch, with a fix-and-retry loop on error responses.

DimensionReasoningScore

Conciseness

The body is dense operational guidance with no concept-teaching, but the 'Contract' section repeats the generated runtime-truth block verbatim (command name and both topics appear twice) and the payload field list overlaps the argument table. This is more than the minor trimming of anchor 4, though well short of anchor 2's padded verbosity.

3 / 5

Actionability

Provides a concrete executable dispatch command, an explicit payload field mapping, always-include rules (UUIDv4 correlation_id, run_id format), and a clear error path ("surface error.code and error.message"). Not a 5 because --payload '<json-payload>' is a placeholder with no complete worked payload example covering a common case.

4 / 5

Workflow Clarity

The dispatch flow is legible but unnumbered, and validation mechanisms (--compile-only preflight, dry_run, verify) are documented as options rather than sequenced as explicit checkpoints, with no validate-fix-retry feedback loop. As an org-wide batch merge skill, the batch-operation cap of 3 applies: risky-sweep validation is available but never explicitly ordered into the workflow.

3 / 5

Progressive Disclosure

Section headers are clear and navigation is easy, but the ~40-line generated transport/evidence metadata block (binding-field enums, evidence wire schema) is inline reference-grade material in a 125-line file with no bundle files. Fits anchor 3's 'content that should be separate is inline' better than anchor 4's 'most content is appropriately placed'.

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.

The description follows the good-example pattern well: a concise capability statement plus an explicit 'Use for' trigger clause naming four natural use cases. Its main weakness is that the 'what' is expressed through internal jargon (Codex shim, node name) rather than plain capability language, and it lacks common synonym variations of its trigger terms.

DimensionReasoningScore

Specificity

Lists several concrete actions ("PR inventory, triage, merge, or fix sweeps") anchored to a clear domain. Not a 5 because the capability statement leans on the internal node name and omits phases like verification and rebase that the body documents.

4 / 5

Completeness

Both parts are present: an explicit "Use for org-wide PR inventory, triage, merge, or fix sweeps" when-clause and a what-statement. Not a 5 because the 'what' ("Thin Codex skill shim for node_pr_lifecycle_orchestrator") describes implementation plumbing rather than plainly stating the capability.

4 / 5

Trigger Term Quality

Contains natural phrases users would say ("merge", "triage", "fix sweeps", "PR inventory", "org-wide"). Not a 5 because common variations like "pull request" spelled out, "close PRs", or "bulk/batch merge" are missing.

4 / 5

Distinctiveness Conflict Risk

The org-wide PR-lifecycle niche plus unique internal identifiers (node_pr_lifecycle_orchestrator) make it mostly distinct with only minor overlap risk against generic merge/review skills. Not a 5 because 'merge' and 'triage' alone could collide with simpler PR-handling skills.

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

src/omnimarket/adapters/codex/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.