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,064 | 21,168 | 16,570 | 54,832 |
| 最終コード更新 | 2026年3月30日 | 2026年11月18日 | 2026年9月25日 | 2026年9月12日 | 2026年11月17日 |
| ライセンス | MIT | MIT | MIT | GPL-3.0 | MIT |
adamlyttleapps による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
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 1Claude 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 が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
ターミナルを開く
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-screenshotsClaude Code を開き直し、/claude-skill-aso-appstore-screenshots と入力するか関連する作業を頼むと Claude が自動で使います
ChatGPT デスクトップアプリ
ChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
Option 1ChatGPT にインストールしてもらう
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 が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
ターミナルを開く
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
Web 版とモバイル版の ChatGPT
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1Codex にインストールしてもらう
この文をコピーして 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 が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
ターミナルを開く
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-screenshotsCodex を開き直して関連する作業を頼むと、Codex が skill を一覧に出します
Option 1Cursor にインストールしてもらう
この文をコピーして 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 が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
ターミナルを開く
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-screenshotsCursor の 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
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、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