CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-observability

Design or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system boundary, or vendor guide.

Quality

60%

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 ./skills/oma-observability/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 well-organized intent router with strong guardrails, explicit validation stages, and a clear reference index, but it suffers from redundant workflow restatements and DSL-style ceremony that inflate token cost. More critically, every route and instruction terminates in resources/ files that are missing from the bundle, so the skill's operating model dead-ends in practice.

Suggestions

Collapse the three parallel workflow descriptions (Entry, Scenes PREPARE-FINALIZE, Canonical workflow path) into one authoritative sequence and remove the 'SSL primitive' and 'Resource scope' ceremony tables to reclaim token budget.

Ship the referenced bundle: the 35+ resources/ files cited by the Routes table, Dependencies, and References (e.g. execution-protocol.md, matrix.md, vendor-categories.md) are absent, so every route and the checklist-driven verification cannot execute.

Inline at least one minimal concrete artifact (e.g. an SLO burn-rate alert rule snippet or a worked example of routed output) so the skill delivers standalone value when the external files are unavailable.

DimensionReasoningScore

Conciseness

The same workflow is described three times (Entry, Scenes PREPARE-FINALIZE, and 'Canonical workflow path'), routing targets are repeated across 'When to use', the Routes table, 'Invocation and loading', and References, and the 'SSL primitive' and 'Resource scope' tables add ceremony without actionable value — several padded sections despite otherwise dense tables. Not 1 because no already-known concepts are re-explained.

2 / 5

Actionability

Concrete routing guidance exists (per-intent Routes table, guardrail checks like "clock synchronization, cardinality limits, and retention", an invocation example), but every executable step terminates in a resources/ file that is absent from the bundle, and no config or output example is inlined, leaving the guidance incomplete as written.

3 / 5

Workflow Clarity

A clear sequence is present with a dedicated VERIFY stage, a failure-and-recovery section, "Record checks that could not run", and partial-success exit criteria — checkpoints are all present. Not 5 because the steps carry no executable commands and the triplicated workflow descriptions (Entry / Scenes / Canonical path) blur which flow is authoritative.

4 / 5

Progressive Disclosure

The in-body structure is well organized (categorized References index, per-intent route table, explicit "Do not load all transport, layer, boundary, and signal guides together"), but none of the 35+ referenced resources/ files exist in the bundle, so every reference is dangling and the progressive-disclosure design cannot actually function. Not 4 because references do not resolve to real files.

3 / 5

Total

12

/

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 concise and identifies a clear observability niche, but it under-sells the skill's actual scope and omits an explicit use-when trigger clause plus the domain's most common keywords (observability, monitoring, metrics, logs, traces, OTel). It reads as a serviceable but incomplete router summary rather than a strong trigger surface.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations, e.g. setting up OTel Collector pipelines, debugging a production incident with traces/logs, choosing an APM vendor, or writing SLO burn-rate alerts.

Include the natural terms users actually say — "observability", "monitoring", "metrics", "logs", "traces", "OpenTelemetry/OTel", "APM", "dashboards" — rather than only telemetry/SLO/incident vocabulary.

Expand the action list to reflect full scope (e.g. design observability pipelines, tune collection transport, localize incidents across 6 dimensions, write observability-as-code) instead of the generic "Design or troubleshoot".

DimensionReasoningScore

Specificity

The description names its domain ("telemetry, SLOs, and incident diagnostics") and 2-3 actions ("Design or troubleshoot", "Route to the relevant signal, system boundary, or vendor guide"), but the verbs are generic and major scope items (metrics, logs, traces, dashboards, OTel, alerting) are unmentioned, matching the 'domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

The 'what' is clear ("Design or troubleshoot telemetry, SLOs, and incident diagnostics"), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the second sentence ("Route to the relevant signal...") describes an action the skill performs, not when to invoke it, so completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes some relevant keywords ("telemetry", "SLOs", "incident diagnostics") but misses the most natural terms users say in this domain — "observability", "monitoring", "metrics", "logs", "traces", "OpenTelemetry/OTel", "APM", "dashboards" — which is more than 'a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

"Telemetry, SLOs, and incident diagnostics" carves a mostly distinct observability niche, but "incident diagnostics" overlaps with general debugging skills (including the ecosystem's own oma-debug per the body), and the absent "observability" keyword weakens the distinct trigger set, leaving minor overlap risk.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

first-fluke/oh-my-agent

Path

skills/oma-observability/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.