BC azure-playwright-migration-skill
Migrate test automation from Azure Playwright Workspaces / Microsoft Playwright Testing to TestMu AI (formerly LambdaTest) in any language or framework. Covers playwright.service.config.ts with @azure/playwright createAzurePlaywrightConfig (or the retired @azure/microsoft-playwright- testing getServiceConfig), PLAYWRIGHT_SERVICE_URL, Entra ID or access-token auth, exposeNetwork, the Azure reporter. Use this whenever someone wants to move, switch, port, migrate or point tests from Azure Playwright Workspaces to TestMu AI or LambdaTest, asks what the TestMu or LT:Options equivalent is for a capability, config, CLI flag or API from Azure Playwright Workspaces, mentions playwright.service.config, @azure/playwright, createAzurePlaywrightConfig, @azure/microsoft-playwright-testing, getServiceConfig, PLAYWRIGHT_SERVICE_URL, PLAYWRIGHT_SERVICE_ACCESS_TOKEN, ServiceOS, or wants a migration plan, estimate, PR or checklist for a repo currently on Azure Playwright Workspaces, even without the word migrate.
Migrate test automation from Azure Playwright Workspaces / Microsoft Playwright Testing to TestMu AI (formerly LambdaTest) in any language or framework.
As a process C 58/100 · Has gaps — References files that are not bundled: ../shared/testmu-cloud-reference.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-usereference/testmu-target.md:277Credential used in a network call (verify the destination is the intended service) (test fixture / example file; the skill's own vendor host)curl -u "$LT_USERNAME:$LT_ACCESS_KEY" -X POST "https://manual-api.lambdatest.com/app/upload/realDevice" -F "appFile=@app.apk" -F "name=myapp"
fixturevendor-host
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../shared/testmu-cloud-reference.md - note
frontmatter-keyunknown frontmatter key "languages"
Process rating: all ten parameters 58/100
- 0Tools and files. 1 referenced file(s) missing: ../shared/testmu-cloud-reference.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4535 tokens
- 85Steps. 45 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1009: 120–800 characters recommended
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.