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.

79

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable SKILL.md body with a gated, feedback-driven workflow and clean progressive-disclosure design. The one real defect is packaging, not authoring: the repeatedly-referenced conventions.md is absent from the bundle.

Suggestions

Ship the referenced conventions.md inside the skill bundle — the body points to it six times ('Read conventions.md before writing any POM or spec') but no conventions.md exists under references/, scripts/, assets/, or the bundle root, so the one-level-deep reference is currently a dead link. Verify release-gate-contract.md likewise resolves from the consuming repo.

DimensionReasoningScore

Conciseness

Dense, repo-specific operational knowledge with no generic concept explanations Claude already knows; the only mild redundancy is the DOT graph restating the numbered steps, but it earns its place as a compact visual overview.

3 / 3

Actionability

Provides copy-paste-ready executable commands throughout (npx playwright test …, docker compose build/recreate with pull_policy override, the grep-based data-testid verify, the ~/.opik.config heredoc) plus concrete import paths and file conventions.

3 / 3

Workflow Clarity

A clearly sequenced 5-step loop with explicit gates at Steps 1 and 3, a run-until-green feedback loop, and verification steps (data-testid grep check, ~/.opik.config safety check) guarding the destructive-risk seed operation.

3 / 3

Progressive Disclosure

Overview plus a well-signaled one-level-deep reference to conventions.md and delegation to the playwright-pom-discovery skill; content is appropriately split rather than inlined, matching the score-3 anchor on structure and signaling.

3 / 3

Total

12

/

12

Passed

Description

100%

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 'Use when' triggers, concrete example phrasings, and a clear what-and-when structure tightly scoped to Opik E2E testing. No voice or over-claim issues.

DimensionReasoningScore

Specificity

Lists multiple specific 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' — matching the score-3 anchor rather than the domain-only level 2.

3 / 3

Completeness

Explicitly answers both 'when' ('Use when a developer wants to add, write, or create an end-to-end test…') and 'what' ('Runs the full loop…analyze…explore…write…run') with explicit triggers.

3 / 3

Trigger Term Quality

Quotes natural phrasings 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'), giving good coverage of real trigger terms.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'an end-to-end test for an Opik feature, page, or branch' — a clear niche with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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: 5 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.