Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Install and vet framework-vendor skills: Expo and Xcode

Written November 1, 2026

A developer installs skills written by the framework vendor, expecting the vendor's own guidance — and gets snapshots that go stale, paid-service triggers, and skills that only make sense inside the vendor's own tools.

Before you start

A vendor skill is a folder of instructions written by the people who ship the framework: a SKILL.md file that tells an agent how to build, deploy, or debug with that framework, plus any reference files it ships with. The vendor's name on the skill says who wrote the guidance. It does not say the guidance is current, free to follow, or usable by every agent. Expo's own repository states the position plainly: Expo documentation, Expo CLI, and EAS CLI remain the source of truth, and the skills teach an agent how to apply that guidance. This page covers two vendor collections that install differently and go stale differently: Expo's plugin and skills-CLI install, and Xcode's export from inside the toolchain. Vet each skill on its own triggers, costs, and tool needs — the vendor label covers none of those.

Expo: install the plugin or the skills CLI

Expo's skills page lists one install route per agent family. For Claude Code, install the official Expo plugin from the claude-plugins-official marketplace:

claude plugin install expo@claude-plugins-official

Inside a Claude Code session, the same install is /plugin install expo@claude-plugins-official. For Codex, the repository gives the OpenAI-curated marketplace install:

codex plugin add expo@openai-curated

For Cursor, OpenCode, GitHub Copilot, and other agents, Expo's repository gives the skills CLI route:

npx skills@latest add expo/skills --skill '*'

The CLI still asks where to install the skills; add --agent <agent> to target one agent directly. Run it from the project root, then restart or refresh the agent session so it can discover the installed SKILL.md files. Plugin installs stay updated through their official marketplaces. Skills-CLI installs update with npx skills@latest update, or one skill at a time with npx skills@latest update expo-router.

The two routes do not wire up the same extras. For Claude Code and Codex, the plugin also registers the Expo MCP Server, so it is not added separately. The skills CLI installs skills only. A skills-CLI install therefore gives the agent the written guidance without the live Expo and EAS access the MCP server provides, and a skill that assumes that access will not behave the same way on the CLI route.

Expo: read the free and paid groups before using a skill

Expo's repository groups the skills so the free and paid boundary is clear, and each skill's description carries the same label. The framework group covers the open-source Expo SDK and React Native: expo-overview as the entry point that routes to the right skill, plus expo-router, expo-animation, expo-native-ui, expo-data-fetching, expo-upgrade, and the rest of the framework list. The services group covers paid Expo Application Services (EAS): eas-app-stores for store submission, eas-hosting, eas-workflows, eas-observe, eas-update, eas-update-insights, and eas-simulator. Every services skill opens with a costs and plan-limits note. Read that note before asking the agent to follow the skill: an eas-* skill whose core purpose uses a paid service will spend against an EAS plan, and the note at the top of the skill is where the repository puts that fact.

Two skills deserve a first read because of what they trigger. expo-upgrade covers SDK upgrades, dependency conflicts, and deprecated packages — run it, or read it, when the SDK version in the project changes, because guidance written for one SDK version does not carry to the next. eas-simulator runs and controls an app on a remote simulator hosted on EAS cloud, and its description says to read it before running any eas simulator:* command, since it carries the current syntax for an experimental API. On macOS, its description says not to trigger it for a plain request to run on the local simulator. A third group, the experimental skills, ships in a separate expo-experiments plugin: content for APIs that are not final, which may change or be retired. Treat an experimental skill as a draft, not as settled guidance.

Xcode: export the skills, then read what your own Xcode printed

Xcode 27 ships with Apple-written agent skills in the Agent Skills format: folders holding a SKILL.md file and supporting files, the same format a plugin can carry. Apple's WWDC presentation describes a plugin as containing skills that are simple Markdown files capturing how to do a particular task. The skills live inside the toolchain, and one command pulls them out into a folder an outside agent can read:

xcrun agent skills export --output-dir ~/Downloads/xcode-skills

The export needs Xcode 27 installed and selected as the command-line tools. If xcrun cannot find the agent utility, the command-line tools still point at an older Xcode: set them to Xcode 27 in Xcode Settings, under Locations, and run the export again.

Do not trust any count of the skills from memory or from an article. Reports disagree: early write-ups list seven skills, later exports list ten, and a check of the Codex plugin inside Xcode counted fifteen. The names differ between those lists too — adopt-c-bounds-safety and app-intents-specialist appear in the ten-skill export and not in the seven-skill list. The collection changes between Xcode releases. Your own export is the list that counts for your Xcode build: run it, read the names it prints, and read each exported SKILL.md before handing it to an agent. Re-export after an Xcode upgrade. The exported copies are files on disk; they do not update themselves when Xcode does, and a skill tied to one release, such as swiftui-whats-new-27, describes that release's APIs.

Some exported skills assume Xcode's own tooling. device-interaction covers simulator screenshots, view-hierarchy inspection, and simulated touch. The exported folder holds instructions; the simulator and the tools that carry those instructions out live in Xcode. An outside agent given only the exported text cannot run a simulator check. Read each skill for the tools its steps name, and set aside the ones whose steps need Xcode tools the receiving agent cannot reach. That distinction — instructions in the skill, executable tools elsewhere — is the vetting step for this collection.

Steps

  1. Install by the framework's own route. Expo: the plugin for Claude Code or Codex, the skills CLI for other agents. Xcode: the xcrun agent skills export command with Xcode 27 selected. Use no other install path for a vendor skill.
  2. List what landed. For Expo, list the installed skills and note which group each one sits in: framework, services, or experimental. For Xcode, read the names the export printed. A skill that is not in the list was not installed, whatever an article said the collection holds.
  3. Read each skill's description and opening lines. For Expo, the description label says free or paid, and every services skill opens with a costs and plan-limits note — read the note, not just the label. For Xcode, read the SKILL.md itself: the description says when the agent should load it, and the body says which tools its steps need.
  4. Note the triggers, costs, and tool needs in one line each. A trigger is the request or project signal that loads the skill, such as an expo dependency in package.json for expo-overview. A cost is a paid service, a cloud simulator, or a store submission. A tool need is the MCP server, the simulator, or a CLI the skill assumes. A skill with a cost or a tool need the project does not have is not ready to use.
  5. Re-check on every SDK or Xcode update. Update the Expo install, then read expo-upgrade before trusting older Expo guidance against a new SDK. Re-export the Xcode skills after an Xcode upgrade, and read the diff: a renamed skill, a new skill, or a dropped one changes what the agent will load.

Check the agent's work

What can go wrong

Limits

Related playbooks

Sources

Sources: Expo Skills for AI agents, expo/skills repository, Inside Apple Intelligence and Xcode (WWDC26), Xcode 27 export skills guide.

Back to: Coding playbooks hub · Also: Vet a skill before you install it · Make sure your Claude Code skill actually loads when it should: test it in each agent before you rely on it · Vet an Antigravity plugin before the one-click install (a different vendor bundle: one plugin file carrying skills, MCP servers, rules, hooks, and custom agents, rather than one framework's skills)