Agent skill

Xcode Simulator Test

by EveryInc in EveryInc/compound-engineering-plugin

Builds an iOS app, exercises it on a simulator with XcodeBuildMCP and reports PASS, FAIL or PARTIAL with screenshots, logs and per-screen evidence.

MITAuto-check passedMobile

Install Xcode Simulator Test

skills CLI
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-test-xcode -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install EveryInc/compound-engineering-plugin ce-test-xcode --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ce-test-xcode .claude/skills/ce-test-xcode && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ce-test-xcode
GitHub stars
25k
Token cost
~519 tokens
SKILL.md length
255 words
Files
4 (incl. references)
Skills in repo
37
Repo updated
First seen
Licence
MIT

At a glance

Builds an iOS app, exercises it on a simulator with XcodeBuildMCP and reports PASS, FAIL or PARTIAL with screenshots, logs and per-screen evidence.

  • Works in 2 steps: Prepare and launch. Read… → Exercise and report. After launch, read…
  • iOS changes need simulator evidence before handoff
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Producing a PASS or FAIL report with screenshots and console logs for an app build

What it does

The skill preserves screenshots, logs, human-verification results and failures as evidence. A finished run reports an overall `PASS`, `FAIL` or `PARTIAL` together with the project, scheme, simulator, build result, per-surface `PASS`, `FAIL` or `SKIP`, console errors, human checks and leftover failures. Status per surface comes from evidence rather than from your routing choice, and the overall result is FAIL while any failure remains, PARTIAL when only skips remain, and otherwise PASS.

Work follows two reference files. The first covers checking that XcodeBuildMCP is available, discovering the project and scheme, choosing a simulator, build, install, launch and starting log capture; a failure before launch stops later stages and reports a setup blocker. The second covers per-screen evidence, flows only a human can do, a limitation with SwiftUI inline links, what to do when a check fails, cleanup and the summary fields. The skill only tests and reports, with diagnosis and fixes going to `ce-debug`.

When your agent uses it

  • iOS changes need simulator evidence before handoff
  • Producing a PASS or FAIL report with screenshots and console logs for an app build
  • Separating simulator checks the agent can automate from ones a human must confirm

Example prompts

  • “Run the Xcode simulator test on the onboarding flow and report what passed.”
  • “Build the app on a simulator and give me screenshots plus console errors for the settings screen.”
  • “Retest the login fix on the simulator and update the overall result.”

Requirements

  • Xcode with an iOS simulator
  • XcodeBuildMCP available to the agent

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Prepare and launch. Read references/setup-and-build.md. It defines the XcodeBuildMCP availability check, project and scheme discovery…
  2. Exercise and report. After launch, read references/test-and-report.md. It defines per-screen evidence, human-only flows, the SwiftUI…

What it can do on your machine

Read from SKILL.md and the folder at commit cef001f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Xcode Simulator Test loads about 519 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 31 tokens; SKILL.md has 255 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~519
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from EveryInc/compound-engineering-plugin at commit cef001f, republished under its MIT licence (© EveryInc). 255 words, ~519 tokens.

Download SKILL.mdSave it as .claude/skills/ce-test-xcode/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
ce-test-xcode
description
Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.
argument-hint
[scheme name or 'current' to use default]
disable-model-invocation
true

Xcode Simulator Test

Build and exercise an iOS app on a simulator, preserving screenshots, logs, human-verification results, and failures as evidence for the user.

Done:

  • A completed run reports overall PASS, FAIL, or PARTIAL plus project, scheme, simulator, build result, per-surface PASS / FAIL / SKIP, console errors, human checks, and residual failures.
  • Per-surface status is derived from evidence, not the user's routing choice. PASS requires completed passing evidence. FAIL records observed failing evidence until a completed retest replaces it. SKIP means the check has no completed outcome.
  • The overall result is FAIL while any failure remains, PARTIAL when no failure remains but a scoped check is skipped, and otherwise PASS.
  • Any failure before the app is launched with log capture running stops later stages and reports an actionable setup blocker with its evidence.

Boundaries: this skill tests and reports. Diagnosis and any user-approved product fix belong to ce-debug, invoked with its authority narrowed so it returns here without committing, pushing, or opening a PR. Keep simulator interaction within the app and flows the user placed in scope.

Run

  1. Prepare and launch. Read references/setup-and-build.md. It defines the XcodeBuildMCP availability check, project and scheme discovery, simulator choice, build, install, launch, and log-capture start.
  2. Exercise and report. After launch, read references/test-and-report.md. It defines per-screen evidence, human-only flows, the SwiftUI inline-link automation limitation, what to do when a check fails, cleanup, and the fixed summary fields.

Do not replace either required read with remembered tool names. XcodeBuildMCP adapters differ by host, while their observable success conditions do not.

© EveryInc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/ce-test-xcode of EveryInc/compound-engineering-plugin.

  • SKILL.md
  • agents/openai.yaml
  • references/setup-and-build.md
  • references/test-and-report.md

Open the folder on GitHubat commit cef001f

Compare with similar skills

Xcode Simulator Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Xcode Simulator Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Xcode Simulator Test this skillEveryInc/compound-engineering-plugin25k—~519Automated safety check: PassMIT
Live-Device iOS QAgarrytan/gstack136k—~10kAutomated safety check: NotesMIT
FlowdeckSwiftedMind/Tessera116—~11kAutomated safety check: PassMIT
Orca iOS Simulator Controlstablyai/orca87k1 repos~584Automated safety check: PassApache-2.0
Limrun iOS Simulatorsuperset-sh/superset15k—~5.2kAutomated safety check: NotesCustom licence
Apple Crash Log .NET Symbolicationdotnet/skills5.6k1 repos~2.4kAutomated safety check: PassMIT

