CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-e2e-tests

Use when a developer wants to add, write, or create an end-to-end test for an Opik feature, page, or branch — e.g. "add an e2e test for the experiments comparison page", "write a test for the feature I just built", "e2e test for this branch", "cover the dataset items flow with a test". Runs the full loop in tests_end_to_end/e2e/ — analyze the feature and frontend code, explore the live UI with the Playwright MCP, write the Page Object Model + spec, and run it locally until green.

75

Quality

94%

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

88%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, highly actionable skill body: concrete commands, an explicit gated workflow with feedback loops and a done-checklist, and clean delegation to referenced materials. The main weaknesses are mild verbosity in places and a key reference (conventions.md) that is not bundled with the skill.

Suggestions

Tighten the anti-patterns table and step rationale to bare assertions — e.g. drop 'What renders is the only source of truth for selectors' and similar explanatory tails — to recover tokens without losing the rule.

Bundle conventions.md (or inline its must-follow rules) so the skill is self-contained; currently the body repeatedly defers to a file that is not present in the skill package.

The FE rebuild/docker section is long and operational; consider moving the network-note troubleshooting into a reference file and keeping only the core rebuild commands inline.

DimensionReasoningScore

Conciseness

Mostly efficient and domain-specific with little generic explanation Claude already knows, but a few rationale sentences in the anti-patterns table and step prose could be trimmed without losing clarity.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — `npx playwright test ...`, the docker compose rebuild sequence, `tag_lint.py`, `npx tsc --noEmit`, and the config heredoc — covering the common cases concretely.

5 / 5

Workflow Clarity

A clear 5-step loop with a dot graph, explicit GATE checkpoints, a run-until-green feedback loop, a safety gate before seeding, and a three-check done checklist — validation is present for the batch/destructive operations, so no cap applies.

5 / 5

Progressive Disclosure

Clear overview with well-signaled one-level references (conventions.md, taxonomy.yaml, release-gate-contract.md, the playwright-pom-discovery skill), but conventions.md is heavily relied on yet not bundled in the skill package, leaving a minor organization gap.

4 / 5

Total

18

/

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, exemplary description: concrete actions, multiple natural trigger phrases, and explicit what/when guidance in third person. It is specific enough to be unmistakable and concise enough to avoid padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'analyze the feature and frontend code, explore the live UI with the Playwright MCP, write the Page Object Model + spec, and run it locally until green' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (the full loop: analyze, explore UI, write POM+spec, run until green) and 'when' via a 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes several natural phrases a developer would actually say — 'add an e2e test for the experiments comparison page', 'write a test for the feature I just built', 'e2e test for this branch' — with synonyms (add/write/create/cover).

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (end-to-end tests for Opik features/pages/branches in a specific suite) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

Total

15

/

16

Passed

Repository
comet-ml/opik
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.