● Community
furkancingoz
⚡ Instant
aso-skill
by furkancingoz · furkancingoz/aso-skill
End-to-end App Store Optimization from Claude Code: metadata + competitor analysis + screenshots + direct App Store Connect submission via JWT.
Six commands covering ASO lifecycle: metadata generation with character validation, competitor analysis via iTunes API, AI-generated screenshots (Gemini MCP), App Store Connect API submission (JWT), version management, and auto-generated legal (privacy, terms). Eliminates web interface clicking for iOS submissions.
Why use it
Key features
- Metadata generation + character limit validation
- Competitor analysis from the free iTunes API
- AI screenshot generation via Gemini MCP
- Direct App Store Connect API via JWT — no web UI clicking
- Phased rollout control
- Auto-generated privacy policy + terms
Live Demo
What it looks like in practice
Use Cases
Real-world ways to use aso-skill
When to use: Conversion rate on your product page is flat and you want a data-driven refresh.
Flow
-
Run competitor analysis
Use aso-skill to pull the top 10 competitors for 'habit tracker' in the US store. Compare their subtitles and keywords.✓ Copied
→ Comparison table with frequency-weighted keyword clusters
-
Generate optimized metadata
Now generate a new title, subtitle, keyword list, and promotional text for my app. Validate character limits.✓ Copied
→ Fields under limit, ranked by estimated impact
-
Submit via ASC API
Push the new metadata to App Store Connect as a new version pending submission.✓ Copied
→ Version draft created; ready for manual review
Outcome: A refreshed listing with a data-grounded story, submitted without clicking through ASC.
Pitfalls
- Keyword stuffing beyond the 100-char field — Skill validates, but double-check — stuffing kills relevance
When to use: You have an IPA ready and want everything else automated.
Prerequisites
- IPA uploaded to App Store Connect — xcode or Transporter
Flow
-
Generate metadata + legal
Generate metadata and auto-draft privacy policy + terms for a meditation app targeting EN/DE/FR.✓ Copied
→ Localized metadata + hosted legal URLs
-
Generate screenshots
Use aso-skill + Gemini MCP to generate 5 App Store screenshots per locale matching the app's visual identity.✓ Copied
→ PNG set at correct resolutions
-
Submit for review
Attach the build, upload screenshots, submit for review with a phased 7-day rollout.✓ Copied
→ Version status: Waiting For Review
Outcome: App in review without opening ASC manually.
Pitfalls
- Screenshot text violates store guidelines — Ask the skill to keep screenshot text minimal and within safe areas
When to use: Every quarter or when competitors shift their keyword strategy.
Flow
-
Diff keyword sets vs last quarter
Compare this quarter's competitor keyword cluster against last quarter's. What's new?✓ Copied
→ Added / dropped keywords
-
Propose updates
Propose a keyword update — keep my wins, capture 2–3 new opportunities.✓ Copied
→ Revised 100-char keyword field
Outcome: Live keyword edit that reflects reality, not 6-month-old research.
Combinations
Pair with other MCPs for X10 leverage
Use the other ASO skill's reporting layer over this one's execution layer
After aso-skill submits, use claude-code-aso-skill reporting to summarize the changes.✓ Copied
Commit the metadata and screenshots to repo for version control
Write metadata to fastlane/metadata and commit with the version tag.✓ Copied
Cost & Limits
What this costs to run
- API quota
- iTunes Search API: free, lightly rate-limited. App Store Connect: per-account quota.
- Tokens per call
- Large for screenshot generation; moderate otherwise
- Monetary
- Free skill; Gemini usage is separate
- Tip
- Cache competitor data locally for a quarter — it doesn't change hourly
Security
Permissions, secrets, blast radius
Minimum scopes: App Store Connect: App Manager on one app (prefer) over admin
Credential storage: JWT .p8 key stored locally; reference via path in env, never check into git
Data egress: iTunes API (public), Apple ASC API, Gemini MCP if screenshots enabled
Never grant: Account Holder role to the key used by the skill
- A leaked .p8 gives full write on your apps — rotate if you ever commit it.
Troubleshooting
Common errors and fixes
ASC 401
JWT expired (max 20min) — regenerate; check issuer id and key id are correct
Verify: curl with the JWT against https://api.appstoreconnect.apple.com/v1/apps
Metadata field rejected for character limit
Skill validation missed localization — validate per-locale
Screenshots wrong resolution
Specify device list explicitly; Apple's required sizes change
Alternatives
aso-skill vs others
| Alternative | When to use it instead | Tradeoff |
|---|
| claude-code-aso-skill | You want the agent-based ASO reporting framework | Less direct ASC integration |
| Fastlane deliver | You already have a Fastlane pipeline | No AI metadata drafting |