CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

otel-browser

OpenTelemetry browser/RUM mechanics for SPAs and MPAs. Use for “browser OTel,” “frontend observability,” “Web Vitals,” `sdk-trace-web`, `WebTracerProvider`, `browser-sdk`, browser instrumentations, page-load or route tracing, sessions, clicks, console capture, JavaScript errors, or frontend-to-backend trace correlation. Browser telemetry is privacy- and volume-sensitive, and experimental packages move quickly. Not for Node.js service instrumentation or Collector-only configuration.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

A well-structured routing/overview skill: real one-level-deep references, concrete verification commands, and explicit safety checkpoints. The main cost is redundancy in the safety-gate section and inline time-sensitive version detail that the skill itself delegates to references.

Suggestions

Collapse the 'Safety and evidence gate' prose and bullet checklist into one form — keep the explicit pre-finalize checklist and trim the paragraphs it restates, or vice versa.

Move the dated stability/version facts (release tags, verification dates) entirely into references/setup-sdk.md's stability section, leaving only a one-line pointer in the body.

Trim the repeated pointers to references/instrumentation.md in 'Semantic conventions and package routing', since the References table already routes readers there.

DimensionReasoningScore

Conciseness

The body is dense and free of beginner-concept padding, but the 'Safety and evidence gate' bullets largely restate the paragraphs immediately above them, and dated version snapshots ('Verified 2026-10-21', 'browser-instrumentation-v0.9.0') sit inline in the stability note and package-routing section rather than being fully delegated to references/setup-sdk.md. This is more than 'minor instances' of over-explanation, so it sits below the 4 anchor.

3 / 5

Actionability

The Sources of Truth table gives copy-paste commands (`gh api repos/open-telemetry/opentelemetry-browser/releases -q '.[].tag_name'`, `npm view @opentelemetry/browser-sdk version`, a WebFetch URL) and the gates name specific knobs (`propagateTraceHeaderCorsUrls`, `visibilitychange`/`pagehide`, `traceparent`). Minor gaps: no quick-start code snippet inline, and some directives are directional rather than executable ('Bound queues, batches, resource timing').

4 / 5

Workflow Clarity

A clear pre-finalize checkpoint exists ('Before finalizing an answer, make the applicable gates explicit') with an explicit three-case checklist, and the semantic-conventions section gives a decision procedure (catalog instrumentation -> verify released shape -> bounded custom names). The sections are thematic rather than a sequenced end-to-end workflow, and there are no validate/fix/retry feedback loops, keeping it below 5.

4 / 5

Progressive Disclosure

Verified all three referenced files exist (references/setup-sdk.md, instrumentation.md, performance.md) and are one level deep; cross-references between them are sibling-level, not nested. The References table with a 'Use when' column provides clear navigation, and the body stays a genuine overview with detail (setup, catalogs, budgets) properly split into the bundle files.

5 / 5

Total

16

/

20

Passed

Description

95%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 exemplary description: explicit 'Use for' triggers with natural user phrasing and package names, a clear scope statement, and explicit exclusions that de-conflict it from adjacent skills. The only soft spot is that capabilities are phrased as topic areas rather than actions, which slightly limits specificity.

DimensionReasoningScore

Specificity

The description enumerates many concrete areas — 'page-load or route tracing, sessions, clicks, console capture, JavaScript errors, or frontend-to-backend trace correlation' — but frames them as topic 'mechanics' rather than concrete actions, a minor gap versus the 5 anchor's action-verb coverage. It is well above the 3 anchor's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both: what ('OpenTelemetry browser/RUM mechanics for SPAs and MPAs') and when ('Use for...') with a long list of concrete trigger phrases, plus explicit exclusions ('Not for Node.js service instrumentation or Collector-only configuration'). The 'Use when' clause is present and highly specific, so the 3-cap for missing triggers does not apply.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage: users' phrasings ('browser OTel', 'frontend observability', 'Web Vitals', 'JavaScript errors') plus the specific package and class names they would paste (`sdk-trace-web`, `WebTracerProvider`, `browser-sdk`). Synonyms and both SPA/MPA framings are present, matching the 5 anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (browser/RUM telemetry) with distinct package-name triggers, and the 'Not for Node.js service instrumentation or Collector-only configuration' boundary explicitly prevents overlap with the closest sibling skills. Minimal conflict risk, matching the 5 anchor.

5 / 5

Total

19

/

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

ollygarden/opentelemetry-agent-skills

Path

skills/otel-browser/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.