Agent skill

iOS App Intents

by omarshahine in omarshahine/HomeClaw

Design and implement App Intents, app entities, and App Shortcuts for iOS apps so useful actions and content are available to Shortcuts, Siri, Spotlight, widgets, controls, and other intent-driven…

MITAuto-check passedMobile

Install iOS App Intents

skills CLI
$ npx skills add omarshahine/HomeClaw --skill ios-app-intents -a claude-code

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

GitHub CLI
$ gh skill install omarshahine/HomeClaw ios-app-intents --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/omarshahine/HomeClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ios-app-intents .claude/skills/ios-app-intents && 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
ios-app-intents
GitHub stars
176
Used in
1 other repo
Token cost
~1.2k tokens
SKILL.md length
613 words
Files
6 (incl. references)
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Design and implement App Intents, app entities, and App Shortcuts for iOS apps so useful actions and content are available to Shortcuts, Siri, Spotlight, widgets, controls, and other intent-driven…

  • Works in 5 steps: Start with actions, not screens → Define a small entity surface → Decide whether the action completes in… → …
  • Exposing app actions outside the UI
  • SKILL.md covers Overview, Core workflow, Strong defaults and Anti-patterns, plus 1 more section
  • Reaches developer.apple.com

What it does

iOS App Intents is an agent skill from omarshahine/HomeClaw. Design and implement App Intents, app entities, and App Shortcuts for iOS apps so useful actions and content are available to Shortcuts, Siri, Spotlight, widgets, controls, and other intent-driven system surfaces. Use when exposing app actions outside the UI, adding AppEntity and EntityQuery types, shaping shortcut phrases and display representations, or routing intent execution back into the main app.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `references/code-templates.md` and `references/example-patterns.md`).

It sits in Mobile, covering iOS development. It works with iOS. The repository describes itself as: HomeKit smart home control via MCP — lights, locks, thermostats, and scenes for Claude Desktop, Claude Code, and OpenClaw. The licence is MIT.

When your agent uses it

  • Exposing app actions outside the UI
  • Adding AppEntity and EntityQuery types
  • Shaping shortcut phrases and display representations
  • Routing intent execution back into the main app

Example prompts

  • “/ios-app-intents”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Start with actions, not screens
  2. Define a small entity surface
  3. Decide whether the action completes in place or opens the app
  4. Make the actions discoverable
  5. Validate the runtime handoff

What it can do on your machine

Read from SKILL.md and the folder at commit 69ff193. 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

    Hosts in commands or code, which the agent is likely to contact:

    • developer.apple.com

    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

iOS App Intents loads about 1.2k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 613 words of instructions outside code blocks.

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

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 omarshahine/HomeClaw at commit 69ff193, republished under its MIT licence (© omarshahine). 613 words, ~1,213 tokens.

Download SKILL.mdSave it as .claude/skills/ios-app-intents/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
ios-app-intents
description
Design and implement App Intents, app entities, and App Shortcuts for iOS apps so useful actions and content are available to Shortcuts, Siri, Spotlight, widgets, controls, and other intent-driven system surfaces. Use when exposing app actions outside the UI, adding `AppEntity` and `EntityQuery` types, shaping shortcut phrases and display representations, or routing intent execution back into the main app.

iOS App Intents

Overview

Expose the smallest useful action and entity surface to the system. Start with the verbs and objects people would actually want outside the app, then implement a narrow App Intents layer that can deep-link or hand off cleanly into the main app when needed.

Read these references as needed:

  • references/first-pass-checklist.md for choosing the first intent and entity surface
  • references/example-patterns.md for concrete example shapes to copy and adapt
  • references/code-templates.md for generalized App Intents code templates
  • references/system-surfaces.md for how to think about Shortcuts, Siri, Spotlight, widgets, and other system entry points

Core workflow

1) Start with actions, not screens
  • Identify the 1-3 highest-value actions that should work outside the app UI.
  • Prefer verbs like compose, open, find, filter, continue, inspect, or start.
  • Do not mirror the entire app navigation tree as intents.
2) Define a small entity surface
  • Add AppEntity types only for the objects the system needs to understand or route.
  • Keep the entity shape narrower than the app's persistence model.
  • Add EntityQuery or other query types only where disambiguation or suggestions are genuinely useful.
