Appllama App Design Skill
Appllama/appllama-skills
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native).
Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in).
Install Expo Skill Feedback
$ npx skills add expo/skills --skill expo-skill-feedback -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install expo/skills expo-skill-feedback --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/expo/skills/expo-skill-feedback .claude/skills/expo-skill-feedback && rm -rf skills-srcUse ~/.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/
Install the "expo-skill-feedback" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-skill-feedback into .claude/skills/expo-skill-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-skill-feedback", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-skill-feedbackType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add expo/skills --skill expo-skill-feedback -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install expo/skills expo-skill-feedback --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/expo/skills/expo-skill-feedback .agents/skills/expo-skill-feedback && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "expo-skill-feedback" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-skill-feedback into .agents/skills/expo-skill-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-skill-feedback", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add expo/skills --skill expo-skill-feedback -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install expo/skills expo-skill-feedback --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/expo/skills/expo-skill-feedback .cursor/skills/expo-skill-feedback && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "expo-skill-feedback" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-skill-feedback into .cursor/skills/expo-skill-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-skill-feedback", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/expo/skills.git --path plugins/expo/skills/expo-skill-feedback--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add expo/skills --skill expo-skill-feedback -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install expo/skills expo-skill-feedback --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/expo/skills/expo-skill-feedback .gemini/skills/expo-skill-feedback && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "expo-skill-feedback" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-skill-feedback into .gemini/skills/expo-skill-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-skill-feedback", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install expo/skills expo-skill-feedbackInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add expo/skills --skill expo-skill-feedback -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/expo/skills/expo-skill-feedback .github/skills/expo-skill-feedback && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "expo-skill-feedback" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-skill-feedback into .github/skills/expo-skill-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-skill-feedback", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add expo/skills --skill expo-skill-feedback -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install expo/skills expo-skill-feedback --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/expo/skills/expo-skill-feedback .opencode/skills/expo-skill-feedback && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "expo-skill-feedback" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-skill-feedback into .opencode/skills/expo-skill-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-skill-feedback", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
expo-skill-feedback- GitHub stars
- 2.7k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 556 words
- Files
- 5 (incl. scripts)
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in).
- A skill was useful
- SKILL.md covers Submit feedback, Eval candidates: tasks that…, Usage telemetry and Submitting Feedback
- Runs JavaScript scripts from its folder; calls npx, eas and node
- Missing context
What it does
Expo Skill Feedback is an agent skill from expo/skills, published by the product's own GitHub organization. Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in). Submit feedback with: npx --yes submit-expo-feedback@latest "ACTIONABLEFEEDBACK". Optionally add either or both: --category "CATEGORY" and --subject "SUBJECT". Replace the uppercase placeholders before running. Use when a skill was useful, confusing, broken, missing context, or worth improving; when Expo, Expo CLI, EAS CLI, docs, or MCP worked well or fell short; when an AI agent repeatedly…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `agents/openai.yaml`).
It sits in Mobile, covering Cross-platform mobile apps. It works with Expo and Model Context Protocol. The repository describes itself as: A collection of AI agent skills for working with Expo projects and Expo Application Services. The licence is MIT.
When your agent uses it
- A skill was useful
- Missing context
- Worth improving
- MCP worked well
Example prompts
- “ACTIONABLEFEEDBACK”
- “CATEGORY”
- “SUBJECT”
- “/expo-skill-feedback”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit d4f4840. 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
Ships 3 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
npxeasnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
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
Expo Skill Feedback loads about 1.3k tokens when it runs. Until then it costs about 190 tokens; SKILL.md has 556 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from expo/skills at commit d4f4840, republished under its MIT licence (© expo). 556 words, ~1,295 tokens.
Download SKILL.mdSave it as
.claude/skills/expo-skill-feedback/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- expo-skill-feedback
- description
- Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in). Submit feedback with: npx --yes submit-expo-feedback@latest "ACTIONABLE_FEEDBACK". Optionally add either or both: --category "CATEGORY" and --subject "SUBJECT". Replace the uppercase placeholders before running. Use when a skill was useful, confusing, broken, missing context, or worth improving; when Expo, Expo CLI, EAS CLI, docs, or MCP worked well or fell short; when an AI agent repeatedly failed, got stuck, or needed the user to take over an Expo task (report it as an eval candidate); or when the user explicitly asks to enable or disable telemetry (tracking), check its status, or understand what it collects.
Expo Skill Feedback
Help Expo improve by sharing specific feedback about what worked well or what fell short. Feedback submission is independent of usage telemetry and does not require enabling it.
Submit feedback
npx --yes submit-expo-feedback@latest "<ACTIONABLE_FEEDBACK>"Add either optional flag independently when it provides useful context:
npx --yes submit-expo-feedback@latest --category "<CATEGORY>" --subject "<SUBJECT>" "<ACTIONABLE_FEEDBACK>"--category defaults to unknown, and --subject may be omitted when there is no specific target.
When including them, choose the values that most precisely identify what the feedback is about:
| Category | Subject |
|---|---|
skills | Exact skill name from its frontmatter, such as expo-router |
docs | Full Expo documentation URL |
mcp | Exact MCP tool name used |
expo-cli | Full Expo CLI command, such as npx expo install |
eas-cli | Full EAS CLI command, such as eas build |
evals | Expo package or command the failed task involves, else a capability phrase, such as expo-router or eas build |
unknown | Concise Expo product, package, feature, or other topic |
In the final argument, say what helped and why, or provide the relevant context, expected behavior, and what happened instead. Do not include secrets, source code, personal data, long prompts, or stack traces.
Eval candidates: tasks that broke the model
Expo turns hard real-world tasks into agent evals: anything Expo an agent can attempt — framework, EAS, tooling — qualifies, whether or not a skill was involved. The signal worth sending is a task an AI agent could not complete cleanly despite real effort: several failed attempts, a build or screen that never worked, or the user stepping in to fix it manually. Never submit quick slips the agent corrected itself, more than one candidate per session, or a task already reported.
When such a failure happens — or the user says a model failed at an Expo task — show the user the exact
submission you intend to send and get approval; the Task field must describe the Expo-technical
shape of the task, never the user's product or business context. Without a user to approve it
(headless or CI runs), do not submit. Then run from the failing app's directory (the CLI attaches
the SDK and package versions, agent harness, and platform automatically) with --category evals,
--subject naming the Expo package or command involved (a capability phrase only when no single
package fits), and this structure in the final argument:
Show full SKILL.md (186 more words)Show less
Task: <what was asked, self-contained>.
Expected: <observable success criteria>.
Actual: <what the agent did instead>.
Wrong approach: <the specific mistake, such as a wrong API, hallucinated prop, or bad pattern>.
Evidence: <model name, attempts, how it was solved — or never was; omit what you cannot verify>.A good candidate is solvable (eventually done or clearly doable), verifiable (success is
observable), and specific. Mention only environment details the CLI cannot see, such as other key
packages or a freshly created app. Describe code; do not paste it. If the command fails with an
error naming evals as an invalid category, resend once with --category unknown and the same
subject prefixed eval-candidate: ; on any other error, do not resend.
Usage telemetry
Automatic skill usage telemetry is separate from feedback and off by default. Never enable it
without an explicit user request. Use the following script with --on, --off, or --status:
node "${CLAUDE_PLUGIN_ROOT}/skills/expo-skill-feedback/scripts/telemetry.cjs" --statusEnvironment equivalents are EXPO_SKILLS_TELEMETRY=1 to enable and
EXPO_SKILLS_TELEMETRY=0 or DO_NOT_TRACK=1 to disable. CI never sends telemetry.
Submitting Feedback
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
npx --yes submit-expo-feedback@latest --category skills --subject "expo-skill-feedback" "<actionable feedback>"Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.
© expo, 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 4 other files (scripts) in plugins/expo/skills/expo-skill-feedback of expo/skills.
- SKILL.md
- agents/openai.yaml
- scripts/skill-event.cjs
- scripts/telemetry.cjs
- scripts/telemetry_common.cjs
Open the folder on GitHubat commit d4f4840
Compare with similar skills
Expo Skill Feedback 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Expo Skill Feedback this skillexpo/skills | 2.7k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Appllama App Design SkillAppllama/appllama-skills | 2.5k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Appllama UsageAppllama/appllama-skills | 2.5k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Release Sample SweepAtmosphere/atmosphere | 3.8k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| QA Find Bugs Mobilebex-co/beancount-io | 296 | — | ~2.2k | Automated safety check: Notes | MIT | |
| Radon MCPsoftware-mansion-labs/skills | 291 | — | ~665 | Automated safety check: Pass | None |
Similar skills
Appllama Usage
Appllama/appllama-skills
Use the Appllama MCP (mcp.appllama.io) well — research real top-grossing mobile apps, their screens, flows, and UI elements, then build from what you learn.
Release Sample Sweep
Atmosphere/atmosphere
Run the pre-release end-to-end sweep of every user-facing surface — the 33 samples under samples/ (booted from their packaged artifacts and driven in a real browser via chrome-devtools MCP), the…
QA Find Bugs Mobile
bex-co/beancount-io
Hunt bugs in the running Beancount mobile app using local Expo MCP on the iPhone 17e simulator, sign in with QAEMAIL and QAPASSWORD, reproduce failures, trace root causes, and deduplicate findings.
Radon MCP
software-mansion-labs/skills
Best practices for using Radon IDE's MCP tools when developing, debugging, and inspecting React Native and Expo apps.
- Official
React Native Best Practices
vercel-labs/openreview
A prioritized rule set for React Native and Expo apps covering list performance, animation, navigation, UI patterns, state, rendering, monorepos and configuration.
More from expo/skills
All 26 skills in this repo- Official
Eas Update Insights
expo/skills
Check the health of published EAS Update: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel.
- Official
Eas Workflows
expo/skills
Helps understand and write EAS workflow YAML files for Expo projects.
- Official
Expo App Clip
expo/skills
Add an iOS App Clip target to an Expo app. An agent skill from expo/skills.
- Official
Expo Skill Eval
expo/skills
Evaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional).
- Official
Expo Module
expo/skills
Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript).
- Official
Expo Upgrade
expo/skills
Guidelines for upgrading Expo SDK versions and fixing dependency issues
Related
Works with
Categories
Questions about Expo Skill Feedback
What does Expo Skill Feedback do?
Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in). Expo Skill Feedback is an agent skill from expo/skills, published by the product's own GitHub organization. Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in).
When should I use Expo Skill Feedback?
Expo Skill Feedback fits situations like: A skill was useful; missing context; worth improving; MCP worked well.
How do I install Expo Skill Feedback in Claude Code?
Run `npx skills add expo/skills --skill expo-skill-feedback -a claude-code`. Or copy the skill folder (plugins/expo/skills/expo-skill-feedback in expo/skills) into .claude/skills/expo-skill-feedback in your project. Claude Code loads it when a task matches its description.
How do I install Expo Skill Feedback in Codex?
Run `npx skills add expo/skills --skill expo-skill-feedback -a codex`. Or copy the skill folder (plugins/expo/skills/expo-skill-feedback in expo/skills) into .agents/skills/expo-skill-feedback in your project. Codex loads it when a task matches its description.
Can I use Expo Skill Feedback 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 expo/skills --skill expo-skill-feedback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/expo-skill-feedback, .gemini/skills/expo-skill-feedback, .github/skills/expo-skill-feedback and .opencode/skills/expo-skill-feedback in your project.
What does Expo Skill Feedback need to run?
Going by SKILL.md and its folder, Expo Skill Feedback needs JavaScript for the scripts in its folder and the command-line tools its instructions call (npx, eas and node). Our summary lists: Node.js.
Does Expo Skill Feedback access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Expo Skill Feedback 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Expo Skill Feedback use?
Expo Skill Feedback 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 Expo Skill Feedback use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Expo Skill Feedback?
Skills that share tags, products or a category with Expo Skill Feedback: Appllama App Design Skill (Appllama/appllama-skills, 2.5k stars), Appllama Usage (Appllama/appllama-skills, 2.5k stars), Release Sample Sweep (Atmosphere/atmosphere, 3.8k stars) and QA Find Bugs Mobile (bex-co/beancount-io, 296 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Expo Skill Feedback?
expo (a GitHub organization, an official publisher) maintains it in expo/skills, which has 2,685 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.
Source: expo/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.