iphoneclaw-action-scripts

Name: iphoneclaw-action-scripts
Availability: InStock
Author: NoEdgeAI

Execute iPhoneClaw action scripts via a local registry mapping short names.

64|5|Updated Feb 7, 2026

Search Tags:#automation #registry #recording #remote-control #iphone #action-scripts

Ready to run

npx skills add https://github.com/NoEdgeAI/iphoneclaw --skill iphoneclaw-action-scripts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: iphoneclaw-action-scripts
Source: https://github.com/NoEdgeAI/iphoneclaw/tree/main/skills/iphoneclaw-action-scripts
Command: npx skills add https://github.com/NoEdgeAI/iphoneclaw --skill iphoneclaw-action-scripts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the creation, organization, and execution of iPhoneClaw action scripts by leveraging a local registry to map short names to recorded actions, reducing token usage and enabling repeatable automations.

Core Features & Use Cases

Local script registry at action_scripts/registry.json that maps short names to pre-recorded action scripts.
Available scripts reside in action_scripts/common and action_scripts/recorded to enable deterministic execution and easy reuse.
Supports recording, exporting from runs, and remote triggering via supervisor APIs for governance and debugging.

Quick Start

Record or export a script, add it to the registry, and call it with run_script(name=...).

Frequently Asked Questions about iphoneclaw-action-scripts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate remote iPhone control flows using pre-recorded action scripts?▼

You can automate remote iPhone control by registering pre-recorded action scripts in a local JSON registry and triggering them remotely via supervisor APIs for governance and debugging. This maps short names to recorded flows for deterministic execution.

What is the best way to organize and reuse iPhone automation scripts?▼

The best way to organize iPhone automation scripts is using a local registry that maps short names to recorded actions. Store available scripts in dedicated common and recorded directories to enable deterministic execution and easy reuse.

Can I export automation scripts directly from previous iPhone recording runs?▼

Yes, you can export action scripts directly from previous recording runs. The system supports recording new flows and exporting scripts from runs, which you can then add to the registry for future automated execution.

Do I need a specific file structure to run iPhone action scripts?▼

Yes, you need a populated action_scripts/registry.json file to map short names to scripts. You also require access to action_scripts/common and action_scripts/recorded directories to resolve names and execute the scripts properly.

How does a local script registry reduce token usage for iPhone automations?▼

A local script registry reduces token usage by mapping short names to pre-recorded actions. Instead of passing full script logic, you call run_script(name=...), which resolves the short name locally and executes the recorded flow.

Why are my iPhone action scripts not resolving during execution?▼

Action scripts fail to resolve when the registry.json file is missing entries or the script files are absent from the action_scripts/common or action_scripts/recorded directories required for name resolution and execution.