CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

local-review

Thin Codex skill shim for node_local_review. Use to run the OmniMarket local review loop through the runtime adapter.

Quality

75%

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/local-review/SKILL.md

The canonical home for this skill is local-review in OmniNode-ai/omnimarket

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, dispatch-ready shim: fully executable command and payload guidance, explicit error and output handling, and an honest compile-only preflight caveat. Its only weaknesses are mild — duplicated contract metadata across two sections and slightly more evidence-schema detail than the task strictly requires.

DimensionReasoningScore

Conciseness

The body is dense and fact-per-line with no explanation of concepts Claude already knows, but the command/topic contract metadata is duplicated between the generated "Runtime truth" section and the "## Contract" section, and the evidence-wire-schema and binding-field detail slightly exceeds a thin shim's needs.

4 / 5

Actionability

The dispatch command, complete payload JSON shape, argument table with defaults and env-var fallback, input-mapping and generation rules, --compile-only preflight, and explicit ok true/false output handling make the guidance fully executable and copy-paste ready for the common cases.

5 / 5

Workflow Clarity

The single-task sequence (run from the omnimarket repo, map inputs into the payload, dispatch via the wrapper, interpret output or surface error.code/message) is clear with a validation checkpoint (--compile-only preflight), but the preflight is optional rather than sequenced as a mandated validate-before-dispatch step and loop-level verification is delegated to the node.

4 / 5

Progressive Disclosure

The single-file body is well organized into Arguments, Dispatch, Contract, and Output sections with one-level-deep pointers to real repo artifacts (scripts/run_codex_runtime_request.py, src/omnimarket/nodes/node_local_review/); the gap is the ~40-line generator-owned runtime-truth block duplicated by the Contract section in a file over 50 lines, which keeps it from a 5.

4 / 5

Total

17

/

20

Passed

Description

57%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 highly distinctive and names a concrete niche, but reads as internal jargon rather than a user-facing trigger: it states one action, provides no explicit "Use when..." guidance, and omits the review/fix/commit/clean-check capabilities that would make it both more specific and more discoverable.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to run local reviews, a review-fix-commit loop, or clean-run checks on the OmniMarket repo."

Enumerate the concrete capabilities in the description (runs the review, fix, commit, and clean-check loop) instead of the single generic action "run the local review loop".

Reduce internal jargon ("thin shim", "runtime adapter", "node_local_review") or pair each term with a natural synonym users would actually say.

DimensionReasoningScore

Specificity

Names a specific domain ("OmniMarket local review loop", "node_local_review") with one concrete action ("run ... through the runtime adapter"), but does not enumerate the several actions the skill actually enables (review, fix, commit, clean-check), matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

The "what" is clear (a thin shim over node_local_review), but the "when" is only weakly implied through the "Use to run..." purpose clause; there is no explicit "Use when..." situational trigger, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"local review loop" is a natural user phrase, but the description is dominated by jargon ("thin Codex skill shim", "runtime adapter", the node identifier) and misses common variations like "review-fix loop", "clean runs", or "run reviews locally".

3 / 5

Distinctiveness Conflict Risk

The uniquely named niche ("node_local_review", "OmniMarket local review loop", Codex runtime adapter) gives it distinct triggers with minimal overlap risk against any other skill.

5 / 5

Total

14

/

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/local-review/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.