Name: azure-microsoft-playwright-testing-ts
Rating: 58.4 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-microsoft-playwright-testing-ts

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/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

Quality

Content

68%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 content is highly actionable with copy-paste-ready code and CI examples, but repeats config blocks unnecessarily and lacks validation/verification checkpoints for its batch test-execution workflow. Structure is good but could push more reference material into separate files.

Suggestions

De-duplicate the repeated Entra ID service-config block — show it once and reference it from the Authentication, Core Workflow, and Azure Reporter sections to recover token budget.

Add an explicit validation/verification step for test runs (e.g. how to confirm a run reported to the Azure portal and what to do on failure) so the batch workflow clears the workflow-clarity cap.

Move the configuration-options type reference and migration table into a separate reference file linked from the body, pushing progressive disclosure toward 5.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with no concept-explanation padding, but the Entra ID service-config block is repeated near-verbatim across Authentication, Core Workflow, and Azure Reporter sections, which is unnecessary token spend; this fits the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor rather than the lean 4.	3 / 5
Actionability	Install commands, env vars, full TypeScript config snippets, CI/CD YAML, a migration table, and before/after examples are all copy-paste ready and cover the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	Sections are sequenced (Install → Env → Auth → Config → Run → CI/CD), but running tests at scale is a batch operation with no explicit validation/verification checkpoint or validate→fix→retry loop; the destructive/batch cap holds workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized with clear section headers and one-level-deep migration/before-after structure, but the ~300-line body with an inline config-options reference and migration table could be split out, fitting 'good structure; minor organization gaps' rather than the cleanly-split 5.	4 / 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 natural trigger terms. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when running Playwright tests at scale in Azure, or when the user mentions cloud-hosted browsers, Azure Playwright, or Playwright Service.'

Add a couple of natural synonyms/file cues (e.g. 'E2E tests', '.spec.ts') to broaden trigger-term coverage toward a 5.

Optionally enumerate one or two more concrete actions (e.g. 'collect run artifacts', 'view results in the Azure portal') to push specificity from 4 toward 5.

Dimension	Reasoning	Score
Specificity	"Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting" names several concrete capabilities (scale execution, cloud browsers, portal reporting) with only minor coverage gaps, fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	The description gives a clear 'what' but no 'when'/'Use when' trigger clause; per the judging guidelines a missing explicit trigger guidance caps completeness at 3, so it does not reach the 4 anchor.	3 / 5
Trigger Term Quality	"Playwright tests", "cloud-hosted browsers", and "Azure portal reporting" are natural phrases users would say, but common synonyms or file-extension variants (e.g. ".spec.ts", E2E) are absent, matching the 'good coverage; a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The Azure-Playwright cloud-testing niche with portal reporting is fairly distinct with only minor overlap risk against generic Playwright skills, fitting the 'mostly distinct; minor overlap risk' anchor rather than the clearly-niched 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-microsoft-playwright-testing-ts/SKILL.md
Commit: 57c135b

Reviewed: 18 hours ago

Table of Contents

Discovery Implementation Validation

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.