- Home
- Skills
- Prompt & Skill Engineering
- Mobile ASO Kit
Works with the AI Agents you already use
Mobile ASO Kit
Maintaining an app store listing is a fragmented manual process prone to keyword waste and policy rejection.
Free
Mobile ASO Kit
Example session with this skill installed
Run an ASO audit for my iOS app with ID 123456789 in the US store. It feels like our keyword placement is suboptimal.
- Read your context and instructions
- Compiled the mobile aso kit
I have completed the audit of your App Store listing by fetching live data and checking it against the current knowledge base.
Audit — Habitly
Rating: iOS 4.7 · Play 3.9 ✗ — below 4.0, ratings first
Checker: 2 errors, 3 warnings
Scorecard
| Field | iOS | Play | Note |
|---|---|---|---|
| Name / title | ✓ | ! | Play title is only 18 chars; wasting space |
| Subtitle | ✓ | ✗ | Play short description repeats the first line |
| Keyword Field | ! | — | 72/100 chars; missing 28 chars of potential traffic |
| Description | ✓ | ! | Primary keyword missing from first 3 sentences on Play |
Fixes
Now (no release needed)
iOS Promotional Text: The current text is generic. I recommend adding "Featured in Top 10 Productivity Apps" to improve conversion.
Play Short Description: Update to "Track habits, set goals, and improve daily routines" to target specific user benefits.
Next Release
- Keyword Field: Add "routine,planner,tracker,goals,atomic,discipline" to fill the remaining 28 characters.
Play Full Description: Move the head term "Habit Tracker" into the first paragraph. It is currently buried in the feature list.
Next steps
- Review the detailed fixes in
aso/audit.md. - Run
/aso-keywordsto generate a denser keyword set for the next update. - Address the Play Store rating (3.9) before the next major feature push.
Connects securely to your tools. The creator never sees your data.
About this skill
Maintaining an app store listing is a fragmented manual process prone to keyword waste and policy rejection. aso-kit automates the text-based App Store Optimization lifecycle by reading your repository, fetching live store data, and applying a dated, evidence-based knowledge base to your metadata. It handles everything from initial competitive research to release notes and localization gates.
What it does
- App Context Extraction reads codebases, nav graphs, and READMEs to identify core features and audiences.
- Keyword Research seeds terms from your app and expands them using live autocomplete data from the App Store and Google Play.
- Metadata Generation writes titles, subtitles, and descriptions tailored to store limits and keyword targets.
- Listing Audits checks live or draft listings against store policies and ranking factors, providing prioritized fixes.
- Release Automation generates formatted "What's New" notes directly from git history and conventional commits.
- Knowledge Refresh verifies field limits and store endpoints against official documentation to prevent drift.
How it works
- Initialize with
aso-contextto map your app's features and fetch live store snapshots. - Research with
aso-keywordsto generate a scored, localized keyword set and pack the iOS keyword field. - Draft with
aso-metadatato create store-ready text assets that pass built-in policy and length checks. - Audit existing listings to find gaps in ranking potential or policy compliance.
Frameworks & tools
The kit uses a custom Node.js backend for store lookups and suggestions, interacting with Git, Fastlane metadata structures, and a local Markdown-based knowledge base.
Why this beats prompting it yourself
Generic LLMs often hallucinate character limits and store policies, leading to rejected builds or wasted keyword slots. This skill uses a verifiable knowledge base and precise character counting to ensure every byte contributes to your app's visibility.
Use cases
- Optimizing a new app launch for specific target locales.
- Auditing a live listing that has dropped in search rankings.
- Generating localized store descriptions for international expansion.
- Automated generation of App Store release notes from technical commit logs.
Known limitations
Does not generate or edit icons, screenshots, or video assets. Localization requires a pre-existing primary locale that has been live for at least 4 to 8 weeks to ensure valid source data.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Prompt & Skill Engineering.
Text-based ASO only; no image/video generation. Localization requires 4-8 weeks of live data from the primary listing. Requires local Node.js scripts for store lookups.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 2 days ago
- Free with an Agensi account
- Software
Node.js
Git