argent-ios-simulator-setup — Claude Code skill: boot and connect iOS
A skill for connecting to an iOS simulator via argent MCP tools. Use it to find a booted simulator, get its UDID, and prepare for any interaction task.
npx skills add software-mansion/argent --skill argent-ios-simulator-setup -a claude-codeWhat argent-ios-simulator-setup does
The skill handles two core operations: finding an already-booted simulator using list-devices (filters out physical devices and picks the first available iOS simulator) and booting a specific device with boot-device if none are running.
All interaction tools (gesture-tap, gesture-swipe, gesture-custom) automatically start the MCP server if it isn't running yet. The simulator UDID has the format A1B2C3D4-E5F6-7890-ABCD-EF1234567890 — pass it to any command that needs it.
If you delegate simulator tasks to sub-agents, verify they have MCP-permissions access.
What it helps with
- find a booted iOS simulator
- boot and connect to a new simulator
- retrieve a simulator UDID for interactions
- start the MCP server before automation
- distinguish a simulator from a physical device
Example prompts for the agent
- Connect to an iOS simulator and find the first available one
- Boot the simulator with UDID A1B2C3D4-E5F6-7890-ABCD-EF1234567890
- Set up a simulator for argent before running UI tests
How to install argent-ios-simulator-setup
1Skills CLI (Vercel)
npx skills add software-mansion/argent --skill argent-ios-simulator-setup -a claude-code2Manually: put the files in place
~/.claude/skills/argent-ios-simulator-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/argent-ios-simulator-setup/
1Skills CLI (Vercel)
npx skills add software-mansion/argent --skill argent-ios-simulator-setup -a codex2Manually: put the files in place
.agents/skills/argent-ios-simulator-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add software-mansion/argent --skill argent-ios-simulator-setup -a cursor2Manually: put the files in place
.cursor/skills/argent-ios-simulator-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install software-mansion/argent argent-ios-simulator-setup2Manually: put the files in place
.github/skills/argent-ios-simulator-setup/SKILL.md1Skills CLI (Vercel)
npx skills add software-mansion/argent --skill argent-ios-simulator-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/software-mansion/argent --path packages/skills/skills/argent-ios-simulator-setupManually: put the files in place
.devin/skills/argent-ios-simulator-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add software-mansion/argent --skill argent-ios-simulator-setup -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set15
The whole set →Similar
Questions about argent-ios-simulator-setup
How do I install argent-ios-simulator-setup in Claude Code?
Run npx skills add software-mansion/argent --skill argent-ios-simulator-setup -a claude-code twice, then open ~/.claude/skills/argent-ios-simulator-setup/SKILL.md.
What does this skill do?
It finds a booted iOS simulator via list-devices, boots a specific device with boot-device, and prepares it for interaction using argent MCP tools.
Do sub-agents need special permissions?
Yes. If you assign simulator tasks to sub-agents, make sure they have access to MCP-permissions to use argent tools.
Source text
SKILL.md · Apache-2.0
--- name: argent-ios-simulator-setup description: Set up and connect to an iOS simulator using argent MCP tools. Use when starting a new session, booting an iOS simulator, getting an iOS UDID, or before any iOS simulator interaction task. --- ## 1. Setup Steps If you delegate simulator tasks to sub-agents, make sure they have MCP permissions. 1. **Find a booted simulator** Use `list-devices`. Filter for entries with `platform: "ios"` and skip any with `kind: "device"` (a physical iPhone, never a simulator target): booted simulators are listed first. If none are booted, call `boot-device` with `udid: <chosen UDID>`. 2. **Verify connection** All interaction tools (`gesture-tap`, `gesture-swipe`, `gesture-custom`, etc.) auto-start the server if not already running. ## 2. Notes - UDIDs look like: `A1B2C3D4-E5F6-7890-ABCD-EF1234567890`
© software-mansion · Apache-2.0 · software-mansion/argent