More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Expo App Clip: Lightweight iOS Clips

    1

    Add an iOS App Clip to an Expo app: score the idea first, then wire identity, domain association, the AASA file, and banner, and ship both targets to TestFlight.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Expo App Clip: Lightweight iOS Clips

    Expo App Clip: Lightweight iOS Clips

    Example session with this skill installed

    We run a food truck with an Expo app for our restaurant. People queue at the truck and we want the QR code on the side to open a tiny order-ahead flow — pick items, pay, get a pickup number — without installing the app. Is that an App Clip, and what do we have to set up?

    • Read your context and instructions
    • Compiled the expo app clip

    APP CLIP ASSESSMENT AND SETUP — food-truck order-ahead.

    WORTH IT? Score the candidate: single action 2 (order, pay, done — no account), context 2 (the QR encodes the truck's location ID as a URL parameter), moment 2 (the customer is physically at the truck, queueing), size 1 (menu is data-light; photos need trimming to stay lean). Total 7 of 8, no zero on single action — build it.

    FOUR CONTRACTS, IN ORDER: 1) Identity — parent com.truck.kitchenapp, Clip derived as com.truck.kitchenapp.clip, team ID in the app config. 2) Entitlements — applinks: on the parent, appclips: on the Clip, both naming the ordering domain. 3) Association file — served from the domain's .well-known path, no extension, appclips block naming the full Clip ID (team ID + Clip bundle ID, not the parent's); verified with curl against the production deploy before any device test, because iOS caches this file and a stale copy mimics a code bug. 4) Banner — Smart App Banner with the parent's app-id and app-clip-display=card on the ordering page the QR resolves to.

    PERMISSIONS: the Clip needs no location permission at all — the truck is identified by the QR parameter, not GPS — so the Clip's Info.plist stays minimal, which also keeps review simple.

    TEST PATH: joint build to TestFlight, then on a real device scan the printed QR: card appears, Clip launches to that truck's menu, test order completes with a pickup number. Loyalty, order history, and settings stay in the full app, where they belong.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A customer is standing at your counter, your truck, your venue. They will not install a full app to pay, order, or check in — but iOS will launch a tiny App Clip from a link, a QR code, or a banner, no install required. Adding one to an Expo project means making four contracts agree: the Clip's identity, the domain entitlements on both targets, the association file your website serves, and the build plus store record. When any one disagrees, the Clip simply never appears, and the failure is silent. This skill works the whole path in order. First, a scoring rubric decides whether your candidate action is worth a Clip at all — single action, self-contained, valuable at the physical moment — because a Clip that needs an account or three screens of context fights both users and App Store review. Then the wiring: bundle ID and team ID in the app config, scaffolding the Clip target, the applinks and appclips entitlements, the apple-app-site-association file with the Clip's full app ID (and the two gotchas — no file extension, and the appclips block names the Clip, not the parent), the Smart App Banner with card display, and permission mirroring that gives the Clip only what it uses, with ephemeral location instead of background access. A readiness checklist gates the build, both targets ship together to TestFlight, store metadata describes the launch experience, and the worked example follows a coffee chain's pickup-order Clip from scoring (7 of 8, build it) through curl-verified association to a real-device order. A triage table maps each symptom — card never appears, Clip won't install, permissions fail — to its likely cause and first check.

    • iOS only: there is no Android equivalent in this skill, and Clip behavior (invocation, association caching, the card UI) can only be verified on a real device, not a simulator.
    • Clips live under a size ceiling and a one-action discipline; experiences needing accounts, history, or multi-screen context are out of scope by design.
    • Tooling shown is the current community target scaffolding for Expo; exact commands evolve, so the skill's verification steps (curl the association file, real-device test) matter more than any single command spelling.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Requires

    expo
    Node.js

    Permissions

    Terminal / Shell
    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    At the association file, with curl — not in your native code. Almost every silent failure is the file missing from the .well-known path, served on the wrong domain, or its appclips block naming the parent's ID instead of the Clip's. The skill's triage table works the symptoms in order.

    Small isn't the constraint — shape is. A Clip that needs sign-in or history stops being the one-action moment tool it's meant to be, and review will push on it. Keep the Clip to order-and-pay; the full app prompt after success is where accounts and history live.

    No. The QR and link reach both: devices with the Clip available get the card, everyone else gets the web page. The association file and banner route between them, which is why the web deploy and the Clip build have to be verified together.

    New in Mobile Development