CtrlK
BlogDocsLog inGet started
Tessl Logo

playwright-trace

Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./node_modules/.pnpm/playwright-core@1.59.1/node_modules/playwright-core/lib/tools/trace/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Scale 1-5

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

This is a strong, well-crafted skill that provides comprehensive CLI reference for Playwright trace inspection. It excels in actionability with fully executable commands covering all subcommands and their flags. The structure flows logically from workflow overview to command reference to a practical investigation walkthrough, though the investigation section slightly overlaps with the workflow section.

DimensionReasoningScore

Conciseness

The content is efficient and avoids explaining what Playwright or traces are. Minor verbosity in the 'Typical investigation' section which somewhat repeats the workflow section, but overall each section earns its place with concrete commands.

4 / 5

Actionability

Every command is fully executable and copy-paste ready with clear CLI syntax. The skill covers all common cases with specific flags and options, including advanced snapshot queries with eval expressions and element refs.

5 / 5

Workflow Clarity

The workflow section provides a clear numbered sequence, and the 'Typical investigation' section reinforces it with a concrete example. However, there are no explicit validation checkpoints or error recovery steps (e.g., what to do if open fails or if a snapshot phase doesn't exist). Since this is a read-only inspection tool (non-destructive), the missing feedback loops are less critical.

4 / 5

Progressive Disclosure

Content is well-structured with clear section headers progressing from overview to individual commands to a full investigation example. For a standalone skill with no bundle files, the organization is appropriate. Minor improvement could be made by separating the lengthy command reference into a separate file, but the current length (~120 lines) is manageable.

4 / 5

Total

17

/

20

Passed

Description

75%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 in specificity and distinctiveness, clearly naming the tool (Playwright), the artifact (trace files), and multiple concrete inspection actions. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding trigger guidance and a few more natural synonyms would make it excellent.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to inspect, debug, or analyze Playwright trace files or .zip trace archives.'

Include additional natural trigger terms like 'debug test', 'trace.zip', 'test recording', or 'Playwright test results' to capture more user phrasings.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: list actions, view requests, console, errors, snapshots, and screenshots. Also specifies the domain (Playwright trace files) and the context (command line).

5 / 5

Completeness

Clearly answers 'what' (inspect Playwright trace files with specific sub-actions), but there is no explicit 'Use when...' clause or equivalent trigger guidance. Per rubric guidelines, this caps completeness at 3.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'Playwright', 'trace files', 'snapshots', 'screenshots', 'console', 'errors', 'requests', and 'command line'. Missing some variations like '.zip trace', 'trace.zip', 'debug test', or 'test recording' that users might naturally say.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive — 'Playwright trace files' is a very specific niche. Unlikely to conflict with other skills since it targets a particular tool (Playwright) and a particular artifact (trace files) via command line.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
stevenknowswhy/ForhemitComing
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.