BC percy-migration-skill
Migrate visual regression testing from BrowserStack Percy (web, Percy on Automate, App Percy, Storybook, static snapshots, uploads) to TestMu AI SmartUI in any language or framework: Playwright, Cypress, Selenium (JS, Python, Java, C#, Ruby), Puppeteer, WebdriverIO, TestCafe, Capybara, Appium, Storybook. Use whenever someone wants to move from Percy to SmartUI or LambdaTest, mentions @percy/cli, percy exec, percySnapshot, percyScreenshot, PERCY_TOKEN, .percy.yml, App Percy or Percy baselines, or asks for the SmartUI equivalent of a Percy command, option or SDK call.
Migrate visual regression testing from BrowserStack Percy (web, Percy on Automate, App Percy, Storybook, static snapshots, uploads) to TestMu AI SmartUI in…
As a process C 53/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 · 0
✓ No critical or high findings
Files scanned: 4. 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 53/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
- 30Running it twice. 10 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 85Steps. 21 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1890 tokens
- 100Progress reporting. Reports progress
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 572: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.