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.

72

Quality

89%

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

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 overview skill that defers detail to real reference files and gives concrete, executable source-of-truth commands. Minor tightening of the evidence gate and more executable snippets in the body would push it higher.

Suggestions

Consolidate the three 'For ... state that ...' bullets in the evidence gate into a single compact checklist to reduce repetition and token cost.

Add one short inline code snippet showing a minimal WebTracerProvider setup so the body is actionable even before the reader opens setup-sdk.md.

Number the browser-specific gates or label them as validation checkpoints to make the workflow sequence and feedback loop more explicit.

DimensionReasoningScore

Conciseness

Lean and dense with no padding of concepts Claude already knows; each line (gates, routing, commands) earns its place, though the evidence-gate bullets are somewhat repetitive and could be tightened slightly.

4 / 5

Actionability

Provides copy-paste executable commands (`gh api ...`, `npm view ...`, `WebFetch ...`) and concrete browser-specific gates, but some guidance is routing/direction rather than executable code, leaving minor gaps.

4 / 5

Workflow Clarity

Sequenced from safety gate through references, models, conventions, browser gates, and a fetch-then-answer Sources-of-Truth loop with explicit checkpoints; not a numbered destructive workflow, so it sits just below the explicit-validation-recovery anchor.

4 / 5

Progressive Disclosure

A clear overview with a References table routing to three confirmed one-level-deep bundle files and cross-references to sibling skills; content is appropriately split and easy to navigate.

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.

A strong, third-person description that concisely states what the skill covers, gives rich natural trigger terms, and draws a clear boundary against adjacent skills. It avoids fluff and over-claims entirely.

DimensionReasoningScore

Specificity

Names the domain (browser/RUM for SPAs/MPAs) and multiple concrete mechanics and primitives such as `sdk-trace-web`, `WebTracerProvider`, sessions, clicks, and console capture — comprehensive coverage of the niche.

5 / 5

Completeness

Explicitly answers both 'what' (browser/RUM mechanics for SPAs and MPAs) and 'when' (a 'Use for...' clause listing concrete triggers), and adds an explicit out-of-scope boundary.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases ('browser OTel,' 'frontend observability,' 'Web Vitals,' page-load, route tracing, clicks, console capture, JS errors) plus technical identifiers and an explicit 'Not for Node.js' exclusion; synonyms and file/package names included.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct browser-only triggers and an explicit exclusion of Node.js service instrumentation and Collector-only config, minimizing overlap with sibling otel-js/otel-collector skills.

5 / 5

Total

20

/

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.