agentleFS
rebornixrebornix/Agmente/.github/skills/run-agmente-e2e/SKILL.md

run-agmente-e2e

Skill545 starsChanged 9 months agoMITView on GitHub

Run Agmente iOS end-to-end tests against a local ACP agent (Gemini, Claude, Qwen, or Vibe), validate core RPC flow, and perform mandatory cleanup.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the user asks to run Agmente E2E or UI-level integration checks with a real ACP agent.

    line 8
  2. Distinctive:

    Start local ACP bridge in background:

    line 20
  3. Very specific:

    Use XcodeBuildMCP build_run_sim with Agmente defaults.

    line 23
  4. Very specific:

    Call describe_ui before each tap.

    line 26
  5. Very specific:

    Use tap by id or label where available.

    line 27
  6. Distinctive:

    Do not skip cleanup.

    line 36
  7. Very specific:

    Use a valid working directory on host machine (for Agmente server config).

    line 37
  8. Distinctive:

    Do not rely on guessed coordinates from screenshots.

    line 38
  9. Very specific:

    Prefer deterministic selectors and describe_ui.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Run Agmente E2E

Use this skill when the user asks to run Agmente E2E or UI-level integration checks with a real ACP agent.

Inputs

  • agent: gemini (default), claude, qwen, or vibe
  • scenario: sanity (default), add-server, prompt-send
  • port: default 9000
  • simulatorID: default BE205EA8-B26C-44C2-B52B-B49141678273
  • npxTag: package tag for npx-based agents (latest by default). Override via third arg to start_agent.sh or AGMENTE_E2E_NPX_TAG.

Workflow

  1. Start local ACP bridge in background:
    • ./.github/skills/run-agmente-e2e/scripts/start_agent.sh <agent> <port>
  2. Build and run in simulator:
    • Use XcodeBuildMCP build_run_sim with Agmente defaults.
  3. Execute UI steps:
    • Follow references/ui-checklist.md.
    • Call describe_ui before each tap.
    • Use tap by id or label where available.
  4. Validate protocol behavior:
    • Confirm sequence: initialize -> session/list -> session/new -> session/prompt.
    • Confirm capability badges and session list behavior.
  5. Cleanup always (success or failure):
    • ./.github/skills/run-agmente-e2e/scripts/cleanup.sh <simulatorID> <port>

Constraints

  • Do not skip cleanup.
  • Use a valid working directory on host machine (for Agmente server config).
  • Do not rely on guessed coordinates from screenshots.
  • Prefer deterministic selectors and describe_ui.

References

  • UI and validation checklist: references/ui-checklist.md

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.