CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gap

Thin Codex skill shim for node_gap_compute. Use when running OmniNode integration gap detection, report classification, or gap-cycle preflight.

Quality

77%

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/gap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 dense, actionable dispatch guide with a concrete command, complete argument reference, and explicit response-handling rules. Its main weaknesses are token duplication between the generated Runtime truth block and the Contract section, and the absence of a worked payload example that would make the dispatch command copy-paste ready.

Suggestions

Deduplicate the command-name and topic metadata that appears in both the generated "Runtime truth" section and the "Contract" section (e.g., the gap-compute-start/completed topics), keeping one authoritative location and pointing to it from the other.

Add one concrete example payload for the common case (e.g., subcommand detect with a scope) so the dispatch command is copy-paste ready rather than requiring the reader to assemble JSON from the field list.

Trim the runtime-evidence/binding-field enumerations (terminal_selection values, wire-schema semantics) to what a dispatch decision actually needs, or move the full detail into a reference file.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence with no basic-concept padding, but the generated "Runtime truth" block ("Adapter transport command topic: onex.cmd.omnimarket.pattern-b-dispatch.v1" etc.) duplicates command/topic metadata that reappears nearly verbatim in the "Contract" section, and the evidence-schema/binding-field enumerations could be tightened.

3 / 5

Actionability

Provides a concrete dispatch command ("env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name \"gap_compute\" ..."), a complete arguments table with defaults, an explicit payload field mapping, and clear response handling ("If ok is false, surface error.code and error.message directly"). The placeholder '--payload \'<json-payload>\'' with no worked example payload keeps it from being fully copy-paste ready.

4 / 5

Workflow Clarity

The workflow is legible (map arguments to payload, optional --compile-only preflight validation, dispatch via the wrapper, then check ok and read output_payloads[0] or surface the error), and compile-only is an explicit validation checkpoint. It falls short of 5 because the sequence is implicit rather than ordered and there is no recovery loop beyond surfacing errors.

4 / 5

Progressive Disclosure

A single self-contained SKILL.md with clear, well-labeled sections (Arguments, Runtime truth, Dispatch, Contract, Output) and no nested or buried references; the referenced scripts/run_codex_runtime_request.py lives in the target repo, not the bundle. The ~40-line generated contract metadata block is arguably reference material inlined in the overview, which is a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

78%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 concise, explicit, and highly distinctive, with a clear Use-when trigger clause covering detection, classification, and preflight. Its only weakness is incomplete capability coverage — the fix, reconcile, and cycle subcommands from the body are absent, leaving the what-side thin.

DimensionReasoningScore

Specificity

"Thin Codex skill shim for node_gap_compute" names the mechanism and "gap detection, report classification, or gap-cycle preflight" lists several concrete actions. It is not 5 because coverage is incomplete — the fix, reconcile, and cycle subcommands documented in the body are unmentioned.

4 / 5

Completeness

Both what ("Thin Codex skill shim for node_gap_compute") and when ("Use when running OmniNode integration gap detection, report classification, or gap-cycle preflight") are present, with an explicit Use-when clause. It falls short of 5 because the what is thin — the actual capabilities only appear inside the when-clause and omit fix/reconcile.

4 / 5

Trigger Term Quality

"gap detection", "report classification", and "gap-cycle preflight" are natural phrases a user in this domain would say, matching anchor 4's "good keyword coverage; a few natural terms missing" — users asking to "fix gaps" or "reconcile a gap report" would not trigger it.

4 / 5

Distinctiveness Conflict Risk

"node_gap_compute", "OmniNode", and "gap-cycle" carve out a clear niche with distinct triggers; no plausible competing skill would match these phrases, so conflict risk is minimal.

5 / 5

Total

17

/

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/gap/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.