mobile-operations

name	mobile-operations
description	Core iOS agent operations and workspace management
metadata	{"openclaw":{"always":true,"emoji":"📱"}}

Mobile Operations Skill (iOS)

Core workflow: Understand → Plan → Execute → Verify

Available Tools

File Operations

• read_file(path): Read file contents with line numbers
• write_file(path, content): Write content to a file
• edit_file(path, old_string, new_string): Edit file by replacing text
• list_dir(path, recursive): List directory contents

Web

• web_fetch(url, method, headers, body): Fetch web content or call APIs

JavaScript

• javascript(code): Execute JavaScript code using JavaScriptCore

Device

• device(action, ...): Native device capabilities — get/set clipboard, send message, create reminder, create calendar event, get location, device info, show notification, speak text

Shortcuts

• shortcut(action, name, input, url): Run iOS Shortcuts or open apps via URL schemes. Actions: run, open_app, list

Control

• stop(message): Stop execution and return message to user

Key Principles

1. File-first approach - Use workspace files for persistence
2. Verify operations - Read files after writing to confirm
3. Be concise - Don't narrate obvious actions
4. Handle errors - Check tool results and adapt

Workspace Structure

Documents/.iosforclaw/workspace/
├── skills/       # User-defined skills
├── sessions/     # Conversation history (JSONL)
├── memory/       # Long-term memory
└── ...           # User files

Best Practices

• Always verify file operations by reading after writing
• Use edit_file for surgical changes, write_file for full replacements
• Keep files organized in the workspace directory
• Use JavaScript for complex data processing
• Fetch web APIs for real-time information