Agent skill · Testing & QA

azure-resource-manager-playwright-dotnet

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

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill azure-resource-manager-playwright-dotnet --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/azure-resource-manager-playwright-dotnet/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Azure.ResourceManager.Playwright (.NET) Management plane SDK for provisioning and managing Microsoft Playwright Testing workspaces via Azure Resource Manager. > **⚠️ Management vs Test Execution** > - **This SDK (Azure.ResourceManager.Playwright)**: Create workspaces, manage quotas, check name availability > - **Test Execution SDK (Azure.Developer.MicrosoftPlaywrightTesting.NUnit)**: Run Playwright tests at scale on cloud browsers ## Installation ```bash dotnet add package Azure.ResourceManager.Playwright dotnet add package Azure.Identity ``` **Current Versions**: Stable v1.0.0, Preview v1.0.0-beta.1 ## Environment Variables ```bash AZURE_SUBSCRIPTION_ID=<your-subscription-id> # For service principal auth (optional) AZURE_TENANT_ID=<tenant-id> AZURE_CLIENT_ID=<client-id> AZURE_CLIENT_SECRET=<client-secret> ``` ## Authentication ```csharp using Azure.Identity; using Azure.ResourceManager; using Azure.ResourceManager.Playwright; // Always use DefaultAzureCredential var credential = new DefaultAzureCredential(); var armClient = new ArmClient(credential); // Get subscription var subscriptionId = Environment.GetEnvironmentVariable("AZURE_SUBSCRIPTION_ID"); var subscription = armClient

What's inside
Steps it walks through
  1. Installation
  2. Environment Variables
  3. Authentication
  4. Resource Hierarchy
  5. Core Workflow
  6. 1. Create Playwright Workspace
  7. 2. Get Existing Workspace
  8. 3. List Workspaces
  9. 4. Update Workspace
  10. 5. Check Name Availability
  11. 6. Get Quota Information
  12. 7. Delete Workspace
  13. Key Types Reference
  14. Workspace Properties
Commands it runs
dotnet add package Azure.ResourceManager.Playwright
dotnet add package Azure.Identity
For service principal auth (optional)
More from agentic-awesome-skills
All skills →
leiloeiro-editalAnalise e auditoria de editais de leilao judicial e extrajudicial. Riscos ocultos, clausulas…Otherdiagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug…Code Review & Qualityfind-complementary-foundersUse when an owner explicitly asks for a cofounder or project partner, or explicitly says they need…AI & Agentslinkedin-content-generatorAI-powered LinkedIn content suite: generate posts, carousels, newsletters, and 30-day calendars…Content & Marketingagent-orchestratorMeta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por…AI & Agentsseo-fundamentalsCore principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality…Code Review & Quality
About this skill
What does the azure-resource-manager-playwright-dotnet skill do?

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

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill azure-resource-manager-playwright-dotnet --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.