asc-aso-audit

Audit local App Store metadata for keyword gaps using Astro MCP.

127|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill asc-aso-audit-hanamizuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-aso-audit
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/ios-dev/skills/asc-aso-audit
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill asc-aso-audit-hanamizuki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Offline ASO auditing on local App Store metadata to identify keyword gaps and optimization opportunities.

Core Features & Use Cases

  • Offline checks against the latest version of local metadata for consistency and gaps.
  • Astro MCP-based keyword gap analysis to surface high-impact keywords.
  • Localized workflows supporting en-US by default and other locales.

Quick Start

Run this skill after pulling metadata with asc metadata pull to perform a two-phase ASO audit and surface keyword gaps.

Frequently Asked Questions about asc-aso-audit

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

FAQPage Schema
How do I perform an offline ASO audit on local App Store metadata?

To perform an offline ASO audit, run this skill after pulling metadata with asc metadata pull. It checks your local App Store metadata stored under ./metadata/version/{latest-version} to identify optimization opportunities and keyword gaps.

How does keyword gap analysis work with Astro MCP?

Keyword gap analysis with Astro MCP surfaces high-impact keywords by comparing your local App Store metadata against tracked data. You need an optional Astro MCP track configured to enable this gap analysis during the offline audit.

Can I audit App Store metadata for locales other than en-US?

Yes, you can audit App Store metadata for locales other than en-US. The localized workflow supports en-US by default and processes locale-specific files organized within your canonical local metadata directory structure.

What is the required directory structure for local App Store metadata?

The required directory structure for local App Store metadata is ./metadata/version/{latest-version}. You must organize your pulled metadata in this canonical format before running the offline ASO audit and keyword gap analysis.

What is the difference between offline ASO auditing and live App Store analysis?

Offline ASO auditing checks local metadata files directly without connecting to live App Store data, ensuring consistency and identifying gaps. It relies on pulled metadata and an optional Astro MCP track rather than querying live platform APIs.

Are there limitations to offline App Store metadata audits?

A limitation of offline App Store metadata audits is the requirement for local metadata in a canonical format under ./metadata/version/{latest-version}. Additionally, keyword gap analysis only functions if you provide an optional Astro MCP track.