What does this skill do, and when should you use it?
This skill is for .NET developers managing Microsoft Playwright Testing through the Azure management plane. It covers workspace creation, retrieval, updates, deletion, name-availability checks, and subscription- or workspace-level quota inspection. It explicitly does not run Playwright tests; test execution belongs to the separate Azure.Developer.MicrosoftPlaywrightTesting.NUnit SDK. The guidance includes Azure authentication, resource hierarchy, asynchronous ARM operations, error handling, and configuring the data-plane URI.
It guides an agent to install Azure.ResourceManager.Playwright and Azure.Identity, create an ArmClient with DefaultAzureCredential, locate an Azure subscription and resource group, and perform Playwright workspace CRUD operations through PlaywrightWorkspaceResource. It also shows how to check workspace-name availability, read subscription and workspace quotas, handle RequestFailedException, and preserve DataplaneUri for test-execution configuration.
- A .NET Azure developer needs to provision a Microsoft Playwright Testing workspace in a resource group and wants ARM-based C# code.
- A platform engineer needs to enumerate Playwright workspaces across a resource group or subscription and inspect provisioning state.
- A team wants to validate a workspace name before provisioning a new resource.
- An operations or development team needs to inspect quotas or update workspace tags.
- A developer has created a workspace and needs to pass its data-plane URI into Playwright test configuration.
How do you install this skill?
- Workspace deletion is destructive; add explicit user confirmation, scope review, and a recovery or backup strategy before use.
- Verify that Azure.ResourceManager.Playwright 1.0.0, API version 2025-09-01, and all shown types and methods are available in the target environment.
- Document least-privilege RBAC, authentication and authorization failures, missing subscription-ID validation, regional differences, and Azure China cloud applicability.
- The supplied CI and test materials are general repository infrastructure and do not prove execution coverage for this skill path.
- Shell / CLI
- Network access
.NETAzure.ResourceManager.PlaywrightAzure.Identity
Run npx skills add microsoft/skills and select this skill in the wizard. The README says skills are installed into the selected agent directory, such as .github/skills/ for GitHub Copilot. The source does not provide a dedicated installation command for this individual skill.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/microsoft/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/.github/plugins/azure-sdk-dotnet/skills/azure-resource-manager-playwright-dotnet" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- create a Playwright Testing workspace
- check Playwright workspace name availability.
With the skill installed, use a prompt such as “create a Playwright Testing workspace” or “check Playwright workspace name availability.” A .NET project should add dotnet add package Azure.ResourceManager.Playwright and dotnet add package Azure.Identity, set AZURE_SUBSCRIPTION_ID, and authenticate with DefaultAzureCredential or a specific Azure credential. Do not use this skill to run Playwright tests; use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that purpose.
What are this skill's strengths and limitations?
- Covers concrete ARM operations: workspace CRUD, name availability, and quota queries.
- Includes copyable asynchronous C# examples, resource hierarchy guidance, and ARM error handling.
- Clearly separates management-plane work from test execution, reducing package-selection mistakes.
- Uses DefaultAzureCredential and demonstrates both resource-group and subscription-level access.
- It is limited to Microsoft Playwright Testing management-plane operations and does not execute tests.
- It requires an Azure subscription, credentials, and network access; the source does not specify minimum RBAC permissions.
- The source provides no independent test-coverage or compatibility result for this specific skill.
- The source does not provide pricing information for Azure resources or the testing service.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Azure Playwright Workspace Manager this page ✓ Microsoft · Official | 54 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Fabric Capacity Manager for .NET ✓ Microsoft · Official | 53 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Azure API Management for .NET ✓ Microsoft · Official | 48 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Azure Redis Management for .NET ✓ Microsoft · Official | 48 · Use with care | ★ 2.7k | 3mo ago | MIT |
| MongoDB Atlas Azure ARM Manager ✓ Microsoft · Official | 51 · Use with care | ★ 2.7k | 3mo ago | MIT |
The skill explicitly distinguishes Azure.ResourceManager.Playwright from Azure.Developer.MicrosoftPlaywrightTesting.NUnit: the former manages workspaces and quotas, while the latter runs NUnit Playwright tests on cloud browsers.
How did FollowSkills review this skill?
The skill uses DefaultAzureCredential, environment variables, and avoids hardcoded keys, while clearly separating management-plane and test-execution responsibilities. However, create, update, and delete operations require no user confirmation; deletion has no rollback or recovery guidance; and permission scope, token data flow, and sensitive-output handling are not sufficiently disclosed, so points are deducted.
Installation, authentication, resource hierarchy, major CRUD paths, quotas, asynchronous operations, and RequestFailedException handling are documented with generally diagnosable feedback. Static review provides no executable reproduction or skill-specific tests, and the document lacks handling for missing subscription IDs, authorization failures, timeouts, partial failures, and API-version compatibility, so the score remains below the static ceiling.
The name, audience, management-plane scope, trigger phrases, and non-fit boundary with the NUnit test-execution SDK are reasonably clear. Inputs, required RBAC, regional/cloud differences, behavior outside Azure or when Azure is unreachable, and Chinese-language usage guidance are incomplete, limiting environment-fit confidence.
The SKILL.md has clear progressive sections for installation, authentication, hierarchy, workflows, types, best practices, and errors, with MIT, author, version metadata, and related documentation links. Version wording is somewhat ambiguous between stable and preview, and there is no changelog, explicit maintenance owner/update path, dependency version constraint, or FAQ, so points are deducted.
The skill provides directly usable .NET examples for workspace creation, retrieval, listing, updating, name checks, quota reads, and deletion, and distinguishes management-plane from data-plane use. However, no real outputs or target-path tests are statically verifiable; correctness, API availability, and production readiness still require manual validation, with limited coverage of idempotency conflicts, authorization, and recovery.
The skill gives concrete package names, types, resource provider, API version, and official documentation links, while the repository includes general CI and test infrastructure. The supplied material does not show skill-specific acceptance tests, real CI coverage, or third-party execution evidence, so the evidence is only partially auditable.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →