asc-aso-audit

Audit local App Store metadata offline to surface keyword gaps across locales.

103|6|Updated Aug 2, 2025
One-click install
npx skills add https://github.com/n0an/VivaDicta --skill asc-aso-audit-n0an
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-aso-audit
Source: https://github.com/n0an/VivaDicta/tree/main/.claude/skills/asc-aso-audit
Command: npx skills add https://github.com/n0an/VivaDicta --skill asc-aso-audit-n0an

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run offline ASO audits on local App Store metadata to surface keyword gaps using Astro MCP, reducing manual auditing time.

Core Features & Use Cases

  • Offline checks against canonical metadata stored locally.
  • Astro MCP-based gap analysis to identify missing keywords across locales.
  • Guidance for normalizing metadata before auditing and for applying findings.

Quick Start

Pull the latest canonical metadata into the metadata directory with asc metadata pull, then run asc-aso-audit to generate insights.

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?

Offline keyword gap analysis compares local App Store metadata against canonical records to identify missing terms across multiple locales, helping reduce manual auditing time by automating the gap detection process.

What is keyword gap analysis for localized App Store metadata?

Astro MCP connectivity is optional for gap analysis; the core offline checks run against local metadata directories, but connecting to Astro MCP enables cross-locale gap analysis to identify missing localized keywords.

How do I normalize local metadata before auditing App Store keywords?

To start the audit, pull the latest canonical metadata into the metadata directory using the appropriate command, then execute the audit tool to generate keyword gap insights across your local locales.

Do I need Astro MCP connectivity to run a local ASO audit?

Yes, the audit tool requires canonical metadata pulled into a local metadata directory with the latest version stored under metadata/version to function properly.