← Products

Mobile
⚙ Needs: the asc CLI (from the same author's repo) installed…

App Store ASO audit (offline checks + keyword gaps)

Two-phase ASO audit on pulled App Store metadata — offline checks (keyword waste, field utilization, separators, cross-locale gaps) plus competitor keyword-gap analysis

At a glance
What
Two-phase ASO audit on pulled App Store metadata — offline checks (keyword waste, field utilization, separators, cross-locale gaps) plus competitor keyword-gap analysis
Cost
Free
Needs
the asc CLI (from the same author's repo) installed and authenticated with App Store Connect — that needs an Apple Developer Program membership ($99/year); Astro MCP optional (needed only for the Phase 2 keyword-gap analysis)
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @rorkai
⌁

Install

Prerequisites: the asc CLI (from the same author's repo) installed and authenticated with App Store Connect — that needs an Apple Developer Program membership ($99/year); Astro MCP optional (needed only for the Phase 2 keyword-gap analysis) Install "App Store ASO audit (offline checks + keyword gaps)" for me. It gives the agent @rorkai's two-phase ASO audit: after pulling metadata with asc metadata pull, run offline checks (keyword waste, field utilization, separators, cross-locale gaps, description coverage) with script-aware tokenization, then optional per-store keyword-gap analysis via Astro MCP plus Apple-generated app-tag signals, reported as a single audit report. MIT-licensed. Repository: https://github.com/rorkai/app-store-connect-cli-skills/blob/main/skills/asc-aso-audit/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "asc-aso-audit". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install and authenticate the asc CLI, pull metadata with asc metadata pull before running the audit). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.