CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ticket-pipeline

Thin Codex skill shim for node_ticket_pipeline. Use to run the bounded per-ticket pipeline slice through the OmniMarket runtime adapter.

Quality

66%

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 ./plugins/onex/skills/ticket-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 tightly written, highly actionable dispatch guide with a real preflight checkpoint and clear output-handling rules — its main strengths. Its weaknesses are structural: a large generated contract block is misplaced under the Arguments section and duplicated verbatim in the Contract section, and deep evidence-schema detail is inlined where reference material belongs. Moving the contract/evidence metadata into a single deduplicated section (or a reference file) would resolve both the conciseness and organization issues.

Suggestions

Deduplicate the contract metadata: the "Runtime truth" block and the "Contract" section repeat the command name, wrapper script, and both topics — keep one authoritative location.

Move the generated runtime-truth block out from under "## Arguments" so the argument table directly follows its heading, or relocate that metadata to a references/ file with a one-line pointer.

Trim over-detailed dispatch-irrelevant material (e.g. the terminal_selection enum list and evidence wire schema v2 semantics) to a short 'inspect runtime_evidence' note, and add one fully assembled example payload with concrete values.

DimensionReasoningScore

Conciseness

The body is dense and free of beginner-concept padding, but the ~38-line generated "Runtime truth" block is almost wholly duplicated by the later "Contract" section (command name, wrapper script, both topics, backing node all repeated), and details like the full terminal_selection enum and evidence-schema v2 semantics exceed what dispatch requires. This is 'mostly efficient but could be tightened', below the minor-trim level 4 and well above the padded level 2.

3 / 5

Actionability

The dispatch command is concrete and nearly complete ("env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name \"ticket_pipeline\" --payload '<json-payload>' --timeout-ms 600000"), with an exact payload JSON shape, an argument table with defaults, and explicit output/error handling rules. It misses 5 only because placeholders like '<json-payload>' and '<TICKET-ID>' are never assembled into one fully copy-paste-ready worked example.

4 / 5

Workflow Clarity

The dispatch flow is clear and includes real checkpoints: "--compile-only" preflight that "validates the payload, command topic, response topic, correlation id, timeout, and target runtime address", plus explicit error handling ("If ok is false, surface error.code and error.message"). It sits at 4 rather than 5 because payload construction is presented after the dispatch command, and the error path gives no fix/retry loop.

4 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/), so everything lives in one SKILL.md with headers — but at ~110 lines the generated contract metadata (~38 lines) is inlined under the "## Arguments" heading, separating the argument table from its own header, and is then duplicated in a separate "Contract" section. This matches 'some structure but could be better organized; content that should be separate is inline', below the well-placed level 4.

3 / 5

Total

14

/

20

Passed

Description

53%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 short, specific to its niche, and low-conflict, but it reads as internal jargon rather than user-facing trigger language. It states what the skill does without any explicit 'use when' guidance, so a user (or Claude) relying on natural trigger phrases would struggle to select it. Adding trigger conditions and natural synonyms would lift the completeness and trigger-term dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to run, resume, or dry-run a ticket through the OmniMarket ticket pipeline (e.g. 'run the pipeline for TICKET-123')", to raise completeness.

Include natural synonyms and variations users would say — "ticket pipeline", "run ticket", "resume pipeline phase", "pipeline dry run" — instead of internal terms like "shim" and "bounded slice".

Name one or two more concrete capabilities (e.g. compile-only preflight validation, phase resume via skip_to) so the 'what' is more than a single action.

DimensionReasoningScore

Specificity

The description names its domain ("node_ticket_pipeline", "OmniMarket runtime adapter") and one concrete action ("run the bounded per-ticket pipeline slice"), matching the 'domain plus 1-2 concrete actions' anchor. It does not list several specific actions, so it falls below 4, and its single action is more concrete than the generic 'names the domain only' level 2.

3 / 5

Completeness

The 'what' is stated (a thin shim that runs the bounded per-ticket pipeline slice through the runtime adapter), but 'when' is only weakly implied by the purpose phrasing "Use to run..." — there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the trigger conditions are entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

"ticket pipeline", "per-ticket", and "pipeline run" are relevant keywords a user in this ecosystem might say, but coverage stops there — no synonyms or variations, and the rest is internal jargon ("Codex skill shim", "runtime adapter") users would not naturally say. This fits 'some relevant keywords but missing common variations', below the good-coverage level 4 and above the generic level 2.

3 / 5

Distinctiveness Conflict Risk

Naming "node_ticket_pipeline", "OmniMarket", and the Codex adapter gives it a clear, highly specific niche with minimal conflict risk against generic skills. It stops short of 5 because it offers no distinct trigger phrases to distinguish it from sibling OmniMarket node-shim skills, leaving minor overlap risk with closely related pipeline skills.

4 / 5

Total

13

/

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/ticket-pipeline/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.