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 其他
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/adamlyttleapps-claude-skill-aso-appstore-screenshots)相似的 Skill
同类工作,排序与 Skill 列表相同
| 本项 claude-skill-aso-appstore-screenshots | llmfit | claude-video | VideoCaptioner | claude-cookbooks | |
|---|---|---|---|---|---|
| 作者 | adamlyttleapps | AlexsJones | bradautomates | WEIFENG2333 | anthropics |
| Skill 数 | 1 | 1 | 1 | 1 | 4 |
| GitHub 星标 | 1,837 | 39,096 | 21,249 | 16,577 | 54,867 |
| 最近代码更新 | 2026年3月30日 | 2026年11月18日 | 2026年9月25日 | 2026年9月12日 | 2026年11月17日 |
| 许可证 | MIT | MIT | MIT | GPL-3.0 | MIT |
Skill 和 MCP 有什么不同
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
适用的应用
Claude Code
依据开发者 README 和 repo 中的文件夹
安装
Is it safe?
- Who made it
GitHub account adamlyttleapps (person), 8 years old
- Use and upkeep
★ 1,837 stars · code last changed 2026年3月30日
- 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
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
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 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1让 Claude Code 帮你安装
复制这句话,粘贴到 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
重新打开 Claude Code,输入 /claude-skill-aso-appstore-screenshots,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.claude/skills
这条命令把 repo 下载到临时文件夹,只复制含 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-screenshots重新打开 Claude Code,输入 /claude-skill-aso-appstore-screenshots,或直接提出相关任务,Claude 会自动选用
ChatGPT 桌面应用
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
Option 1让 ChatGPT 帮你安装
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
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 2自己放入文件夹
把 aso-appstore-screenshots 文件夹放到 ~/.agents/skills/aso-appstore-screenshots
~ 是你的主文件夹($HOME)
不用终端:下载 ZIP,解压后把 aso-appstore-screenshots 文件夹移到 ~/.agents/skills
下载 aso-appstore-screenshots.zip
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 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
安装之后
- ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
- 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
- Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
网页版和手机版 ChatGPT
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1让 Codex 帮你安装
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 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 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 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重新打开 Codex 并提出相关任务,Codex 会列出这个 skill
Option 1让 Cursor 帮你安装
复制这句话,粘贴到 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
在 Cursor 的 Agent 聊天中输入 / 并选择 claude-skill-aso-appstore-screenshots
Checked against official docs 2026年11月12日 · Source: cursor.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.cursor/skills
这条命令把 repo 下载到临时文件夹,只复制含 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-screenshots在 Cursor 的 Agent 聊天中输入 / 并选择 claude-skill-aso-appstore-screenshots
Option 1Let the AI install it
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · 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 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月19日
查看原始 SKILL.md
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 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/da讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
来自 GitHub
- GitHub 星标
- 1,837
- 开发者
- adamlyttleapps
- 许可证
- MIT
- 最近代码更新
- 2026年3月30日
- repo 中的 SKILL.md 文件(含译本和模板)
- 1