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 ./src/omnimarket/adapters/codex/skills/dep-cascade-dedup/SKILL.md

The canonical home for this skill is dep-cascade-dedup in OmniNode-ai/omnimarket

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.

The content is a well-sectioned, mostly executable dispatch guide with a real command, argument table, and error handling, held back by a duplicated contract section and the absence of a worked payload example. Most importantly, a batch PR-closing operation ships without result verification or dry-run-first guidance, capping workflow clarity.

Suggestions

Remove the 'Contract' section or reduce it to the one item not already in the runtime-truth block (the backing node path) — the command name and both topics are stated verbatim twice.

Add a filled example payload (e.g., '{"repos": ["org/repo"], "label": "dependencies", "dry_run": true}') so the dispatch command is copy-paste ready.

Add a verification checkpoint for the destructive close path: recommend 'dry_run: true' first, then confirm the reported prs_closed/prs_kept groups before dispatching without it.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence and explains no general concepts, but the 'Contract' section repeats the command name and both topics already given in the generated runtime-truth block, and the binding/evidence wire-schema detail (terminal_selection enum, schema_version lineage) exceeds what a self-described 'thin shim' needs. Not 4 because the duplication and over-detailed evidence fields are more than minor trimmable instances; not 2 because everything present is domain-specific truth rather than padding or explanations of known concepts.

3 / 5

Actionability

The dispatch section gives a concrete, mostly executable command with real flags ('env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name ... --timeout-ms 600000'), an argument table with defaults, an explicit payload field list, and concrete error-handling guidance ('surface error.code and error.message'). Not 5 because '--payload '<json-payload>'' is a placeholder with no filled example payload covering the common case.

4 / 5

Workflow Clarity

The sequence (map arguments → build payload → dispatch → interpret ok/error → render output) is present and the '--compile-only' preflight is an explicit checkpoint, but the skill drives a batch, destructive operation (bulk-closing superseded PRs) with no result-verification step, no dry-run-first guidance despite 'dry_run' existing as an argument, and no fix-and-retry loop on failure. The rubric's destructive/batch cap of 3 applies: checkpoints for the close operation itself are missing or implicit. Not 2 because the sequence is well-defined and preflight/error paths are stated.

3 / 5

Progressive Disclosure

The body is cleanly sectioned (Arguments, Runtime truth, Dispatch, Contract, Output) with all content appropriately in SKILL.md for a thin single-purpose adapter, and the only file reference ('scripts/run_codex_runtime_request.py') is a real script in the target repo per the 'Run from the omnimarket repo' instruction — though no bundle files exist to verify. Not 5 because at ~108 lines the generated runtime-truth block could live in a reference file, and the duplicated Contract section adds navigation noise.

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 has an explicit 'Use when' trigger and occupies a highly distinct niche, but it delegates the "what" to an internal node name and offers only a single natural trigger phrase. Expanding the action list and trigger synonyms would lift specificity and trigger-term quality.

Suggestions

State the concrete operations in the description itself (e.g., 'Discovers dependency bump PRs, groups them by version, and closes superseded PRs') instead of deferring entirely to the node name.

Add natural trigger variations users would actually say, such as 'duplicate dependency PRs', 'superseded version-bump PRs', or 'Dependabot PR cleanup'.

Drop or replace the jargon phrase 'through runtime truth' — no user would say it, so it adds no trigger value.

DimensionReasoningScore

Specificity

"Thin Codex skill shim for node_dep_cascade_dedup_orchestrator" and "deduplicating dependency bump PR cascades" name the domain and one concrete action, but the description never states what the skill actually does (PR discovery, version grouping, closing superseded PRs). Not 4 because it does not list several specific actions; not 2 because the dedup-cascade action is concrete rather than generic.

3 / 5

Completeness

Both parts are present: the "what" ("Thin Codex skill shim for node_dep_cascade_dedup_orchestrator") and an explicit "Use when deduplicating dependency bump PR cascades..." trigger. Not 5 because the "what" leans on the node name instead of stating the concrete operations, and the "when" is a single narrow trigger rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

"deduplicating dependency bump PR cascades" is a phrase a user in this domain might say, but coverage stops there — no synonyms like "duplicate PRs", "superseded PRs", "version bumps", or "Dependabot", and "through runtime truth" is internal jargon no user would utter. Not 4 because common variations are missing, not 2 because the one phrase present is genuinely natural to the domain.

3 / 5

Distinctiveness Conflict Risk

The niche is unmistakably narrow — a shim over one named orchestrator for dependency-bump PR cascade dedup — so it is clearly distinguishable from other skills and unlikely to trigger for the wrong one. Not 4 because there is no realistic overlap with a closely related skill given how specific the trigger is.

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

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