3) Decide whether the action completes in place or opens the app
  • Use non-opening intents for actions that can complete directly from the system surface.
  • Use openAppWhenRun or open-style intents when the user should land in a specific in-app workflow.
  • When the app must react inside the main scene, add one clear runtime handoff path instead of scattering ad hoc routing logic.
  • If the action can work in both modes, consider shipping both an inline version and an open-app version rather than forcing one compromise.
4) Make the actions discoverable
  • Add AppShortcutsProvider entries for the first set of high-value intents.
  • Choose titles, phrases, and symbols that make sense in Shortcuts, Siri, and Spotlight.
  • Keep shortcut phrases direct and task-oriented.
  • Reuse the same action model for widgets and controls when a widget configuration or intent-driven control already needs the same parameters.
5) Validate the runtime handoff
  • Build the app and confirm the intents target compiles cleanly.
  • Verify the app opens or routes to the expected place when an intent runs.
  • Summarize which actions are now exposed, which entities back them, and how the app handles invocation.
Show full SKILL.md (250 more words)Show less

Strong defaults

  • Prefer a dedicated intents target or module for the system-facing layer.
  • Keep intent types thin; business logic should stay in app services or domain models.
  • Keep app entities small and display-friendly.
  • Use AppEnum for fixed app choices such as tabs, modes, or visibility levels before reaching for a full entity type.
  • Prefer one predictable app-intent routing surface in the main app scene or root router.
  • Treat App Intents as system integration infrastructure, not only as a Shortcuts feature.

Anti-patterns

  • Exposing every screen or tab as its own intent without a real user value.
  • Mirroring the entire model graph as AppEntity types.
  • Hiding runtime handoff in global side effects with no clear app entry path.
  • Adding App Shortcuts with vague phrases or generic titles.
  • Treating the first App Intents pass as a broad taxonomy project instead of a small useful release.

Notes

  • Apple documentation to use as primary references:
    • https://developer.apple.com/documentation/appintents/making-actions-and-content-discoverable-and-widely-available
    • https://developer.apple.com/documentation/appintents/creating-your-first-app-intent
    • https://developer.apple.com/documentation/appintents/adopting-app-intents-to-support-system-experiences
  • In addition to the links above, use web search to consult current Apple Developer documentation when App Intents APIs or platform behavior may have changed.
  • A good first pass often includes one open-app intent, one action intent, one or two entity types, and a small AppShortcutsProvider.
  • Good example families to cover are:
    • open a destination or editor in the app
    • perform a lightweight action inline without opening the app
    • choose from a fixed enum such as a tab or mode
    • resolve one or more entities through EntityQuery
    • power widget configuration or controls from the same entity surface

© omarshahine, 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 5 other files (references) in .claude/skills/ios-app-intents of omarshahine/HomeClaw.

  • SKILL.md
  • agents/openai.yaml
  • references/code-templates.md
  • references/example-patterns.md
  • references/first-pass-checklist.md
  • references/system-surfaces.md

Open the folder on GitHubat commit 69ff193

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in omarshahine/HomeClaw, which our catalogue first saw on October 7, 2026.

Compare with similar skills

iOS App Intents 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.

iOS App Intents compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
iOS App Intents this skillomarshahine/HomeClaw1761 repos~1.2kAutomated safety check: PassMIT
Hig Project Contextraintree-technology/hig-doctor1445 repos~1.2kAutomated safety check: PassMIT
Hig Components Contentraintree-technology/hig-doctor1445 repos~1.3kAutomated safety check: PassMIT
iOS Simulator Skilln0an/VivaDicta1301 repos~2.5kAutomated safety check: PassMIT
Inspector Implementationipedro/Inspector170—~729Automated safety check: PassMIT
Device InteractionInfomaniak/desktop-kDrive1201 repos~1.9kAutomated safety check: PassGPL-3.0

