otel-ruby

OpenTelemetry in Ruby — SDK setup, manual tracing, experimental metrics and logs, Bundler integration, contrib instrumentation for Rails/Rack/Sinatra/Sidekiq and other gems, propagation, performance, and upgrades. Use when adding, reviewing, configuring, or troubleshooting OpenTelemetry in a Ruby or Rails service. Triggers on "setup otel in ruby", "ruby telemetry", "Rails OpenTelemetry", "OpenTelemetry::SDK.configure", "opentelemetry-instrumentation-all", "Ruby tracing", "Rack otel", "Sidekiq otel", or any Ruby-related OTel question.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%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.

An exemplary router-style SKILL.md: lean, precisely structured, with executable lookup commands and flawless progressive disclosure to real, self-contained reference files. The only weakness is the inline dated version snapshot, which is time-sensitive information sitting outside a deprecation/old-patterns section.

Suggestions

Move the 'Released snapshot verified 2026-10-03' version table into references/breaking-changes.md (or a dedicated 'audit anchor' section), keeping only the lookup commands in the body so version drift doesn't erode the top-level file.

Optionally add one sentence under References stating what to do when a task spans multiple references (e.g., setup plus instrumentation selection), to make the routing rule total.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-assumed (tables of commands, no concept explanations, no filler), but the 'Released snapshot verified 2026-10-03' block embeds ten-plus specific version numbers and a date outside any old-patterns/deprecated section, which the rubric flags as time-sensitive padding that could be trimmed or relocated.	4 / 5
Actionability	Provides copy-paste-ready commands ('gh api repos/open-telemetry/opentelemetry-ruby/releases --paginate', 'gem specification <gem> dependencies --remote --yaml'), a precise per-task routing table, and a concrete gem-resolution procedure. As an index-style skill with actionable guidance, the absence of inline Ruby code is not penalized per the rubric's scoring notes.	5 / 5
Workflow Clarity	The body is under 50 lines with a single unambiguous action — 'Load only the reference that matches the task' backed by a use-when table mapping each task to one file. The simple-skill exception applies, and there are no destructive or batch operations that would require validation checkpoints.	5 / 5
Progressive Disclosure	Clear overview with five well-signaled, one-level-deep references, each verified to exist in references/ and each paired with an explicit 'Use when' condition. Content is appropriately split and navigation is trivial.	5 / 5
	Total	19 / 20 Passed

Description

100%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.

An excellent description: dense with concrete capabilities, natural trigger phrases including synonyms and gem/class identifiers, an explicit use-when clause, and a tightly scoped niche that minimizes mis-triggering. No fluff or over-claims despite its length.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — 'SDK setup, manual tracing, experimental metrics and logs, Bundler integration, contrib instrumentation for Rails/Rack/Sinatra/Sidekiq..., propagation, performance, and upgrades' — with comprehensive coverage and no vague filler.	5 / 5
Completeness	Explicitly answers both what (the enumerated capability list) and when ('Use when adding, reviewing, configuring, or troubleshooting OpenTelemetry in a Ruby or Rails service') with concrete trigger phrases. Third-person voice is maintained throughout.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases including synonyms and concrete identifiers: 'setup otel in ruby', 'ruby telemetry', 'Rails OpenTelemetry', 'OpenTelemetry::SDK.configure', 'opentelemetry-instrumentation-all', 'Ruby tracing', 'Rack otel', 'Sidekiq otel' — exactly what a user would say.	5 / 5
Distinctiveness Conflict Risk	A clear Ruby/Rails-scoped niche with distinct, Ruby-bound triggers; even the catch-all 'any Ruby-related OTel question' is scoped to Ruby, keeping conflict with sibling otel-* skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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: ollygarden/opentelemetry-agent-skills
Path: skills/otel-ruby/SKILL.md
Commit: ea1a940

Reviewed: 18 hours ago

Table of Contents

Discovery Implementation Validation

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.