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.
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.
Install Appllama Usage
$ npx skills add Appllama/appllama-skills --skill appllama-usage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Appllama/appllama-skills appllama-usage --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/Appllama/appllama-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/appllama-usage .claude/skills/appllama-usage && 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 "appllama-usage" agent skill from https://github.com/Appllama/appllama-skills/tree/main/skills/appllama-usage into .claude/skills/appllama-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appllama-usage", 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/Appllama/appllama-skills/tree/main/skills/appllama-usageType 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 Appllama/appllama-skills --skill appllama-usage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Appllama/appllama-skills appllama-usage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Appllama/appllama-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/appllama-usage .agents/skills/appllama-usage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "appllama-usage" agent skill from https://github.com/Appllama/appllama-skills/tree/main/skills/appllama-usage into .agents/skills/appllama-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appllama-usage", 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 Appllama/appllama-skills --skill appllama-usage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Appllama/appllama-skills appllama-usage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Appllama/appllama-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/appllama-usage .cursor/skills/appllama-usage && 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 "appllama-usage" agent skill from https://github.com/Appllama/appllama-skills/tree/main/skills/appllama-usage into .cursor/skills/appllama-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appllama-usage", 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/Appllama/appllama-skills.git --path skills/appllama-usage--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 Appllama/appllama-skills --skill appllama-usage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Appllama/appllama-skills appllama-usage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Appllama/appllama-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/appllama-usage .gemini/skills/appllama-usage && 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 "appllama-usage" agent skill from https://github.com/Appllama/appllama-skills/tree/main/skills/appllama-usage into .gemini/skills/appllama-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appllama-usage", 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 Appllama/appllama-skills appllama-usageInstalls 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 Appllama/appllama-skills --skill appllama-usage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Appllama/appllama-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/appllama-usage .github/skills/appllama-usage && 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 "appllama-usage" agent skill from https://github.com/Appllama/appllama-skills/tree/main/skills/appllama-usage into .github/skills/appllama-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appllama-usage", 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 Appllama/appllama-skills --skill appllama-usage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Appllama/appllama-skills appllama-usage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Appllama/appllama-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/appllama-usage .opencode/skills/appllama-usage && 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 "appllama-usage" agent skill from https://github.com/Appllama/appllama-skills/tree/main/skills/appllama-usage into .opencode/skills/appllama-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appllama-usage", 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
appllama-usage- GitHub stars
- 2.5k
- Used in
- 1 other repo
- Token cost
- ~1.6k tokens
- SKILL.md length
- 781 words
- Files
- 5 (incl. references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 7 steps: Start with get_credits — it's free. It… → Go deep. Design language lives in the… → Media URLs expire in ~1 hour.… → …
- Tasks that involve Mobile UI design
- SKILL.md covers Ground rules (read first), Tool map, The playbooks and Local reference boards
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Appllama Usage is an agent skill from 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. Load when the Appllama MCP is connected and the task involves building a mobile app or screen, researching app design patterns, studying onboarding/paywall/feature flows, improving an existing screen, or whenever an appllama / searchapps / listappscreens tool is available. Covers the tool map, pagination, expiring media, and the full build-from-research…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `references/build-from-scratch.md` and `references/improve-a-screen.md`).
It sits in Mobile, covering Mobile UI design, MCP servers and Cross-platform mobile apps. It works with Model Context Protocol, Expo and React Native. The repository describes itself as: A builder, not just a researcher. Agent skills that turn top-grossing app patterns into native-quality mobile screens. The licence is MIT.
When your agent uses it
- Tasks that involve Mobile UI design
- Tasks that involve MCP servers
- Tasks that involve Cross-platform mobile apps
Example prompts
- “/appllama-usage”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Start with get_credits — it's free. It tells you the balance,
- Go deep. Design language lives in the whole journey, not a sample —
- Media URLs expire in ~1 hour. Download/view what you study promptly.
- Ignore the watermark. Every Appllama image and video carries a small
- Pagination is sequential. Every list response carries next_cursor;
- If you hit a rate limit, wait it out. The per-minute and per-day
- Errors are instructions. Tool errors are written to be acted on
What it can do on your machine
Read from SKILL.md and the folder at commit dd5caae. 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
No URLs in SKILL.md.
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
Appllama Usage loads about 1.6k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 136 tokens; SKILL.md has 781 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from Appllama/appllama-skills at commit dd5caae, republished under its MIT licence (© Appllama). 781 words, ~1,613 tokens.
Download SKILL.mdSave it as
.claude/skills/appllama-usage/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- appllama-usage
- description
- 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. Load when the Appllama MCP is connected and the task involves building a mobile app or screen, researching app design patterns, studying onboarding/paywall/feature flows, improving an existing screen, or whenever an appllama_* / search_apps / list_app_screens tool is available. Covers the tool map, pagination, expiring media, and the full build-from-research playbooks.
- license
- MIT
- metadata.author
- Appllama (appllama.io)
- metadata.version
- 1.1.0
Appllama Usage Skill
Appllama is the design library of top-grossing mobile apps — their real screens, flows, and UI patterns, with revenue and download context. The MCP puts that library in an agent's hands: not just a research tool, a builder's tool. You study what already wins, then you build something better.
Pair this skill with appllama-app-design-skill for every design/implementation step — this skill tells you what to study; that one tells you how to build.
Ground rules (read first)
- Start with
get_credits— it's free. It tells you the balance, limits, and reset date. Pro includes 1,500 credits a month (they reset in full on the 1st, UTC); every other call spends 1 credit. - Go deep. Design language lives in the whole journey, not a sample — walk every screen of the apps that matter for the task, images included. That is exactly what the library is for. The one thing that's against the terms is harvesting: sweeping the catalog to extract the dataset itself rather than to answer a real task. That isn't research, and it's detected server-side.
- Media URLs expire in ~1 hour. Download/view what you study promptly. If links died mid-task, re-request that page for fresh ones — screen ids are durable, links are not.
- Ignore the watermark. Every Appllama image and video carries a small Appllama watermark in the top-left corner. It is provenance, not part of the screen — don't let it skew your read of that corner (status bar, back button, title), and never reproduce it in anything you build.
- Pagination is sequential. Every list response carries
next_cursor; pass it back to continue. You cannot jump to page N — and a cursor only works for the same query that minted it. If a cursor errors, drop it and restart from page one. - If you hit a rate limit, wait it out. The per-minute and per-day limits sit far above real research; on the rare hit, wait the stated time — don't retry-hammer.
- Errors are instructions. Tool errors are written to be acted on (expired cursor → restart; out of credits → tell the user their credits reset on the 1st and they can request more in Settings → Usage).
Show full SKILL.md (418 more words)Show less
Tool map
| Tool | What it gives you | Typical use |
|---|---|---|
get_credits | Balance, limits, reset date. Free. | Session start |
search_apps | 10 apps/page: name, revenue, downloads, rating, launch date, screens count, flow list with screen counts. Natural-language query + filters (revenue/downloads/rating/launch date/price/onboarding steps) + sort + board_id | Find the top apps for a category or need |
get_app | One app in full: ratings breakdown, category rank, IAP pricing, top countries, flows | Decide if an app deserves a deep study |
list_app_screens | 10 screens/page in journey order (welcome → onboarding → paywall → product), each with media URL, flow, UI elements, colors. Filter by flow or section | Walk an app screen by screen |
search_screens | Screens across the whole library. mode="keyword" matches screen names + filters (flow, screen_type, element, app_id); mode="semantic" searches by meaning/visual language | Gather design references for one screen type |
get_screen | One screen in full + up to 5 visually similar screens from other apps. Accepts screen_ref = app_id/screen_id (what appllama.io's "Copy Screen ID" produces) | The user pasted a screen ref; or drill into one reference |
list_flows | The flow taxonomy with screen/app counts | Discover what flows exist for a category |
get_flow_apps | Apps containing a flow, top revenue first | Find the best examples of one flow |
list_ui_elements | ~38 UI-element families with counts (one call) | Vocabulary for element-level research |
get_element_screens | Screens featuring an element family | Study how winners build one component |
list_my_boards | The member's own appllama.io boards (screens / apps / flows) | Find their curation first |
get_board | A board's full contents: screens with media, app profiles, or (app, flow) pairs | When the member curated a board for the task, START from it |
The screen_ref handshake: members can click "Copy Screen ID" on any
screen at appllama.io and paste it to you. It looks like
1393061654/spl_9i075 — feed it straight to
get_screen(screen_ref=...) and you're looking at exactly the screen they
mean, plus its closest siblings across the library.
The playbooks
| Scenario | Reference |
|---|---|
| Build an app from scratch (e.g. "build me a habit tracker") | references/build-from-scratch.md |
| Make an existing screen better | references/improve-a-screen.md |
| Flow & element research; general research method | references/research-methods.md |
Both build playbooks end the same way: the simulator loop from appllama-app-design-skill, repeated until you cannot find a flaw. Research without that loop is decoration.
Local reference boards
When you pull screens for study, save them into a local working structure — links expire in about an hour, but your notes and downloads don't:
research/
<category>/
apps.md # the shortlist: metrics, flows, verdicts
<app-name>/
screens.md # per-screen notes: id, name, flow, elements, colors
img/ # downloaded screens, in journey order
patterns.md # cross-app synthesis: the category's design languageDownload the screens as you study them — synthesis happens with the images side by side, not from metadata. Notes and screen IDs are durable; re-fetch a fresh link from the ID if you ever need the pixels again.
© Appllama, 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 (references) in skills/appllama-usage of Appllama/appllama-skills.
- SKILL.md
- agents/openai.yaml
- references/build-from-scratch.md
- references/improve-a-screen.md
- references/research-methods.md
Open the folder on GitHubat commit dd5caae
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 Appllama/appllama-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Appllama Usage 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 |
|---|---|---|---|---|---|---|
| Appllama Usage this skillAppllama/appllama-skills | 2.5k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Radon MCPsoftware-mansion-labs/skills | 291 | — | ~665 | Automated safety check: Pass | None | |
| Release Sample SweepAtmosphere/atmosphere | 3.8k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Better Designmarvkr/better-design | 254 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Expo Native UIarcboxlabs/linkcode | 156 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Mobile Devcallstackincubator/codex-mobile-dev-plugin | 144 | — | ~5.5k | Automated safety check: Pass | None |
Similar skills
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…
Better Design
marvkr/better-design
Build, improve, and review production interfaces with the Better Design MCP.
Expo Native UI
arcboxlabs/linkcode
Framework (OSS). An agent skill from arcboxlabs/linkcode.
- Official
Mobile Dev
callstackincubator/codex-mobile-dev-plugin
A skill your agent uses when building, running, changing, or debugging local iOS, Android, Expo, React Native, or SwiftUI apps.
React Native Expert
tech-leads-club/agent-skills
Guides React Native and Expo work for cross-platform apps: Expo Router navigation, fast lists, Reanimated animation, platform-specific code and project structure.
More from Appllama/appllama-skills
Appllama App Design Skill
Appllama/appllama-skills
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native).
Related
Works with
Categories
Questions about Appllama Usage
What does Appllama Usage do?
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. Appllama Usage is an agent skill from Appllama/appllama-skills.io) well — research real top-grossing mobile apps, their screens, flows, and UI elements, then build from what you learn.
When should I use Appllama Usage?
Appllama Usage fits situations like: tasks that involve Mobile UI design; tasks that involve MCP servers; tasks that involve Cross-platform mobile apps.
How do I install Appllama Usage in Claude Code?
Run `npx skills add Appllama/appllama-skills --skill appllama-usage -a claude-code`. Or copy the skill folder (skills/appllama-usage in Appllama/appllama-skills) into .claude/skills/appllama-usage in your project. Claude Code loads it when a task matches its description.
How do I install Appllama Usage in Codex?
Run `npx skills add Appllama/appllama-skills --skill appllama-usage -a codex`. Or copy the skill folder (skills/appllama-usage in Appllama/appllama-skills) into .agents/skills/appllama-usage in your project. Codex loads it when a task matches its description.
Can I use Appllama Usage 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 Appllama/appllama-skills --skill appllama-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/appllama-usage, .gemini/skills/appllama-usage, .github/skills/appllama-usage and .opencode/skills/appllama-usage in your project.
What does Appllama Usage need to run?
SKILL.md names no scripts, command-line tools or credentials: Appllama Usage is instructions for the agent only.
Does Appllama Usage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Appllama Usage 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 Appllama Usage use?
Appllama Usage is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Appllama Usage use?
About 1.6k tokens (SKILL.md is roughly 6.5k 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.1k tokens, read only when the agent opens those files.
What are the alternatives to Appllama Usage?
Skills that share tags, products or a category with Appllama Usage: Radon MCP (software-mansion-labs/skills, 291 stars), Release Sample Sweep (Atmosphere/atmosphere, 3.8k stars), Better Design (marvkr/better-design, 254 stars) and Expo Native UI (arcboxlabs/linkcode, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Appllama Usage?
Appllama (a GitHub organization) maintains it in Appllama/appllama-skills, which has 2,451 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 6, 2026.
Source: Appllama/appllama-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.