asc-aso-audit

Audit local App Store metadata for keyword gaps offline.

4|Updated Dec 8, 2019
One-click install
npx skills add https://github.com/Detrous/dotfiles --skill asc-aso-audit-detrous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-aso-audit
Source: https://github.com/Detrous/dotfiles/tree/main/claude/skills/asc-aso-audit
Command: npx skills add https://github.com/Detrous/dotfiles --skill asc-aso-audit-detrous

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Run an offline ASO audit on pulled App Store metadata to surface keyword gaps using local data and Astro MCP when available.

Core Features & Use Cases

  • Offline validation of metadata pulled via asc migrate export or asc localizations download
  • Keyword gap analysis planning with Astro MCP (when available)
  • Guidance for versioning and multi-locale readiness for ASO audits
  • Example: after exporting metadata, audit results highlight missing keywords and optimization opportunities.

Quick Start

Run asc-aso-audit against your latest local metadata exports to generate an offline ASO audit report.

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 ASO audit on local App Store metadata?

Perform an offline ASO audit by running asc-aso-audit against metadata pulled via asc migrate export or asc localizations download. It reads versioned JSON metadata at metadata/version/{latest-version}/{locale}.json to surface keyword gaps and optimization opportunities.

What is keyword gap analysis for App Store metadata?

Keyword gap analysis identifies missing search terms in your App Store metadata. This process performs offline validation on local JSON metadata and applies Astro MCP integration when available to surface keyword optimization opportunities.

Does the ASO audit work without an internet connection?

Yes, the ASO audit runs offline checks on local App Store metadata. Astro MCP integration is optional and used for keyword gap analysis planning when available, but the core validation operates offline using versioned JSON metadata.

How do I export App Store metadata for offline keyword gap analysis?

Export App Store metadata using asc migrate export or asc localizations download. This generates the versioned JSON metadata at metadata/version/{latest-version}/{locale}.json required by the offline ASO audit to surface keyword gaps.

Can I audit App Store localizations for multiple locales?

Yes, the ASO audit supports multi-locale readiness by reading versioned JSON metadata at metadata/version/{latest-version}/{locale}.json. It supports the primary locale en-US by default and can validate other localizations pulled via asc localizations download.