CtrlK
BlogDocsLog inGet started
Tessl Logo

author-e2e-tests

Use when writing, debugging, or maintaining Playwright e2e tests for Positron -- new test files, test cases, flaky-test fixes, test infrastructure, or performance/metric tests.

76

Quality

93%

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

87%

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

A high-quality, lean body with executable templates, a fixture table, and well-signaled one-level-deep references to real bundle files. The only gap is the absence of explicit validation/feedback-loop checkpoints in its workflows.

Suggestions

Add an explicit validate->fix->retry checkpoint for test authoring, e.g. 'run the new test with --debug; if it flakes, fix the wait/selector rather than adding a timeout'.

For the performance/metric workflow, state the verification step explicitly (e.g. 're-run 5x to confirm the measurement is stable') so the sequence has a concrete checkpoint.

Promote the 'Common Mistakes' items into a short numbered checklist with a confirm step after writing each test, so the workflow carries an explicit feedback loop.

DimensionReasoningScore

Conciseness

Lean and efficient throughout -- no explanation of concepts Claude already knows; specifics like '~600ms of synthetic noise' and numeric-grid-cells-as-strings earn their place. Could not be meaningfully tightened without losing value.

3 / 3

Actionability

Fully executable guidance: a copy-paste test file template, a fixture table with exact call signatures, real `npx playwright test ...` commands, and a concrete performance timer recipe. Copy-paste ready.

3 / 3

Workflow Clarity

Sequences are clear (Start Here -> Critical structure -> fixtures -> POMs -> assertions -> running) and the performance section gives a recipe plus rationale, but there are no explicit validate/fix/retry checkpoints for the fragile operations (e.g. test authoring, POM method choice), which the rubric requires for a 3.

2 / 3

Progressive Disclosure

SKILL.md is a well-organized overview with a dedicated 'Progressive Documentation' section signaling one-level-deep references; all six referenced files exist and content is appropriately split rather than inlined.

3 / 3

Total

11

/

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 an explicit 'Use when...' trigger clause and a clear, specific niche. It names many concrete actions and natural trigger terms with no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions -- 'writing, debugging, or maintaining', 'new test files, test cases, flaky-test fixes, test infrastructure, or performance/metric tests' -- matching the rubric's 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (writing/debugging/maintaining Playwright e2e tests for Positron) and when via a 'Use when...' clause enumerating concrete triggers.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered -- 'writing', 'debugging', 'flaky-test fixes', 'test infrastructure', 'performance/metric tests' -- with no jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to 'Playwright e2e tests for Positron', a clear niche with distinct triggers unlikely to overlap with unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
posit-dev/positron
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.