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 ./src/omnimarket/adapters/codex/skills/observability-sink/SKILL.md

The canonical home for this skill is observability-sink in OmniNode-ai/omnimarket

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 mostly executable, well-structured guidance with genuine validation checkpoints (compile-only preflight, error surfacing). The main costs are redundancy — contract metadata and payload field names each appear twice — and a missing example payload plus post-run verification loop.

Suggestions

Deduplicate the Contract section by either removing it or reducing it to only facts not already in the generated runtime-truth block (backing node path and wrapper path).

Add one concrete example JSON payload (with correlation_id, session_id, events, sink flags, submitted_at) next to the dispatch command so the common case is copy-paste ready.

Move the generated 'Runtime truth' block out from under the '## Arguments' heading into its own section so the arguments table is immediately discoverable, and add a post-run verification step (e.g., check persisted_event_count matches the submitted events).

DimensionReasoningScore

Conciseness

The body is mostly efficient (tables, commands, bullets, no explanations of known concepts), but the Contract section repeats the command name, backing node, and both topics already stated verbatim in the generated runtime-truth block, and the payload field list re-lists the six field names from the arguments table. This duplication is more than the 'minor instances' of anchor 4.

3 / 5

Actionability

Provides an executable dispatch command with flags, an argument table with defaults, and explicit error handling ('If ok is false, surface error.code and error.message'). It falls short of anchor 5 because '--payload <json-payload>' is a placeholder with no concrete example payload for the common case.

4 / 5

Workflow Clarity

The sequence is clear — map inputs to payload, optional --compile-only preflight that validates payload/topics/correlation id, dispatch, then interpret output — so the batch-operation validation cap does not apply. It is below anchor 5 because there is no failure-recovery or post-run verification loop (e.g., confirm persisted_event_count against the submitted events).

4 / 5

Progressive Disclosure

The skill is appropriately self-contained with no bundle files and clear section structure. It misses anchor 5 because the generated 'Runtime truth' block sits under the '## Arguments' heading despite not describing arguments, a real organization gap.

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 is highly distinctive with an explicit 'Use when' trigger and a concrete, jargon-appropriate domain. Its weaknesses are thin action coverage (one verb, 'persisting') and sparse natural keyword variations, leaving a user few alternative phrasings to trigger it.

Suggestions

Enumerate the concrete capabilities in the description (e.g., 'persist events to Kafka and PostgreSQL sinks, validate payloads with compile-only preflight, inspect runtime evidence') to raise specificity beyond a single action verb.

Add natural keyword variations users might say, such as 'telemetry', 'metrics', 'traces', or 'observability persistence', so the trigger fires on more than one phrasing.

State what the skill does in action terms ('Persists ... events through ...') rather than only what it is ('Thin Codex skill shim') to sharpen the 'what' half of completeness.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action ('persisting OmniNode observability events through runtime adapters') but does not list several specific actions, matching the 1-2-concrete-actions anchor. It is above anchor 2 because it goes beyond merely naming a domain.

3 / 5

Completeness

Both parts are explicit: what ('Thin Codex skill shim for node_observability_sink_effect') and when ('Use when persisting OmniNode observability events through runtime adapters'). It falls short of anchor 5 because the 'what' states what the skill is rather than enumerating what it does, and the trigger phrases are not comprehensive.

4 / 5

Trigger Term Quality

'persisting observability events' is a natural phrase a user in this niche would say, but coverage stops there — no synonyms (telemetry, metrics, traces, logging) and the remainder is technical jargon ('Codex skill shim', 'runtime adapters'). This matches the some-relevant-keywords anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The ultra-specific identifiers ('node_observability_sink_effect', 'OmniNode') carve out a clear niche with essentially no overlap risk against other skills. It clearly fits the minimal-conflict anchor.

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