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

70%

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

The canonical home for this skill is oma-observability in first-fluke/oh-my-agent

SKILL.md
Quality
Evals
Security

Quality

Content

71%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-structured router skill: explicit conditional-loading discipline, a strong intent-to-resource routes table, concrete named standards and checks, and clear validation checkpoints with partial-success exit criteria. Its main weaknesses are structural redundancy (the scheduling/scaffolding sections restate the routing content several times) and the complete deferral of executable substance to resource files with no inline example to ground the guardrails.

Suggestions

Consolidate the redundant workflow articulations: intent classification appears in Goal, Intent signature, When to use, Entry, the Actions table, and the Canonical workflow path; a single flow (one classify step feeding the Routes table) would cut significant tokens.

Drop the 'SSL primitive' column from the Actions table: labels like SELECT/READ/INFER/VALIDATE add formalism without executable value, and the Action and Evidence columns already carry the meaning.

Inline one small concrete artifact (e.g., a burn-rate alert YAML fragment or a minimal OTLP collector config) so guardrails like 'deliver working configuration' are grounded in an executable example rather than fully deferred to resources/.

DimensionReasoningScore

Conciseness

The body is dense tables and terse bullets with no explanations of concepts Claude already knows, but intent classification is restated in at least five places (Goal, Intent signature, When to use, Entry step 1, Actions row 1, Canonical workflow path step 1), and the 'SSL primitive' column (SELECT/READ/INFER/VALIDATE/WRITE/NOTIFY) adds formalism without executable value. This fits 'mostly efficient but could be tightened' rather than 2 (no padded concept explanation) or 4 (the structural duplication exceeds minor).

3 / 5

Actionability

As an instruction-only router, the guidance is concrete: each intent maps to a named file ('resources/incident-forensics.md (MRA + 6-dim localization)'), specific technologies are named (W3C Trace Context, PrometheusRule CRD, OpenSLO YAML, burn-rate alerts), and there is a concrete invocation example ('/oma-observability --investigate "5xx spike in checkout"') and live-status URL. It is not 5 because no executable snippet exists and the operational 'how' is entirely deferred to resource files; not 3 because the routing and check guidance is specific and directly followable.

4 / 5

Workflow Clarity

A clear sequence is present (Entry, PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE scenes, Exit criteria) with explicit validation checkpoints ('Before declaring a setup complete, verify pipeline health, clock synchronization, cardinality limits, and retention'; VERIFY scene; 'Run resources/checklist.md §1 Setup validation'), a failure-and-recovery section, and explicit partial-success criteria. It is not 5 because verification is declarative rather than a concrete validate->fix->re-check loop, and the verification mechanics are deferred to checklist.md; not 3 because checkpoints are explicit and abundant, not implicit.

4 / 5

Progressive Disclosure

The body is a clean overview-plus-index: a categorized References section lists ~30 one-level-deep resource files, the Routes table maps each intent to a specific primary and fallback file, and loading discipline is explicit ('The reference list is an index, not a preload list'; 'Do not load all transport, layer, boundary, and signal guides together'; 'Read only relevant matrix rows'). This matches the 'clear overview with well-signaled one-level-deep references' anchor. No bundle files were provided, so the referenced files' existence could not be verified; the score reflects the structure as written.

5 / 5

Total

16

/

20

Passed

Description

55%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 states a clear, reasonably specific 'what' in third person, but omits any 'use when' trigger guidance and lacks the domain's most natural keywords (observability, monitoring, metrics/logs/traces, OTel). Distinctiveness is moderate: SLOs anchor it in observability, but 'incident diagnostics' and 'telemetry' create real overlap risk with debugging and incident-response skills.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger situations, e.g. 'Use when setting up OTel pipelines, designing SLOs and burn-rate alerts, tuning collector transport, or running telemetry-based incident forensics.'

Include natural trigger terms users would actually say: 'observability', 'monitoring', 'metrics, logs, traces', 'OpenTelemetry/OTel', 'APM', 'dashboards', 'alerting', alongside the current telemetry/SLO vocabulary.

Reduce conflict risk by narrowing 'incident diagnostics' to telemetry-based localization (e.g. 'localize incidents from traces, logs, and metrics') so it does not compete with debugging or incident-response/on-call skills.

DimensionReasoningScore

Specificity

"Design or troubleshoot telemetry, SLOs, and incident diagnostics" names three concrete actions (design, troubleshoot, route) across specific domains (telemetry, SLOs, incident diagnostics, signals, boundaries), matching the 'several specific actions; minor gaps' anchor. It is not 5 because coverage is incomplete (no mention of metrics/logs/traces, OTel, observability-as-code) and not 3 because more than 1-2 actions are explicitly listed.

4 / 5

Completeness

The 'what' is clear ("Design or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system boundary, or vendor guide"), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the 'when' is entirely absent rather than merely implicit-but-stated.

3 / 5

Trigger Term Quality

Relevant keywords like "telemetry", "SLOs", and "incident diagnostics" are present, but the most natural user vocabulary is missing: "observability" (the skill's own name), "monitoring", "metrics", "logs", "traces", "OTel/OpenTelemetry", "dashboards", "alerting". This fits 'some relevant keywords but missing common variations or synonyms' rather than 4, where only a few natural terms would be missing.

3 / 5

Distinctiveness Conflict Risk

"SLOs" is distinctively observability, but "troubleshoot ... incident diagnostics" overlaps with debugging and incident-response skills (the body itself lists oma-debug and PagerDuty-style paging as siblings/adjacent), and "telemetry" overlaps with data-pipeline and IoT telemetry skills. This fits 'somewhat specific but could still overlap with similar skills' rather than 4, where overlap risk would be minor.

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

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