Similar skills

  • Hig Project Context

    raintree-technology/hig-doctor

    Create or update a shared Apple design context document that other HIG skills use to tailor guidance.

    144 GitHub starsUsed in 5 repos~1.2k tokens
    MobileAuto-check passed
  • Hig Components Content

    raintree-technology/hig-doctor

    Apple Human Interface Guidelines for content display components.

    144 GitHub starsUsed in 5 repos~1.3k tokens
    MobileAuto-check passed
  • iOS Simulator Skill

    n0an/VivaDicta

    21 production-ready scripts for iOS app testing, building, and automation.

    130 GitHub starsUsed in 1 repo~2.5k tokens
    MobileAuto-check passed
  • Inspector Implementation

    ipedro/Inspector

    A skill your agent uses when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding.

    170 GitHub stars~729 tokensUpdated 5 mo ago
    MobileAuto-check passed
  • Device Interaction

    Infomaniak/desktop-kDrive

    Verify iOS app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions.

    120 GitHub starsUsed in 1 repo~1.9k tokens
    MobileAuto-check passed
  • Run iOS Simulator

    iPlug2/iPlug2OOS

    Build and run an iPlug2 iOS app in the iOS Simulator. An agent skill from iPlug2/iPlug2OOS.

    158 GitHub stars~711 tokensUpdated 26 days ago
    MobileAuto-check passed

More from omarshahine/HomeClaw

All 14 skills in this repo
  • Swiftui Expert Skill

    omarshahine/HomeClaw

    A skill your agent uses when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management, view composition, performance, Liquid Glass adoption, or Instruments .trace…

    176 GitHub starsUsed in 4 repos~2.8k tokens
    Auto-check passed
  • Spm Build Analysis

    omarshahine/HomeClaw

    Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds.

    176 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Xcode Build Benchmark

    omarshahine/HomeClaw

    Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped .build-benchmark/ artifacts.

    176 GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Xcode Build Fixer

    omarshahine/HomeClaw

    Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement.

    176 GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed
  • Xcode Build Orchestrator

    omarshahine/HomeClaw

    Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to…

    176 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed
  • Xcode Compilation Analyzer

    omarshahine/HomeClaw

    Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan.

    176 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

Works with

Categories

Questions about iOS App Intents

What does iOS App Intents do?

Design and implement App Intents, app entities, and App Shortcuts for iOS apps so useful actions and content are available to Shortcuts, Siri, Spotlight, widgets, controls, and other intent-driven…. iOS App Intents is an agent skill from omarshahine/HomeClaw. Design and implement App Intents, app entities, and App Shortcuts for iOS apps so useful actions and content are available to Shortcuts, Siri, Spotlight, widgets, controls, and other intent-driven system surfaces.

When should I use iOS App Intents?

iOS App Intents fits situations like: exposing app actions outside the UI; adding AppEntity and EntityQuery types; shaping shortcut phrases and display representations; routing intent execution back into the main app.

How do I install iOS App Intents in Claude Code?

Run `npx skills add omarshahine/HomeClaw --skill ios-app-intents -a claude-code`. Or copy the skill folder (.claude/skills/ios-app-intents in omarshahine/HomeClaw) into .claude/skills/ios-app-intents in your project. Claude Code loads it when a task matches its description.

How do I install iOS App Intents in Codex?

Run `npx skills add omarshahine/HomeClaw --skill ios-app-intents -a codex`. Or copy the skill folder (.claude/skills/ios-app-intents in omarshahine/HomeClaw) into .agents/skills/ios-app-intents in your project. Codex loads it when a task matches its description.

Can I use iOS App Intents 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 omarshahine/HomeClaw --skill ios-app-intents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ios-app-intents, .gemini/skills/ios-app-intents, .github/skills/ios-app-intents and .opencode/skills/ios-app-intents in your project.

What does iOS App Intents need to run?

SKILL.md names no scripts, command-line tools or credentials: iOS App Intents is instructions for the agent only.

Does iOS App Intents access the network?

SKILL.md names 1 domain. In commands or code: developer.apple.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is iOS App Intents 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 iOS App Intents use?

iOS App Intents 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 iOS App Intents use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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 3.4k tokens, read only when the agent opens those files.

What are the alternatives to iOS App Intents?

Skills that share tags, products or a category with iOS App Intents: Hig Project Context (raintree-technology/hig-doctor, 144 stars), Hig Components Content (raintree-technology/hig-doctor, 144 stars), iOS Simulator Skill (n0an/VivaDicta, 130 stars) and Inspector Implementation (ipedro/Inspector, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains iOS App Intents?

omarshahine (a GitHub user) maintains it in omarshahine/HomeClaw, which has 176 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 10, 2026.

Source: omarshahine/HomeClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.