CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

observability-sink

Thin Codex skill shim for node_observability_sink_effect. Use when persisting OmniNode observability events through runtime adapters.

Quality

72%

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/observability-sink/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 body delivers executable dispatch guidance with useful validation modes (compile-only preflight, side-effect-free smoke, runtime evidence inspection) and is well organized as a single-file skill. Its main weaknesses are duplicated contract metadata between the generated block and the Contract section, a missing concrete example payload, and no error-recovery loop after a failed dispatch.

Suggestions

Deduplicate the contract metadata (command name, command topic, terminal topic) that appears in both the Runtime truth block and the "## Contract" section, keeping a single authoritative source.

Add a filled-in example JSON payload for a typical dispatch so the "<json-payload>" placeholder becomes copy-paste ready.

Add a brief recovery step for the ok-is-false path (e.g., fix the payload or binding and re-run with --compile-only before retrying) to close the feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean and operational, but contract facts (command name, contract command topic, terminal topic) are duplicated between the generated "Runtime truth" block and the "## Contract" section, and the generated block carries dense enum/schema detail (terminal_selection values, runtime-evidence/v2) that could be consolidated. This matches anchor 3 (mostly efficient but could be tightened) rather than anchor 4, since the redundancy spans whole sections.

3 / 5

Actionability

The dispatch command is executable and specific ("env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name 'observability_sink_effect' ..."), with concrete flags for --compile-only and --target-runtime-address, an explicit payload field mapping, and defined output/error handling. It falls short of anchor 5 because "'<json-payload>'" is an unfilled placeholder with no concrete example payload for the common case.

4 / 5

Workflow Clarity

The workflow is clear and sequenced (run from the omnimarket repo, map inputs to the payload, optional --compile-only preflight, dispatch, check ok/output_payloads, render result fields) with real validation checkpoints including compile-only, runtime_evidence inspection, and a side-effect-free smoke mode. It misses anchor 5 because there is no fix-and-retry feedback loop when ok is false — the guidance stops at surfacing error.code and error.message.

4 / 5

Progressive Disclosure

The skill is a single well-sectioned file with no bundle directories and no nested references, and the generator-owned runtime-truth block is clearly delimited and needed at dispatch time. This matches anchor 4 (good structure, content appropriately placed, minor organization gaps) rather than anchor 3, since nothing here clearly belongs in a separate file given the bundle contains only SKILL.md.

4 / 5

Total

15

/

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 is highly distinctive within its niche, but it is jargon-heavy and states only one concrete action. It is serviceable for users already inside this codebase, yet natural trigger coverage and a fuller statement of capabilities would improve it.

Suggestions

Add one or two more concrete capability statements (e.g., what persistence sinks are used or what is returned) so the "what" goes beyond "thin shim".

Include natural trigger phrasing users would actually say, such as "persist", "save", "store", or "sink observability events", alongside the existing jargon.

State the outcome of using the skill (e.g., events persisted via Kafka/PostgreSQL adapters and a persistence result returned) to strengthen completeness.

DimensionReasoningScore

Specificity

"Thin Codex skill shim for node_observability_sink_effect" names the domain and "persisting OmniNode observability events through runtime adapters" states one concrete action, but the description lists no broader set of concrete capabilities. It sits above anchor 2 (a concrete action is explicitly stated) but below anchor 4 (not several specific actions).

3 / 5

Completeness

The "what" is present ("Thin Codex skill shim for node_observability_sink_effect") and the "when" is explicit ("Use when persisting OmniNode observability events through runtime adapters"). It falls short of anchor 5 because the "what" states the skill's role rather than explicitly enumerating its concrete capabilities alongside the trigger.

4 / 5

Trigger Term Quality

Terms like "persisting", "observability events", and "runtime adapters" are relevant to the domain, but the phrasing leans on internal jargon ("Codex skill shim", "node_observability_sink_effect") and misses natural synonyms such as "save", "store", "sink", or "telemetry". This matches anchor 3 (some relevant keywords, missing common variations) rather than anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"node_observability_sink_effect", "OmniNode", and "Codex runtime adapters" define a highly specific internal niche, making accidental triggering for unrelated skills very unlikely. This clearly matches anchor 5's clear niche with distinct triggers rather than anchor 4's minor overlap risk.

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/observability-sink/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.