SKILLEMALL.ai
GitHub ↗ RU Sign in

BC kobiton-migration-skill

Migrate test automation from Kobiton to TestMu AI (formerly LambdaTest) in any language or framework. Covers Kobiton real-device Appium cloud (api.kobiton.com/wd/hub), kobiton: capabilities, Kobiton App Repository (kobiton-store:), NOVA Scriptless exports. Use this whenever someone wants to move, switch, port, migrate or point tests from Kobiton to TestMu AI or LambdaTest, asks what the TestMu or LT:Options equivalent is for a capability, config, CLI flag or API from Kobiton, mentions api.kobiton.com, kobiton:, kobiton-store:, deviceGroup, sessionName, captureScreenshots, KOBITON_USERNAME, KOBITON_API_KEY, or wants a migration plan, estimate, PR or checklist for a repo currently on Kobiton, even without the word migrate.

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

Migrate test automation from Kobiton 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

ProcedurePlaywrightSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
98
Quality 40%
83
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/kobiton.md:74
    Credential used in a network call (verify the destination is the intended service) (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=app"
    vendor-host
  • 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 4450 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)
  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +3Description length 730: enough signal without eating the budget
  • +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: 83.