asc-aso-audit

Audit local App Store metadata to identify optimization gaps and keyword opportunities.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/pyronaur/ngents --skill asc-aso-audit-pyronaur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-aso-audit
Source: https://github.com/pyronaur/ngents/tree/main/docs/topics/apple/asc-cli/asc-aso-audit
Command: npx skills add https://github.com/pyronaur/ngents --skill asc-aso-audit-pyronaur

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill performs an offline ASO audit against local App Store metadata to identify optimization gaps and surface opportunities for improved discoverability.

Core Features & Use Cases

  • Offline checks against canonical metadata in ./metadata to validate structure, completeness, and consistency.
  • Astro MCP keyword gap analysis to surface missing keywords and cross-store opportunities (optional when Astro MCP access is available).
  • Use case: after pulling metadata with asc metadata pull, run this audit to prioritize keyword additions and metadata improvements for a new release.

Quick Start

Pull the app metadata locally with asc metadata pull and run the offline checks, followed by Astro MCP gap analysis when available.

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 gaps?

To audit App Store metadata for keyword gaps, run this Skill against your local metadata directory to validate structure and surface optimization opportunities using offline checks, with optional Astro MCP for deeper gap analysis.

What is an offline ASO audit and how does it work?

An offline ASO audit validates local App Store metadata for structure, completeness, and consistency without requiring live API access. It checks canonical metadata under the metadata/version path to identify discoverability gaps.

Do I need Astro MCP to run an ASO metadata audit?

No, Astro MCP is not required for an ASO metadata audit. Offline checks run by default against your local metadata directory, while Astro MCP is an optional integration for surfacing cross-store keyword opportunities.

How do I prepare local App Store metadata for an ASO audit?

Prepare local App Store metadata for an ASO audit by using the asc metadata pull command to populate the ./metadata directory with the latest version files, ensuring the audit has local data to validate.

What's the best way to surface missing keywords in App Store metadata?

The best way to surface missing keywords in App Store metadata is to run local offline checks for structural gaps, then leverage Astro MCP keyword gap analysis to identify missing terms and cross-store opportunities.

When should I run an ASO audit on local metadata?

Run an ASO audit on local metadata after pulling the latest App Store metadata with asc metadata pull, prioritizing keyword additions and metadata improvements before submitting a new release.