agentleFS
Sign inStart free
ruizricaruizrica/agent-pi/skills/qa-automation/qa-setup/SKILL.md

qa-setup

Skill274 starsChanged 8 months agoMITView on GitHub

Verify and install all dependencies for the QA Automation skill package. Checks for agent-device, agent-browser, Node.js, iOS/Android tools, and the 'ws' WebSocket library. Installs missing tools automatically. Invoke when user says "check qa setup", "install qa tools", "verify qa dependencies", "set up qa automation", "prepare for testing", or any task requiring QA tool verification.

  • Installs packages

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify: Run the setup guard to check everything works:

    line 72
  2. Distinctive:

    Test: Run an example test flow:

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

qa-setup

Dependency verification and installation for the QA Automation skill package. Ensures both agent-device (native app testing) and agent-browser (web app testing) are installed and functional, along with all supporting tools.

What Gets Checked

DependencyPurposeAuto-Install?
agent-deviceNative iOS/Android simulator control, screenshots, gestures✅ npm install -g agent-device
agent-browserWeb browser automation, form filling, screenshots✅ npm install -g agent-browser
Node.jsRuntime for CDP WebSocket and JSON processing❌ Manual install required
npm / npxPackage management❌ Comes with Node.js
wsWebSocket library for CDP connections✅ npm install ws
Xcode / xcruniOS Simulator management❌ Manual install (Mac App Store)
adbAndroid emulator management❌ Manual install (Android Studio)
Bash 4.0+Required for array support in test scripts❌ brew install bash
curlHTTP requests for health checks❌ Usually pre-installed
jqJSON processing (optional)❌ brew install jq

Usage

Full check + auto-install

bash .pi/skills/qa-automation/install.sh

Check only (don't install anything)

bash .pi/skills/qa-automation/install.sh --check

Manual install commands

# Core tools
npm install -g agent-device
npm install -g agent-browser

# CDP dependency (in your project)
cd /path/to/your/project
npm install ws

# iOS tools
xcode-select --install

# Android tools
brew install android-platform-tools

# Optional
brew install jq
brew install bash  # If Bash < 4.0

After Setup

  1. Configure: Copy qa.config.sh and set your app-specific values:
    export APP_BUNDLE_ID="com.yourapp.dev"
export PROJECT_DIR="/path/to/your/project"
  2. Verify: Run the setup guard to check everything works:
    source .pi/skills/qa-automation/qa-scroll/lib/setup-guard.sh
run_setup_guard
  3. Test: Run an example test flow:
    bash .pi/skills/qa-automation/qa-scroll/run.sh

Architecture

The QA Automation package uses a dual-driver architecture:

┌─────────────────────────────────────────────────────────────┐
│                    QA Automation Skills                       │
├──────────────────────┬──────────────────────────────────────┤
│  Native App Testing  │       Web App Testing                │
│                      │                                       │
│  ┌──────────────┐    │    ┌──────────────┐                  │
│  │ agent-device  │    │    │ agent-browser │                  │
│  │              │    │    │               │                  │
│  │ • Screenshots │    │    │ • Screenshots │                  │
│  │ • Gestures    │    │    │ • Click/Fill  │                  │
│  │ • A11y tree   │    │    │ • A11y tree   │                  │
│  │ • App launch  │    │    │ • Navigation  │                  │
│  └──────┬───────┘    │    └──────┬────────┘                  │
│         │            │           │                            │
│  ┌──────▼───────┐    │    ┌──────▼────────┐                  │
│  │ CDP (Hermes)  │    │    │ Browser DOM    │                  │
│  │              │    │    │               │                  │
│  │ • JS eval     │    │    │ • JS eval     │                  │
│  │ • Navigation  │    │    │ • State check │                  │
│  │ • State query │    │    │ • Network     │                  │
│  │ • Debug hooks │    │    │ • Cookies     │                  │
│  └──────────────┘    │    └───────────────┘                  │
└──────────────────────┴──────────────────────────────────────┘

Both drivers are required for full functionality. agent-device handles the physical device/simulator layer, while CDP (or agent-browser for web) handles the application runtime layer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free