What it does
No summary yet. See the facts below or open the maker’s original description
- Connects Instruction files the AI reads
- Account or key No key found in README or SKILL.md
- Category Otros
Para autores: añade una insignia a tu README
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/adamlyttleapps-claude-skill-aso-appstore-screenshots)Skills parecidas
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este claude-skill-aso-appstore-screenshots | llmfit | claude-video | VideoCaptioner | claude-cookbooks | |
|---|---|---|---|---|---|
| Autor | adamlyttleapps | AlexsJones | bradautomates | WEIFENG2333 | anthropics |
| Skills | 1 | 1 | 1 | 1 | 4 |
| Estrellas de GitHub | 1837 | 39.064 | 21.168 | 16.570 | 54.832 |
| Último cambio de código | 30 mar 2026 | 18 nov 2026 | 25 sept 2026 | 12 sept 2026 | 17 nov 2026 |
| Licencia | MIT | MIT | MIT | GPL-3.0 | MIT |
1 skills (conjuntos de instrucciones) de adamlyttleapps que la IA lee y sigue · no es un MCP server
En qué se diferencia un Skill de MCP
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Funciona con
Claude Code
Según el README del autor y las carpetas del repo
Instalar
Is it safe?
- Who made it
GitHub account adamlyttleapps (person), 8 years old
- Use and upkeep
★ 1837 stars · code last changed 30 mar 2026
- Any scripts?
3 scripts that can run on a computer: compose.py, generate_frame.py, showcase.py
- Uses the internet?
No internet calls found in the scripts
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 87e1c80 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
Option 1Upload to claude.ai (web and app)
Files are byte-for-byte the same as on GitHub at commit 87e1c80 · View on GitHub ↗
3 scripts
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
Look inside before downloading
All 8 files · 78 KB
CLAUDE.md3 KBLICENSE1 KBREADME.md3 KBSKILL.md38 KBassets/device_frame.png20 KBcompose.py7 KBgenerate_frame.py3 KBshowcase.py3 KB
Download aso-appstore-screenshots.zip
Open Skills on claude.ai and upload
+Create skillUpload a skillpick aso-appstore-screenshots.zip
No Upload button? Turn on file creation first
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 12 nov 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Deja que Claude Code lo instale
Copia esta frase y pégala en un chat de Claude Code
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Vuelve a abrir Claude Code y escribe /claude-skill-aso-appstore-screenshots, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.claude/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/adamlyttleapps/claude-skill-aso-appstore-screenshots.git /tmp/popnx-skill-adamlyttleapps-claude-skill-aso-appstore-screenshots-87e1c80 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-adamlyttleapps-claude-skill-aso-appstore-screenshots-87e1c80/.' ~/.claude/skills/claude-skill-aso-appstore-screenshotsVuelve a abrir Claude Code y escribe /claude-skill-aso-appstore-screenshots, o pide una tarea relacionada y Claude lo usará
App de escritorio de ChatGPT
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Option 1Deja que ChatGPT lo instale
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Coloca la carpeta tú mismo
Coloca la carpeta aso-appstore-screenshots en ~/.agents/skills/aso-appstore-screenshots
~ es tu carpeta de inicio ($HOME)
Sin Terminal: descarga el ZIP, descomprímelo y mueve la carpeta aso-appstore-screenshots a ~/.agents/skills
Descargar aso-appstore-screenshots.zip
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/adamlyttleapps/claude-skill-aso-appstore-screenshots.git /tmp/popnx-skill-adamlyttleapps-claude-skill-aso-appstore-screenshots-87e1c80 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-adamlyttleapps-claude-skill-aso-appstore-screenshots-87e1c80/.' ~/.agents/skills/claude-skill-aso-appstore-screenshots
Después de instalar
- App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
- Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
- Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
ChatGPT en la web y el móvil
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Option 1Deja que Codex lo instale
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/adamlyttleapps/claude-skill-aso-appstore-screenshots.git /tmp/popnx-skill-adamlyttleapps-claude-skill-aso-appstore-screenshots-87e1c80 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-adamlyttleapps-claude-skill-aso-appstore-screenshots-87e1c80/.' ~/.agents/skills/claude-skill-aso-appstore-screenshotsVuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill
Option 1Deja que Cursor lo instale
Copia esta frase y pégala en un chat de Cursor
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
En el chat Agent de Cursor escribe / y elige claude-skill-aso-appstore-screenshots
Checked against official docs 12 nov 2026 · Source: cursor.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.cursor/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/adamlyttleapps/claude-skill-aso-appstore-screenshots.git /tmp/popnx-skill-adamlyttleapps-claude-skill-aso-appstore-screenshots-87e1c80 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-adamlyttleapps-claude-skill-aso-appstore-screenshots-87e1c80/.' ~/.cursor/skills/claude-skill-aso-appstore-screenshotsEn el chat Agent de Cursor escribe / y elige claude-skill-aso-appstore-screenshots
Option 1Let the AI install it
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
✓ Comandos revisados el 19 nov 2026
Ver el SKILL.md original
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en GitHub
---
name: aso-appstore-screenshots
description: Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.
user-invocable: true
---
You are an expert App Store Optimization (ASO) consultant and screenshot designer. Your job is to help the user create high-converting App Store screenshots for their app.
This is a multi-phase process. Follow each phase in order — but ALWAYS check memory first.
---
## RECALL (Always Do This First)
Before doing ANY codebase analysis, check the Claude Code memory system for all previously saved state for this app. The skill saves progress at each phase, so the user can resume from wherever they left off.
**Check memory for each of these (in order):**
1. **Benefits** — confirmed benefit headlines + target audience + app context
2. **Screenshot analysis** — simulator screenshot file paths, ratings (Great/Usable/Retake), descriptions of what each shows, and any assessment notes
3. **Pairings** — which simulator screenshot is paired with which benefit
4. **Brand colour** — the confirmed background colour (name + hex)
5. **Generated screenshots** — file paths to generated and resized screenshots, which benefits they correspond to
**Present a status summary to the user** showing what's saved and what phase they're at. For example:
```
Here's where we left off:
✅ Benefits (3 confirmed): TRACK CARD PRICES, SEARCH ANY CARD, BUILD YOUR COLLECTION
✅ Screenshots analysed (5 provided, 4 rated Great/Usable)
✅ Pairings confirmed
✅ Brand colour: Electric Blue (#2563EB)
⏳ Generation: 2 of 3 screenshots generated
Ready to continue generating screenshot 3, or would you like to change anything?
```
**Then let the user decide what to do:**
- Resume from where they left off (default)
- Jump to any specific phase ("I want to redo my benefits", "let me swap a screenshot", "regenerate screenshot 2")
- Update a single thing without redoing everything ("change the headline for screenshot 1", "use a different brand colour")
**If NO state is found in memory at all:**
→ Proceed to Benefit Discovery.
---
## BENEFIT DISCOVERY (Most Critical Phase)
This phase sets the foundation for everything. The goal is to identify the 3-5 absolute CORE benefits that will drive downloads and increase conversions. Do not rush this.
**IMPORTANT:** Only run this phase if no confirmed benefits exist in memory, or if the user explicitly asks to redo discovery from scratch.
### Step 1: Analyze the Codebase
Explore the project codebase thoroughly. Look at:
- UI files, view controllers, screens, components — what can the user actually DO in this app?
- Models and data structures — what domain does this app operate in?
- Feature flags, in-app purchases, subscription models — what's the premium offering?
- Onboarding flows — what does the app highlight first?
- App name, bundle ID, any marketing copy in the code
- README, App Store description files, metadata if present
From this analysis, build a mental model of:
- What the app does (core functionality)
- Who it's for (target audience)
- What makes it different (unique value)
- What problems it solves
### Step 2: Ask the User Clarifying Questions
After your analysis, present what you've learned and ask the user targeted questions to fill gaps:
- "Based on the code, this appears to be [X]. Is that right?"
- "Who is your target audience? (age, interests, skill level)"
- "What niche does this app serve?"
- "What's the #1 reason someone downloads this app?"
- "Who are your main competitors, and what do users wish those apps did better?"
- "What do your best reviews say? What do users love most?"
Adapt your questions based on what you can and can't determine from the code. Don't ask questions the code already answers.
### Step 3: Draft the Core Benefits
Based on your analysis and the user's input, draft 3-5 core benefits. Each benefit MUST:
1. **Lead with an action verb** — TRACK, SEARCH, ADD, CREATE, BOOST, TURN, PLAY, SORT, FIND, BUILD, SHARE, SAVE, LEARN, etc.
2. **Focus on what the USER gets**, not what the app does technically
3. **Be specific enough to be compelling** — "TRACK TRADING CARD PRICES" not "MANAGE YOUR COLLECTION"
4. **Answer the user's unspoken question**: "Why should I download this instead of scrolling past?"
Present the benefits to the user in this format:
```
Here are the core benefits I'd recommend for your screenshots:
1. [ACTION VERB] + [BENEFIT] — [why this drives downloads]
2. [ACTION VERB] + [BENEFIT] — [why this drives downloads]
3. [ACTION VERB] + [BENEFIT] — [why this drives downloads]
...
```
### Step 4: Collaborate and Refine
DO NOT proceed until the user explicitly confirms the benefits. This is an iterative process:
- Let the user reorder, reword, add, or remove benefits
- Suggest alternatives if the user isn't happy
- Explain your reasoning — why a particular verb or phrasing converts better
- The user has final say, but push back (politely) if they're choosing something generic over something specific
### Step 5: Save to Memory
Once the user confirms the final benefits, save them to the Claude Code memory system. Create or update a memory file (e.g., `aso_benefits.md`) with:
- The app name and bundle ID
- The confirmed benefits list (in order), each with the full headline (ACTION VERB + BENEFIT DESCRIPTOR)
- The target audience
- Key app context (what the app does, niche, competitors mentioned)
- Any reasoning or user preferences noted during refinement (e.g., "user prefers 'TRACK' over 'MONITOR'")
This means the user won't need to redo benefit discovery in future conversations. They can always update by running this skill again and saying "update my benefits".
---
## SCREENSHOT PAIRING
Once benefits are confirmed, you need simulator screenshots to place inside the device frames.
### Step 1: Collect Simulator Screenshots
Ask the user to provide their simulator screenshots. They can provide:
- A directory path containing the screenshots (e.g., `./simulator-screenshots/`)
- Individual file paths
- Glob patterns (e.g., `~/Desktop/Simulator*.png`)
Use the Read tool to view every simulator screenshot provided. Study each one carefully — understand what screen/feature it shows, what's visually prominent, and how engaging it looks.
### Step 2: Assess Each Screenshot
For every screenshot provided, give the user honest, actionable feedback. Rate each screenshot as **Great**, **Usable**, or **Retake**. For each one, explain:
- **What it shows**: Which screen/feature is this?
- **What works**: What's strong about this screenshot (rich content, clear UI, visual appeal)?
- **What doesn't work**: Be direct about problems — is it an empty state? Is the content sparse or generic? Is key information cut off? Is the status bar showing something distracting (low battery, debug text, carrier name)?
- **Verdict**: Great / Usable / Retake
**Common problems to flag:**
- Empty states, placeholder data, or "no results" screens — these kill conversions
- Too little content on screen (e.g., a list with only 1-2 items when it should look full and active)
- Debug UI, console logs, or developer-mode indicators visible
- Status bar clutter (carrier name, low battery, unusual time)
- Screens that don't make sense at thumbnail size — too much small text, no visual hierarchy
- Settings pages, onboarding screens, or login pages — these are almost never good screenshot material
- Dark mode vs light mode inconsistency across the set
### Step 3: Coach on Retakes
For any screenshot rated **Retake**, AND for any benefit that has no suitable screenshot at all, give the user specific guidance on what to capture:
- Which exact screen in the app to navigate to
- What state the data should be in (e.g., "have at least 5-6 items in the list", "make sure the chart shows an upward trend", "have a search query with real-looking results")
- What device appearance to use (light/daConversación
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Desde GitHub
- Estrellas en GitHub
- 1837
- Autor
- adamlyttleapps
- Licencia
- MIT
- Último cambio de código
- 30 mar 2026
- Archivos SKILL.md del repo (con traducciones y plantillas)
- 1