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

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 navigation hub that routes tasks to self-contained references with concrete lookup commands and a clear task→file table. Its main weakness is the hard-coded version snapshot, which spends tokens on time-sensitive data outside a deprecated section.

Suggestions

Move the 'Released snapshot verified 2026-09-03' version table into a reference (e.g. breaking-changes.md) or a clearly labeled audit/deprecated section, and keep SKILL.md pointing to the live 'gh api' lookups to avoid stale version tokens.

Add an explicit validation checkpoint to the upgrade workflow (e.g. 'after Bundler resolves, diff Gemfile.lock and confirm each changed gem against its changelog before proceeding').

Consider folding the one-line 'Signal stability matters' summary into the references table or setup.md so the overview stays purely navigational.

Dimension	Reasoning	Score
Conciseness	The body is a lean index that assumes competence and avoids explaining OTel basics, but the 'Released snapshot verified 2026-09-03' block hard-codes many time-sensitive version numbers outside a deprecated/old-patterns section, adding tokens that will stale.	4 / 5
Actionability	Provides concrete executable lookups ('gh api repos/open-telemetry/opentelemetry-ruby/releases --paginate', 'gem specification <gem> dependencies --remote --yaml') plus a task→file mapping table, though the bulk of executable setup guidance lives in the references rather than inline.	4 / 5
Workflow Clarity	The references table gives a clear task→reference routing sequence and the upgrade guidance is sequenced ('Resolve each gem independently... inspect its changelog, and keep the resulting Gemfile.lock change under review'), but explicit validation/checkpoint steps for the upgrade flow are only implied.	4 / 5
Progressive Disclosure	Clear one-level-deep structure: a concise overview with a well-signaled references table (file + 'Use when'), all five referenced files present in references/, and detail appropriately split out rather than inlined.	5 / 5
	Total	17 / 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.

The description is exemplary: third-person voice, comprehensive concrete capabilities, explicit 'Use when' trigger guidance, and natural trigger terms including synonyms and technical identifiers. It cleanly satisfies every dimension.

Dimension	Reasoning	Score
Specificity	Names many concrete actions — 'SDK setup, manual tracing, experimental metrics and logs, Bundler integration, contrib instrumentation... propagation, performance, and upgrades' — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both what (the enumerated capabilities) and when ('Use when adding, reviewing, configuring, or troubleshooting OpenTelemetry in a Ruby or Rails service') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Lists natural phrases users would say ('setup otel in ruby', 'ruby telemetry', 'Rails OpenTelemetry', 'Ruby tracing', 'Rack otel', 'Sidekiq otel') alongside technical identifiers, covering synonyms and gem names.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to Ruby/Rails OpenTelemetry with Ruby-specific triggers and gem names, creating a clear niche with minimal overlap risk against other-language OTel skills.	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: 1bf950f

Reviewed: 1 day 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.