CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

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.

A well-structured, largely lean reference skill with concrete commands and explicit evidence-gating validation. Slight conciseness loss from restated gate clauses and a non-linear (decision-guide) workflow keep actionability and workflow_clarity at 4 rather than 5.

Suggestions

Collapse the "Safety and evidence gate" prose and its three enumerated sub-cases into a single list to remove the duplicated gating language and tighten conciseness.

Add a short explicit workflow ordering (e.g., a numbered "How to approach a browser-RUM task" sequence) so the decision-guide content reads as a sequenced process with clear validation checkpoints rather than parallel sections.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (tables, no OTel-explainer padding), but the "Safety and evidence gate" restates the same constraints twice — once as prose, then as three enumerated sub-cases — which is minor over-explanation that could be tightened.

4 / 5

Actionability

Provides concrete executable commands (`npm view ... version`, `gh api ... -q '.[].tag_name'`, `WebFetch https://opentelemetry.io/...`) and specific config directives (flush on `visibilitychange`/`pagehide`, scope `propagateTraceHeaderCorsUrls`), with only minor gaps since full config examples are deferred to references.

4 / 5

Workflow Clarity

A clear reading sequence (models → conventions → gates → sources of truth) with an explicit validation checkpoint ("State the evidence level: static review, observed ... or ... authorized live validation") and a before-finalizing gate checklist; minor validation gaps keep it just below a full feedback-loop workflow.

4 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references to three real files via a "Use when" table (references/setup-sdk.md, instrumentation.md, performance.md), plus cross-references to sibling skills — content is appropriately split and easy to navigate.

5 / 5

Total

17

/

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.

A strong, third-person description with explicit what/when triggers and a clear negative boundary. The only weakness is a topic-framing that lists domains rather than action verbs, slightly capping specificity.

DimensionReasoningScore

Specificity

Lists several concrete telemetry areas — "page-load or route tracing, sessions, clicks, console capture, JavaScript errors, ... frontend-to-backend trace correlation" — but frames them as topics/mechanics rather than explicit verbs, leaving minor action-coverage gaps versus a fully action-verb list.

4 / 5

Completeness

Explicitly answers both "what" (browser/RUM mechanics for SPAs and MPAs) and "when" ("Use for ..." with concrete trigger phrases), and adds a "Not for ..." boundary clause, matching the anchor for clearly answering both what and when.

5 / 5

Trigger Term Quality

Comprehensive natural and technical trigger terms including synonyms and package identifiers — "browser OTel," "frontend observability," "Web Vitals," `sdk-trace-web`, `WebTracerProvider`, `browser-sdk` — matching the anchor for full coverage of natural terms.

5 / 5

Distinctiveness Conflict Risk

Clear browser/RUM niche with distinct triggers and an explicit negative boundary ("Not for Node.js service instrumentation or Collector-only configuration") minimizing conflict with sibling otel skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ollygarden/opentelemetry-agent-skills
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.