← Search

App Store ASO audit (offline checks + keyword gaps)
Mobile 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 9c7e769
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ 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:

Quick answer

App Store ASO audit is a free Muse skill and two-phase ASO audit on App Store metadata, run after asc metadata pull. Phase one runs checks on keyword waste, field utilization, separators and cross-locale gaps, and phase two adds keyword-gap analysis. Note that auditing your own app needs a paid Apple Developer Program membership for App Store Connect API access.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 9c7e769

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/rorkai/app-store-connect-cli-skills/9c7e769f09a18237c9bd9c70f70aef65f0cd0391/skills/asc-aso-audit/SKILL.md Pinned version: install the code at commit 9c7e769f09a18237c9bd9c70f70aef65f0cd0391 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 9c7e769 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
9c7e769 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.