Similar skills

  • Live-Device iOS QA

    garrytan/gstack

    Tests a SwiftUI app on a real iPhone connected by USB, reading the Swift source and then looping through screenshot, analysis and action to find bugs.

    136k GitHub stars~10k tokensUpdated today
    MobileAuto-check: notes
  • Flowdeck

    SwiftedMind/Tessera

    FlowDeck is REQUIRED for all Apple platform build/run/test/launch/debug/simulator/device/log/automation tasks.

    116 GitHub stars~11k tokensUpdated 5 mo ago
    MobileAuto-check passed
  • iOS Simulator control from inside Orca, with the live device view in Orca's emulator pane. Use when driving a booted Apple Simulator on macOS: taps, gestures…

    87k GitHub starsUsed in 1 repo~584 tokens
    MobileAuto-check passed
  • Limrun iOS Simulator

    superset-sh/superset

    Drives an app on a Limrun cloud iOS simulator from any OS: launch, tap, type, read the accessibility tree and logs, take screenshots, record video and reach local services.

    15k GitHub stars~5.2k tokensUpdated today
    MobileAuto-check: notes
  • Official

    Resolves .NET runtime frames in Apple .ips crash logs to function names, source files and line numbers using dSYM symbols, atos and the Microsoft symbol server.

    5.6k GitHub starsUsed in 1 repo~2.4k tokens
    MobileAuto-check passed
  • Update Swiftui APIs

    AvdLee/SwiftUI-Agent-Skill

    Scan Apple's SwiftUI documentation for deprecated APIs and update the SwiftUI Expert Skill with modern replacements.

    3.7k GitHub stars~1.2k tokensUpdated yesterday
    MobileAuto-check passed

More from EveryInc/compound-engineering-plugin

All 37 skills in this repo
  • Compound Learning Writer

    EveryInc/compound-engineering-plugin

    Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.

    25k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Compound Learnings Refresh

    EveryInc/compound-engineering-plugin

    Audits a repo's stored learnings against the current codebase, fixes stale, overlapping or superseded docs and reports on every document.

    25k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Compound Engineering Prototype

    EveryInc/compound-engineering-plugin

    Builds a throwaway prototype at just the fidelity needed to settle a specific how-it-should-work-or-feel question, before committing to an approach other work will treat as fixed.

    25k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Compound Engineering Setup

    EveryInc/compound-engineering-plugin

    Checks Compound Engineering plugin health and repo-local config, or scaffolds a Compound Pack when you ask for one by id.

    25k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • PR Babysitter

    EveryInc/compound-engineering-plugin

    Watches an open GitHub pull request over time, routing review comments and CI failures to other skills until the PR is ready to merge.

    25k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • CE Brainstorm

    EveryInc/compound-engineering-plugin

    Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.

    25k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Questions about Xcode Simulator Test

What does Xcode Simulator Test do?

Builds an iOS app, exercises it on a simulator with XcodeBuildMCP and reports PASS, FAIL or PARTIAL with screenshots, logs and per-screen evidence. The skill preserves screenshots, logs, human-verification results and failures as evidence. A finished run reports an overall `PASS`, `FAIL` or `PARTIAL` together with the project, scheme, simulator, build result, per-surface `PASS`, `FAIL` or `SKIP`, console errors, human checks and leftover failures.

When should I use Xcode Simulator Test?

Xcode Simulator Test fits situations like: iOS changes need simulator evidence before handoff; producing a PASS or FAIL report with screenshots and console logs for an app build; separating simulator checks the agent can automate from ones a human must confirm.

How do I install Xcode Simulator Test in Claude Code?

Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-test-xcode -a claude-code`. Or copy the skill folder (skills/ce-test-xcode in EveryInc/compound-engineering-plugin) into .claude/skills/ce-test-xcode in your project. Claude Code loads it when a task matches its description.

How do I install Xcode Simulator Test in Codex?

Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-test-xcode -a codex`. Or copy the skill folder (skills/ce-test-xcode in EveryInc/compound-engineering-plugin) into .agents/skills/ce-test-xcode in your project. Codex loads it when a task matches its description.

Can I use Xcode Simulator Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EveryInc/compound-engineering-plugin --skill ce-test-xcode -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ce-test-xcode, .gemini/skills/ce-test-xcode, .github/skills/ce-test-xcode and .opencode/skills/ce-test-xcode in your project.

What does Xcode Simulator Test need to run?

SKILL.md names no scripts, command-line tools or credentials: Xcode Simulator Test is instructions for the agent only. Our summary lists: Xcode with an iOS simulator; XcodeBuildMCP available to the agent.

Does Xcode Simulator Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Xcode Simulator Test safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Xcode Simulator Test use?

Xcode Simulator Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Xcode Simulator Test use?

About 519 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Xcode Simulator Test?

Skills that share tags, products or a category with Xcode Simulator Test: Live-Device iOS QA (garrytan/gstack, 136k stars), Flowdeck (SwiftedMind/Tessera, 116 stars), Orca iOS Simulator Control (stablyai/orca, 87k stars) and Limrun iOS Simulator (superset-sh/superset, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Xcode Simulator Test?

EveryInc (a GitHub organization) maintains it in EveryInc/compound-engineering-plugin, which has 25,412 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 7, 2026.

Source: EveryInc/compound-engineering-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.