asc-aso-audit

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

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/barronlroth/Cubby --skill asc-aso-audit-barronlroth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-aso-audit
Source: https://github.com/barronlroth/Cubby/tree/main/.agents/skills/asc-aso-audit
Command: npx skills add https://github.com/barronlroth/Cubby --skill asc-aso-audit-barronlroth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams audit their canonical App Store metadata offline, identifying keyword gaps and optimization opportunities without requiring live store data. It surfaces actionable insights to improve discoverability by analyzing local metadata and comparing against Astro MCP recommendations when available.

Core Features & Use Cases

  • Offline ASO checks against local metadata in ./metadata, including app-info and version data across locales.
  • Keyword gap analysis via Astro MCP when connected, to uncover opportunities not present in local metadata.
  • Guidance and references to maintain best-practice ASO rules (see references/aso_rules.md) and to identify the latest version assets.
  • Use Case: After pulling metadata with asc metadata pull, run this skill to validate keyword coverage and locate gaps for optimization.

Quick Start

After pulling canonical metadata with asc metadata pull, run the audit with asc-aso-audit to 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 run an offline App Store metadata audit to find keyword gaps?

To run an offline App Store metadata audit, pull canonical data into a local directory and execute an audit skill to surface keyword gaps and optimization opportunities without live store data.

What is ASO keyword gap analysis and when do I need it?

ASO keyword gap analysis identifies search terms missing from your local App Store metadata but recommended by market insights, helping improve app discoverability when updating store listings.

How do I audit App Store metadata locally without connecting to the live store?

You audit App Store metadata locally by analyzing the app-info and version files stored in your metadata directory, applying best-practice ASO rules to validate keyword coverage offline.

Does this offline ASO audit require a specific metadata format or pull command?

Yes, this offline ASO audit requires a recent metadata pull to populate the local directory with canonical app-info and version data across locales before analysis can begin.

Can I use Astro MCP for market-specific keyword insights during an offline ASO audit?

Yes, you can optionally leverage Astro MCP during an offline ASO audit to generate market-specific keyword insights and compare them against your local metadata for gap analysis.

What are the limitations of auditing App Store metadata offline instead of live?

Auditing App Store metadata offline relies on previously pulled local data and optional Astro MCP insights, meaning it cannot reflect real-time store ranking changes or live competitor updates.