asc-aso-audit

Audit App Store metadata for keyword waste, field utilization, and cross-locale gaps.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-aso-audit-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-aso-audit
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-aso-audit
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-aso-audit-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? App Store metadata often wastes keyword budget, leaves fields underutilized, and ships unlocalized keywords across locales, reducing search visibility. This Skill audits locally pulled App Store Connect metadata and surfaces concrete ASO issues without requiring network access. ## Core Features & Use Cases - Offline Metadata Checks: Detects keyword duplication between subtitle and keywords, underutilized fields, missing fields, bad keyword separators, and cross-locale keyword gaps against canonical metadata files. - Keyword Gap Analysis: Uses Astro MCP to extract competitor keywords, retrieve suggestions, and check rankings per store territory, then diffs them against local metadata. - Non-Latin Script Handling: Applies correct tokenization for Arabic (ال-prefix stripping), Chinese/Japanese/Korean, and Cyrillic metadata when checking keyword overlap. - Use Case: After running asc metadata pull for your app, run this audit to discover that your keywords field is only 62% utilized, contains spaces after commas, and that your Arabic locale keywords are identical to en-US. ## Quick Start Run an ASO audit on the metadata I pulled into ./metadata for my app and report keyword gaps and field utilization issues.

Frequently Asked Questions about asc-aso-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit App Store keywords for ASO issues?▼

Pull your metadata locally with asc metadata pull, then run the audit to check for keyword duplication between subtitle and keywords, underutilized fields, bad separators, and unlocalized locales. Results are reported with severity levels and specific fix recommendations.

What ASO checks can run offline without network access?▼

Six offline checks run against local metadata files: keyword waste, underutilized fields, missing fields, bad keyword separators, cross-locale keyword gaps, and description keyword coverage. Only the Astro MCP competitor gap analysis requires network access.

Does the App Store index the description field for search?▼

No, Apple does not index descriptions for search. However, including keywords naturally in the description improves conversion rate when users see their search terms reflected, which indirectly boosts rankings.

How does keyword checking work for Arabic or Chinese metadata?▼

Arabic text is tokenized by whitespace with ال-prefix stripping to catch definite article duplicates. Chinese, Japanese, and Korean text is split by enumeration commas or per character since whitespace tokenization does not work for CJK scripts.

What happens if Astro MCP is not connected?▼

The audit skips the keyword gap analysis phase with a note to connect Astro MCP. All offline checks still run normally, so the audit remains useful without competitor keyword data.

Why are identical keywords across locales a problem?▼

Identical keyword fields across locales usually indicate the metadata was never localized for those markets. Keyword popularity varies dramatically by territory, so each locale needs market-specific keyword research rather than direct translation.