test-observability

Integrate Playwright tests with OpenTelemetry, Grafana, Prometheus, Loki, and Tempo. Use when debugging test failures across distributed systems, measuring test performance, creating test dashboards, or correlating tests with backend traces.

Quality

81%

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

63%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 highly actionable with concrete code for the whole stack, but it is verbose in places and its progressive disclosure is broken: the referenced bundle files are absent and their content is inlined. Fixing the dangling references and trimming marketing prose would materially raise quality.

Suggestions

Create the referenced files (references/tracetest-integration.md, references/otel-reporter-setup.md, references/grafana-dashboards.md, dashboards/test-results-dashboard.json) or remove the References section so navigation is not broken.

Move the Tracetest, Grafana dashboard, Log Correlation, and Alerting detail into those reference files, keeping SKILL.md a lean overview with one-level-deep pointers.

Delete the 'Benefits' bullet list and the closing tagline ('Test observability transforms debugging from guesswork to precision...') — they are marketing prose that adds tokens without instructional value.

Fix the log-correlation example so it imports and uses the same exporter (resolve the OTLPLogExporter import vs. OTLPLogTransport usage inconsistency).

Dimension	Reasoning	Score
Conciseness	Mostly efficient code/config, but the ~430-line body carries padding that does not teach Claude anything new — the 'Benefits' bullet list ('80% faster debugging'), the marketing-style closing tagline, and several explanatory intros could be trimmed.	3 / 5
Actionability	Abundant copy-paste-ready code and commands across OTEL reporter, Tracetest, Grafana, Railway, log correlation, and alerting; the main gap is the log-correlation example importing OTLPLogExporter but instantiating an undefined OTLPLogTransport.	4 / 5
Workflow Clarity	Clear numbered sequences in Quick Start (install → configure → run → view) and the Debugging with Traces workflow, plus a Verify Connection checkpoint (curl expecting 200 OK); minor validation gaps but no destructive/batch cap applies.	4 / 5
Progressive Disclosure	Section structure is reasonable and references are clearly signaled, but the referenced files (references/.md, dashboards/.json) do not exist and the detail they should hold (Tracetest setup, OTEL config, Grafana dashboards) is inlined in the body rather than split out.	3 / 5
	Total	14 / 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 strong: third-person voice, concrete actions, explicit 'Use when...' triggers, and a distinct, well-scoped niche. It answers both what and when without padding.

Dimension	Reasoning	Score
Specificity	Names the domain (Playwright tests integrated with OpenTelemetry, Grafana, Prometheus, Loki, Tempo) and lists multiple concrete actions — integrate, debug test failures, measure performance, create dashboards, correlate tests with backend traces — giving comprehensive coverage.	5 / 5
Completeness	Explicitly states both what it does ('Integrate Playwright tests with OpenTelemetry, Grafana, Prometheus, Loki, and Tempo') and when to use it via a 'Use when...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases a user would actually say are well covered — 'debugging test failures across distributed systems', 'measuring test performance', 'creating test dashboards', 'correlating tests with backend traces' — alongside the named tooling.	5 / 5
Distinctiveness Conflict Risk	A clear niche — Playwright test observability across a specific OTEL/Grafana/Prometheus/Loki/Tempo stack — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/test-observability/SKILL.md
Commit: 93ed392

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.