agentleFS
Sign inStart free
KadirHarmancKadirHarmanc/nazar-skill/skills/live-test/SKILL.md

live-test

Skill0 starsChanged 8 months agoMITView on GitHub

Run YAML test files on iOS simulator or Android emulator. Prerequisite: /nazar:health. Use when user says 'live test', 'canli test', 'simulator test', 'run test on device', 'emulator test', 'UI test'.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. mindroom-ai/mindroom★ 361same name
    2. leadgenjay/claude-skills★ 22same name
    3. Mistakey/simulink-automation-suite★ 9same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run YAML-defined UI tests on simulator/emulator.

    line 7
  2. Very specific:

    Run /nazar:health first to verify simulator/emulator is available.

    line 10

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Nazar Live Test

Run YAML-defined UI tests on simulator/emulator.

Prerequisites

Run /nazar:health first to verify simulator/emulator is available.

How to run

  1. Find or accept YAML test file path (look in .nazar/tests/ or user-specified)
  2. Validate YAML syntax - must have: apiVersion, name, platform, steps
  3. Detect platform:
    • iOS: check xcrun simctl list devices booted via Bash
    • Android: check adb devices via Bash
  4. For each step, execute via Bash:
    • launchApp: iOS xcrun simctl launch booted <bundle_id>, Android adb shell am start -n <package>/<activity>
    • tapOn: iOS xcrun simctl io booted tap <x> <y>, Android adb shell input tap <x> <y>
    • inputText: iOS xcrun simctl io booted input text "<value>", Android adb shell input text "<value>"
    • assertVisible: take screenshot and analyze for expected element (use Read on screenshot)
    • screenshot: iOS xcrun simctl io booted screenshot <path>, Android adb shell screencap -p > <path>
    • scrollDown: iOS simctl, Android adb shell input swipe 500 1500 500 500
    • goBack: Android adb shell input keyevent KEYCODE_BACK
    • wait: sleep for specified duration
  5. Report: pass/fail per step, total pass rate, screenshots captured

YAML Format

apiVersion: nazar/v1
name: Test Name
platform: ios | android | all
priority: high | medium | low
steps:
  - action: launchApp
    target: "com.example.app"
  - action: tapOn
    target: "Login Button"
  - action: inputText
    target: "email_input"
    value: "test@example.com"
  - action: assertVisible
    target: "Welcome"
  - action: screenshot
    target: "login-success"
  - action: wait
    duration: 2

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