Name: azure-resource-manager-playwright-dotnet
Rating: 48.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-resource-manager-playwright-dotnet

Azure Resource Manager SDK for Microsoft Playwright Testing in .NET.

Quality

53%

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-resource-manager-playwright-dotnet/SKILL.md

The canonical home for this skill is azure-resource-manager-playwright-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

57%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 comprehensive, executable examples across the management lifecycle, but it is verbose and inlines reference-type content that should be split into separate files. Validation checkpoints around destructive operations are implicit rather than explicit.

Suggestions

Move the Key Types Reference and Workspace Properties tables into a separate references file and link to it, trimming SKILL.md toward an overview.

Relocate version/API-date info into an explicitly labeled section (or old-patterns note) so time-sensitive details don't pad the main flow.

Add an explicit pre-delete validation checkpoint (e.g., confirm via ExistsAsync or a confirmation step) to the Delete Workspace workflow.

Dimension	Reasoning	Score
Conciseness	The ~300-line body includes several padded/duplicated sections (Key Types and Workspace Properties tables restate code, best-practices restate ARM idioms, a filler "When to Use" line) and inlines time-sensitive version info ("v1.0.0", "API Version: 2025-09-01") outside any old-patterns section, making it noticeably verbose.	2 / 5
Actionability	It provides copy-paste-ready, fully executable C# covering the full CRUD lifecycle (create, get, list, update, name-availability, quota, delete) with exact type names, property names, resource-type strings, and env vars, plus concrete error-handling guards.	5 / 5
Workflow Clarity	Core Workflow is numbered 1-7 and an Integration section gives an ordered 4-step sequence with an error-handling feedback section, but the destructive delete operation has no explicit validation checkpoint and main-lifecycle checkpoints are implicit, triggering the rubric's destructive-operation cap at 3.	3 / 5
Progressive Disclosure	No bundle files (references/scripts/assets) exist and all content is inlined in a ~300-line SKILL.md with API/type reference tables that belong in a separate file; section headers provide some structure, but reference material is not split out or signaled with one-level-deep internal links.	3 / 5
	Total	13 / 20 Passed

Description

48%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 clearly identifies a specific niche but only states what the SDK is, not what it does or when to use it. Adding concrete actions and an explicit "Use when..." trigger clause would substantially improve it.

Suggestions

Add concrete verbs to the description, e.g., "Provision and manage Microsoft Playwright Testing workspaces, quotas, and name availability via Azure Resource Manager in .NET."

Append an explicit trigger clause such as "Use when provisioning Azure Playwright Testing workspaces or managing ARM quotas, not for running tests."

Disambiguate from the sibling SDK by noting this is the management plane (e.g., "management plane SDK, not the test-execution SDK").

Dimension	Reasoning	Score
Specificity	The description names the domain ("Azure Resource Manager SDK for Microsoft Playwright Testing in .NET") but lists no concrete actions such as creating workspaces, managing quotas, or checking name availability, matching the anchor that names the domain with minimal/generic actions.	2 / 5
Completeness	It gives a clear "what" (an ARM SDK for Playwright Testing in .NET) but provides no "Use when..." or equivalent trigger guidance; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes recognizable product/tech keywords ("Azure Resource Manager", "Microsoft Playwright Testing", ".NET") but lacks natural verb phrases and synonyms a user would say (e.g., "provision Playwright workspaces", "manage Azure Playwright"), missing common variations.	3 / 5
Distinctiveness Conflict Risk	The niche is highly specific (ARM + Playwright Testing + .NET) and the "Resource Manager" framing signals the management plane, but the description does not disambiguate from the closely related sibling test-execution SDK, leaving a minor overlap risk.	4 / 5
	Total	12 / 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-resource-manager-playwright-dotnet/SKILL.md
Commit: 57c135b

Reviewed: 19 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.