Skip to content
TrustedSkillsbeta
Back to all skills

Mobile Testing

Checked
proffesor-for-testing·vlatest·testing·MIT

Helps with mobile development, testing as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add proffesor-for-testing/agentic-qe --skill mobile-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

proffesor-for-testing

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned proffesor-for-testing/agentic-qe at 124d8c735e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
124d8c735e
Manifest
assets/skills/mobile-testing/SKILL.md
Scanned
8 files, 2,142 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The mobile-testing skill enables AI agents to execute automated functional and regression tests on iOS and Android applications. It supports running test suites across various device configurations to ensure app stability and feature correctness.

When to use it

  • Validating new features before releasing updates to production environments.
  • Performing regression testing after code changes to prevent breaking existing functionality.
  • Checking UI responsiveness and layout integrity on different screen sizes and orientations.
  • Automating repetitive manual test cases to accelerate the software delivery pipeline.

Key capabilities

  • Automated execution of test suites on real or emulated mobile devices.
  • Support for both iOS and Android operating systems.
  • Functional and regression testing workflows.
  • Integration with continuous integration pipelines for agile development cycles.

Example prompts

  • "Run the full regression suite on our latest Android build targeting API level 34."
  • "Execute functional tests for the new checkout flow on iOS devices with varying screen sizes."
  • "Automate a smoke test to verify login functionality across multiple device configurations before deployment."

Tips & gotchas

Ensure you have access to the necessary mobile device farms or emulators configured in your CI/CD environment. Limit test execution scope during initial development phases to reduce runtime costs and speed up feedback loops.