CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dep-cascade-dedup

Thin Codex skill shim for node_dep_cascade_dedup_orchestrator. Use when deduplicating dependency bump PR cascades through runtime truth.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/onex/skills/dep-cascade-dedup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 lean, concrete dispatch shim with an executable command, explicit payload mapping, and clear error semantics. Its weaknesses are verbatim duplication between the Contract and runtime-truth sections and the absence of dry-run-first or post-close verification for its destructive batch operation.

Suggestions

Remove or merge the '## Contract' section: its command name, request wrapper, topics, and backing node duplicate the generated 'Runtime truth' block verbatim — keep only the repo paths that add new information.

Add a destructive-safety checkpoint: recommend "dry_run": true for first runs and instruct the agent to review prs_closed vs prs_kept in the output before treating the run as final.

Trim the unused evidence wire-schema detail (runtime-evidence/v2, terminal_selection enum, binding fields) that the dispatch workflow never references, or move it to a reference file.

DimensionReasoningScore

Conciseness

The hand-written sections are lean and operational with no concept explanations or fluff, but the '## Contract' section repeats the generated runtime-truth block almost verbatim (command name, request wrapper, both topics, backing node), and the generated block carries evidence-schema detail ('runtime-evidence/v2', the 'terminal_selection' enum, binding fields) that the dispatch workflow never uses. A fully duplicated section is more than the 'minor instances' of the 4 anchor, while the absence of any padding rules out 2.

3 / 5

Actionability

The Dispatch section gives a copy-paste-ready command ('env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name ... --timeout-ms 600000') with explicit payload field names, a compile-only preflight, and concrete result interpretation ('treat output_payloads[0] as the primary node result', 'surface error.code and error.message directly'). Not 5 because the '<json-payload>' placeholder is never instantiated — no worked example payload for the common case.

4 / 5

Workflow Clarity

The map-args → optional compile-only preflight → dispatch → interpret-result flow is clear and the failure path is explicit ('A node_not_implemented response is the current explicit stop state'), but this is a destructive batch operation (closing PRs across repos) with no outcome verification and no guidance to prefer dry_run first. The rubric's destructive/batch cap therefore applies despite the otherwise 4-level sequencing.

3 / 5

Progressive Disclosure

Sections (Arguments, Dispatch, Contract, Output) are well-labeled and the skill is self-contained with no bundle files to reference. Not 5 because at ~106 body lines the 39-line generated contract block is inline metadata that could live in a reference file; not 3 because the structure is clean and the inline block is load-bearing for dispatch correctness (e.g. 'It must not publish the target node command topic directly').

4 / 5

Total

14

/

20

Passed

Description

66%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 honest, third-person, and highly distinctive, with an explicit 'Use when' trigger clause. Its weaknesses are thin stated capabilities (one action verb) and narrow natural-language trigger coverage — a user asking to 'close the superseded dependency PRs' would not obviously match it.

Suggestions

State the concrete outcomes in the description itself, e.g. 'Closes superseded dependency bump PRs and keeps the latest version per package group' — currently 'deduplicating' is the only stated action.

Add natural trigger variations users would actually say (superseded, duplicate, redundant dependency PRs) and drop or de-emphasize internal jargon like 'runtime truth' from the trigger clause.

DimensionReasoningScore

Specificity

Names the domain ("Thin Codex skill shim for node_dep_cascade_dedup_orchestrator") and one concrete action ("deduplicating dependency bump PR cascades"), but lists no other capabilities — the node's PR discovery, version grouping, and close decisions appear only in the body, not the description. The single stated action is specific rather than generic (rules out 2), and one action is not 'several specific actions' (rules out 4).

3 / 5

Completeness

Both parts are present: the what ("Thin Codex skill shim for node_dep_cascade_dedup_orchestrator") and an explicit when ("Use when deduplicating dependency bump PR cascades"). Not 5 because the 'what' is structural — a shim over a node — rather than a functional capability statement, so the concrete behavior is only derivable via the trigger clause.

4 / 5

Trigger Term Quality

"deduplicating dependency bump PR cascades" matches what a user in this domain would naturally say, but "runtime truth" is internal jargon and common variations such as "superseded PRs", "duplicate dependency PRs", or "close old bumps" are absent. Coverage is relevant but incomplete, fitting the 'some relevant keywords but missing common variations' anchor rather than 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The backing node name "node_dep_cascade_dedup_orchestrator" and the narrow "dependency bump PR cascades" trigger define a clear niche with distinct triggers; the risk of this firing for an unrelated skill is minimal.

5 / 5

Total

15

/

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/dep-cascade-dedup/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.