CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-microsoft-playwright-testing-ts

Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting.

59

Quality

69%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-microsoft-playwright-testing-ts/SKILL.md

The canonical home for this skill is azure-microsoft-playwright-testing-ts in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

The body is highly actionable with complete, executable examples across auth, config, and CI/CD, but it lacks validation feedback loops for its batch test-execution workflow and inlines a large amount of reference content that would benefit from being split into referenced files.

Suggestions

Add a validation/feedback step after 'Run Tests' — e.g. inspect failed-test output and retry with `--last-failed` — to lift workflow clarity above the batch-operation cap.

Move the CI/CD examples, Key Types, and Configuration Options into files under references/ and link to them from the body to improve progressive disclosure.

Quarantine all time-sensitive details (retirement date, version thresholds) into the existing Migration section so the core workflow stays evergreen.

DimensionReasoningScore

Conciseness

The body is code-heavy and largely lean, explaining little that Claude already knows; the only friction is time-sensitive material (the March 8, 2026 retirement date and version requirements 1.47+/1.57+) placed mostly in a migration section rather than fully quarantined, keeping it just below level 5.

4 / 5

Actionability

Provides copy-paste-ready, executable TypeScript configs, bash commands, CI/CD YAML, and a manual-connection example that cover the common cases end-to-end, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Sections sequence install → env → auth → config → run, but running tests at scale is a batch operation with no validation or failure-retry checkpoint, so per the rubric's batch-operation cap workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

The ~300-line SKILL.md is well-sectioned but inlines substantial reference material (CI/CD examples, Key Types, Configuration Options, the migration table) that belongs in separate files, and no bundle files or external references exist to split the content.

3 / 5

Total

15

/

20

Passed

Description

66%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.

The description is specific and distinct, naming concrete capabilities tied to Azure Playwright Testing, but it omits any 'Use when...' trigger guidance, which caps its completeness. Adding an explicit usage-trigger clause would raise both completeness and distinctiveness.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when running Playwright tests against Azure-hosted browsers, scaling test execution, or sending results to the Azure portal.'

Add natural synonyms users might say — 'E2E tests', 'browser automation', 'Azure Playwright' — to broaden trigger-term coverage.

Mention the package name '@azure/playwright' so the description matches how users reference the skill.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Run Playwright tests at scale', 'cloud-hosted browsers', 'integrated Azure portal reporting' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive level 5.

4 / 5

Completeness

The 'what' is clear ('Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting') but there is no 'Use when...' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Playwright tests', 'at scale', 'Azure portal reporting') but omits common synonyms like 'E2E tests', 'browser automation', or package names, so it sits at good-but-not-comprehensive keyword coverage.

4 / 5

Distinctiveness Conflict Risk

The Azure-portal + cloud-hosted-browser framing carves a clear niche distinct from a generic Playwright skill, with only minor overlap risk against closely related testing skills; it stops short of level 5 due to the absent explicit trigger phrase.

4 / 5

Total

15

/

20

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.