CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

phoenix-playwright-tests

Write Playwright E2E tests for the Phoenix AI observability platform. Use when creating, updating, or debugging Playwright tests, or when the user asks about testing UI features, writing E2E tests, or automating browser interactions for Phoenix.

Quality

81%

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

71%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 highly actionable, Phoenix-specific playbook whose code examples and commands are copy-paste ready and whose debugging workflow is well sequenced with feedback loops. Its weaknesses are redundancy with generic Playwright knowledge repeated across sections and a monolithic single-file structure that inlines material better kept in one-level-deep reference files.

Suggestions

Split the 'Debugging Flaky Tests' deep-dive and the 'Phoenix-Specific Pages' catalog into reference files (e.g., references/debugging-flaky-tests.md, references/pages.md) and link them from a short overview section, keeping SKILL.md to the core writing patterns.

Remove or consolidate generic Playwright material Claude already knows — the Assertions section and the repeated role-selector-priority guidance (stated in Selector Patterns, UI Exploration, and Test Stability Best Practices) — keeping only the Phoenix-specific deviations.

Add an explicit validation checkpoint to the authoring workflow, e.g., after writing a test, build and run it once with '--reporter=list' to confirm it passes before considering it done.

DimensionReasoningScore

Conciseness

The body is code-heavy and free of padded prose, but it restates generic Playwright knowledge Claude already has (the Assertions section, role-selector priority basics) and repeats guidance across sections — the submenu getByRole rule appears in both Common UI Patterns and the flaky-patterns table, and selector priority is stated three times. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is above 2 because there is no concept-explaining padding and most content is project-specific.

3 / 5

Actionability

Everything is executable: a copy-paste login/template, an exact credentials table, concrete selector snippets for every pattern, exact run commands with reporter/CI flags ('pnpm exec playwright test tests/server-evaluators.spec.ts --project=chromium --reporter=list'), and even grep commands for debugging. This matches the 'fully executable; copy-paste ready; covers common cases' anchor.

5 / 5

Workflow Clarity

The debugging workflow is a clear 5-step sequence with a re-run feedback loop ('for i in 1 2 3 4 5; do ...') and error-driven iteration, and running tests has an explicit build-first precondition. It falls to 4 rather than 5 because the primary authoring workflow lacks explicit checkpoints (e.g., verifying a newly written test passes before moving on), leaving minor validation gaps.

4 / 5

Progressive Disclosure

No bundle files exist, so all ~430 lines are inlined in one well-headered file; the debugging-flakiness deep-dive (~110 lines) and the Phoenix page catalog are natural candidates for separate reference files. The only file reference points to another skill's bundle ('references/test-ids.md in the phoenix-frontend skill'), which is not part of this skill. This matches 'some structure but could be better organized; content that should be separate is inline' rather than 4, since a substantial portion of reference material is inlined.

3 / 5

Total

15

/

20

Passed

Description

87%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 description that states a concrete capability and gives explicit, multi-phrase trigger guidance, with a clearly scoped niche. Its only weakness is slightly thin synonym coverage (e.g., 'end-to-end', file extensions) in the trigger terms.

DimensionReasoningScore

Specificity

Names the domain ('Playwright E2E tests for the Phoenix AI observability platform') and several concrete actions ('creating, updating, or debugging Playwright tests'), matching the 'several specific actions; minor gaps' anchor. It is not 5 because the actions are lifecycle variants of a single writing activity rather than a comprehensive list of distinct capabilities.

4 / 5

Completeness

Explicitly answers both questions: the 'what' ('Write Playwright E2E tests for the Phoenix AI observability platform') and a concrete 'when' ('Use when creating, updating, or debugging Playwright tests, or when the user asks about testing UI features, writing E2E tests, or automating browser interactions for Phoenix'). This matches the anchor requiring clear what AND when with concrete trigger phrases; level 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say: 'Playwright', 'E2E tests', 'testing UI features', 'automating browser interactions', 'Phoenix'. It falls short of the 5 anchor because common synonyms and extensions like 'end-to-end tests' or '.spec.ts' are absent, though it clearly exceeds the 'some relevant keywords but missing variations' level.

4 / 5

Distinctiveness Conflict Risk

The pairing of Playwright E2E testing with the Phoenix platform creates a clear niche with distinct, specific triggers, and every clause is scoped 'for Phoenix', giving minimal conflict risk with generic testing or frontend skills. It is above the 4 anchor because the platform qualifier removes even the minor overlap a generic Playwright skill would have.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

Arize-ai/phoenix

Path

.agents/skills/phoenix-playwright-tests/SKILL.md

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.