asc-aso-audit

Audit App Store metadata exports for keyword waste and localization issues.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill asc-aso-audit-curtislmartin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-aso-audit
Source: https://github.com/curtislmartin/daily-ascent-engineering/tree/main/skills_repo/asc-aso-audit
Command: npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill asc-aso-audit-curtislmartin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identifies App Store metadata issues and missed keyword opportunities across locales so teams can fix wasted keyword budget, missing or malformed fields, and localization gaps before submitting updates.

Core Features & Use Cases

  • Offline checks for keyword waste, underutilized fields, missing required fields, bad keyword separators, cross-locale keyword gaps, and description keyword coverage using only exported metadata files.
  • Locale-aware tokenization and script rules (CJK tokenization, Arabic ال-prefix handling, Cyrillic/Latin considerations) to avoid false negatives and ensure accurate keyword matching.
  • Astro MCP integration (optional) to run per-store keyword gap analysis, extract competitor keywords, get popularity-backed suggestions, and diff results against local metadata to surface high-value additions.
  • Use case: After running asc migrate export, produce a single ASO Audit Report for the latest version directory with actionable fixes and prioritized keyword recommendations.

Quick Start

Run the asc-aso-audit skill on your exported metadata directory to generate the ASO audit report and optionally perform Astro MCP keyword gap analysis.

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 metadata for keyword waste and localization issues?

App Store metadata audits detect keyword waste, missing fields, and cross-locale localization gaps by parsing exported metadata files with locale-aware tokenization to compute utilization metrics and flag malformed fields.

What is ASO keyword gap analysis and how does it find missed opportunities?

ASO keyword gap analysis extracts competitor keywords and popularity-backed suggestions via Astro MCP endpoints, then diffs results against local metadata exports to surface high-value keyword additions per store and locale.

How do I handle CJK tokenization and Arabic prefixes when auditing ASO keywords?

Locale-aware tokenization applies script-specific rules like CJK tokenization and Arabic ال-prefix handling during metadata audits to avoid false negatives and ensure accurate keyword matching across Cyrillic and Latin scripts.

Can I run an offline ASO audit without connecting to external services?

Offline ASO audits check keyword waste, underutilized fields, bad keyword separators, and description keyword coverage using only local metadata exports, requiring no external API connections to generate actionable fix reports.

Do I need Astro MCP integration to perform App Store competitor keyword analysis?

Astro MCP integration is optional for App Store competitor keyword analysis; connecting to Astro MCP endpoints enables popularity-backed ranking suggestions and per-store keyword gap extraction beyond offline metadata checks.

What is the best way to fix wasted keyword budget before an App Store submission?

Fixing wasted keyword budget involves running offline checks on exported metadata directories to identify underutilized fields and malformed separators, producing a prioritized ASO audit report with actionable keyword recommendations.