SKILLEMALL.ai

BC aws-device-farm-migration-skill

Migrate test automation from AWS Device Farm to TestMu AI (formerly LambdaTest) in any language or framework. Covers Device Farm desktop browser testing (create_test_grid_url) and mobile runs with test spec YAML, DEVICEFARM_* env vars, device pools, Appium/Espresso/XCUITest/instrumentation uploads. Use this whenever someone wants to move, switch, port, migrate or point tests from AWS Device Farm to TestMu AI or LambdaTest, asks what the TestMu or LT:Options equivalent is for a capability, config, CLI flag or API from AWS Device Farm, mentions create_test_grid_url, CreateTestGridUrl, boto3 devicefarm, DEVICEFARM_DEVICE_NAME, DEVICEFARM_APP_PATH, test spec YAML with phases install/pre_test/test, appium --base-path, 127.0.0.1:4723 inside a Device Farm package, or wants a migration plan, estimate, PR or checklist for a repo currently on AWS Device Farm, even without the word migrate.

LambdaTest/agent-skills Agent Skills author: LambdaTest 7 files · 1 script body ≈ 4 504 tokens Open the sourcegithub.com↗ analyzed 34 h ago

Migrate test automation from AWS Device Farm 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

ProcedureAWSPlaywrightInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
98
Quality 40%
80
Run on models
none yet
Process rating
C
58/100
Has gaps
References files that are not bundled: ../shared/testmu-cloud-reference.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Result and completion w 14
60
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Exfiltration net-credential-use reference/aws-device-farm.md:68
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)
    Upload: `aws devicefarm create-upload --type ANDROID_APP` + `curl -T app.apk <presigned url>` -> `curl -u "$LT_USERNAME:$LT_ACCESS_KEY" -X POST https://manual-api.lambdatest.com/app/upload/realDevice 
    vendor-hostquoted
  • low Exfiltration net-credential-use reference/testmu-target.md:277
    Credential 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-ref reference to a missing file: ../shared/testmu-cloud-reference.md
  • note frontmatter-key unknown frontmatter key "languages"

Process rating: all ten parameters 58/100

Will not run. References files that are not bundled: ../shared/testmu-cloud-reference.md
  • 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 4504 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 892: 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.