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.

68

Quality

86%

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

75%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, well-structured reference for writing Phoenix Playwright tests with concrete code and commands throughout. Its main weakness is redundancy across sections that inflates length without adding capability.

Suggestions

Consolidate the duplicated selector mappings: the "UI Exploration" table repeats the same getByRole patterns already given in "Selector Patterns", so fold them into one section.

De-duplicate the anti-pattern guidance: the "use getByRole not getByText" and "avoid waitForTimeout" rules appear in inline comments, the submenu example, and the Debugging section — state each once and reference it.

Move the long "Debugging Flaky Tests" reference (lessons, workflow, pattern table) into a bundled reference file so SKILL.md stays a lean overview with a one-level-deep pointer.

DimensionReasoningScore

Conciseness

Mostly actionable code and tables rather than concept fluff, but selector guidance is duplicated between the "Selector Patterns" and "UI Exploration" sections, and the waitForTimeout/getByRole anti-patterns are repeated across inline comments and the Debugging section, so it could be tightened.

3 / 5

Actionability

Abundant copy-paste-ready TypeScript snippets, concrete selector examples in priority order, exact pnpm commands, and specific test credentials, fully covering the common cases.

5 / 5

Workflow Clarity

The debugging workflow is a clear numbered sequence with a trace-on-failure feedback loop, and the run-tests flow correctly sequences build before run; minor validation gaps remain in the main authoring flow.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with tables for quick lookup; the only external reference (references/test-ids.md) is a cross-skill pointer rather than a bundled file, and the 420-line body could shed bulk by splitting the debugging/selector reference into separate files.

4 / 5

Total

16

/

20

Passed

Description

95%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 clearly states both what the skill does and when to invoke it, with natural trigger phrasing and a well-scoped niche. Only minor room to broaden the concrete action list.

DimensionReasoningScore

Specificity

Names the domain ("Phoenix AI observability platform", Playwright) and several concrete actions ("creating, updating, or debugging Playwright tests", "automating browser interactions"), with only minor coverage gaps relative to the comprehensive anchor 5.

4 / 5

Completeness

Explicitly states what ("Write Playwright E2E tests for the Phoenix AI observability platform") and when ("Use when creating, updating, or debugging Playwright tests, or when the user asks about...") with concrete trigger phrases, matching the anchor 5 example.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger phrases with synonyms ("Playwright tests", "E2E tests", "testing UI features", "automating browser interactions") that a user would naturally say, matching the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

Scoped to a named platform plus a specific framework, giving it a clear niche with distinct triggers and minimal conflict risk against generic testing skills.

5 / 5

Total

19

/

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.