[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E9NRM58SMNPHE6YAJSNA8R":3,"skill-same:01M7E9NRM58SMNPHE6YAJSNA8R":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7E9NRM58SMNPHE6YAJSNA8R","asc-aso-audit",null,"Run an offline ASO audit on canonical App Store metadata under `.\u002Fmetadata` and surface keyword gaps using Astro MCP. Use after pulling metadata with `asc metadata pull`.","buidangminh23\u002Fdesign-pro-max","buidangminh23","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F256920857?v=4","01M7E9N0JXRWQ1EGSBXP2BE8JR","Minh Spark","01M7E9N0KJ3A6E4RWZ45SNVQJH",5,"MIT","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fapp-store-connect\u002Fasc-aso-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fapp-store-connect\u002Fasc-aso-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: asc-aso-audit\ndescription: Run an offline ASO audit on canonical App Store metadata under `.\u002Fmetadata` and surface keyword gaps using Astro MCP. Use after pulling metadata with `asc metadata pull`.\n---\n\n# asc ASO audit\n\nRun a two-phase ASO audit: offline checks against local metadata files, then keyword gap analysis via Astro MCP.\nWhen available, include Apple-generated app tags as a discoverability signal.\n\n## Preconditions\n\n- Metadata pulled locally into canonical files via `asc metadata pull --app \"APP_ID\" --version \"1.2.3\" --dir \".\u002Fmetadata\"`.\n- If metadata came from `asc migrate export` or `asc localizations download`, normalize it into the canonical `.\u002Fmetadata` layout before running this skill.\n- For Astro gap analysis: app tracked in Astro MCP (optional — offline checks run without it).\n- For Apple-generated discoverability tags: `asc app-tags list --app \"APP_ID\" --output json` works when the API returns tags for the app.\n\n## Before You Start\n\n1. Read `references\u002Faso_rules.md` to understand the rules each check enforces.\n2. Identify the **latest version directory** under `metadata\u002Fversion\u002F` (highest semantic version number). Use this for all version-level fields.\n3. The **primary locale** is `en-US` unless the user specifies otherwise.\n\n## Metadata File Paths\n\n- **App-info fields** (`subtitle`): `metadata\u002Fapp-info\u002F{locale}.json`\n- **Version fields** (`keywords`, `description`, `whatsNew`): `metadata\u002Fversion\u002F{latest-version}\u002F{locale}.json`\n- **App name**: May not be present in exported metadata. If `name` is missing from the app-info JSON, fetch it via `asc apps info list` or ask the user. Do not flag it as a missing-field error.\n\n## Phase 1: Offline Checks\n\nRun these 5 checks against the local metadata directory. No network calls required.\n\n### 1. Keyword Waste\n\nTokenize the `subtitle` field (and `name` if available). Flag any token that also appears in the `keywords` field — it is already indexed and wastes keyword budget.\n\n```\nSeverity: ⚠️ Warning\nExample:  \"quran\" appears in subtitle AND keywords — remove from keywords to free 6 characters\n```\n\nHow to check:\n1. Read `metadata\u002Fapp-info\u002F{locale}.json` for `subtitle` (and `name` if present)\n2. Read `metadata\u002Fversion\u002F{latest-version}\u002F{locale}.json` for `keywords`\n3. Tokenize subtitle (+ name):\n   - **Latin\u002FCyrillic scripts:** split by whitespace, strip leading\u002Ftrailing punctuation, lowercase\n   - **Chinese\u002FJapanese\u002FKorean:** split by `、` `，` `,` or iterate characters — each character or character-group is a token. Whitespace tokenization does not work for CJK.\n   - **Arabic:** split by whitespace, then also generate prefix-stripped variants (remove ال prefix) since Apple likely normalizes definite articles. For example, \"القرآن\" in subtitle should flag both \"القرآن\" and \"قرآن\" in keywords.\n4. Split keywords by comma, trim whitespace, lowercase\n5. Report intersection (including fuzzy matches from prefix stripping)\n\n### Optional: App Tag Alignment\n\nApp tags are Apple-generated labels that can appear in search results and product pages. They are not editable ASO metadata, but they are useful evidence for whether Apple's classification matches the intended positioning.\n\n```bash\nasc app-tags list --app \"APP_ID\" --output json\nasc app-tags view --app \"APP_ID\" --id \"TAG_ID\" --output json\n```\n\nUse tags as context only:\n- If visible tags reinforce the subtitle\u002Fkeyword strategy, note the alignment.\n- If tags point to an unintended category or use case, recommend metadata\u002Fcategory changes that may improve future classification.\n- Do not promise that changing metadata will immediately change Apple-generated tags.\n\n### Optional: Official Apple Search Plan\n\nWhen both App Store Connect and Apple Ads credentials are configured, use the\nexperimental, read-only plan to join the selected metadata with official paid\nsearch evidence:\n\n```bash\nasc optimize search plan \\\n  --app \"APP_ID\" \\\n  --version \"1.2.3\" \\\n  --ad-account \"AD_ACCOUNT_ID\" \\\n  --country \"US\" \\\n  --genre \"PRODUCTIVITY_UTILITIES\" \\\n  --locale \"en-US\" \\\n  --out-dir \".asc\u002Foptimization\u002F1.2.3\" \\\n  --output markdown\n```\n\n- Authenticate App Store Connect with `asc auth` and Apple Ads separately with\n  `asc ads auth login`; the two credential sets are independent.\n- Treat the generated CSV and JSON files as review artifacts. The command does\n  not apply metadata, exact keywords, or negative keywords, and partial Apple\n  Ads source failures stay visible in the report.\n- Keep Apple's popularity, app-specific paid reach, paid search outcomes, and\n  metadata coverage distinct. Do not infer organic rank or keyword difficulty\n  from this plan.\n\n### 2. Underutilized Fields\n\nFlag fields using less than their recommended minimum:\n\n| Field | Minimum | Limit | Rationale |\n|-------|---------|-------|-----------|\n| Keywords | 90 chars | 100 | 90%+ usage maximizes indexing |\n| Subtitle | 20 chars | 30 | 65%+ usage recommended |\n\n```\nSeverity: ⚠️ Warning\nExample:  keywords is 62\u002F100 characters (62%) — 38 characters of indexing opportunity unused\n```\n\n### 3. Missing Fields\n\nFlag empty or missing required fields: `subtitle`, `keywords`, `description`, `whatsNew`.\n\nNote: `name` may not be in the export — only flag it if the app-info JSON explicitly contains a `name` key with an empty value.\n\n```\nSeverity: ❌ Error\nExample:  subtitle is empty for locale en-US\n```\n\n### 4. Bad Keyword Separators\n\nCheck the `keywords` field for formatting issues:\n- Spaces after commas (`quran, recitation`)\n- Semicolons instead of commas (`quran;recitation`)\n- Pipes instead of commas (`quran|recitation`)\n\n```\nSeverity: ❌ Error\nExample:  keywords contain spaces after commas — wastes 3 characters\n```\n\n### 5. Cross-Locale Keyword Gaps\n\nCompare `keywords` fields across all available locales. Flag locales where keywords are identical to the primary locale (`en-US` by default) — this usually means they were not localized.\n\n```\nSeverity: ⚠️ Warning\nExample:  ar keywords identical to en-US — likely not localized for Arabic market\n```\n\nHow to check:\n1. Load keywords for all locales\n2. Compare each non-primary locale against the primary\n3. Flag exact matches (case-insensitive)\n\n### 6. Description Keyword Coverage\n\nCheck whether keywords appear naturally in the `description` field. While Apple does **not** index descriptions for search, users who see their search terms reflected in the description are more likely to download — this improves conversion rate, which indirectly boosts rankings.\n\n```\nSeverity: 💡 Info\nExample:  3 of 16 keywords not found in description: namaz, tarteel, adhan\n```\n\nHow to check:\n1. Load `keywords` and `description` for each locale\n2. For each keyword, check if it appears as a substring in the description (case-insensitive)\n3. Account for inflected forms: Arabic root matches, verb conjugations (e.g., \"memorizar\" ≈ \"memorices\"), and case declensions (e.g., Russian \"сура\" ≈ \"суры\")\n4. Report missing keywords per locale — recommend weaving them naturally into existing sentences\n5. Do NOT flag: Latin-script keywords in non-Latin descriptions (e.g., \"quran\" in Cyrillic text) — these target separate search paths\n\n## Phase 2: Astro MCP Keyword Gap Analysis\n\nIf Astro MCP is available and the app is tracked, run keyword gap analysis. **Run this per store\u002Flocale, not just for the US store** — keyword popularity varies dramatically across markets.\n\n### Steps\n\n1. **Get current keywords**: Call `get_app_keywords` with the app ID to retrieve tracked keywords and their current rankings.\n\n2. **Check multi-store tracking**: Query existing tracking for each locale's App Store territory. Report untracked stores as unavailable and continue the audit. Use `add_keywords` only when the user separately authorizes tracking setup; empty rankings for an untracked store do not prove poor performance.\n\n3. **Extract competitor keywords**: Call `extract_competitors_keywords` with 3-5 top competitor app IDs to find keyword gaps. This is the highest-value Astro tool — it reveals keywords competitors rank for that you don't. Run this per store when possible.\n\n4. **Get suggestions**: Call `get_keyword_suggestions` with the app ID for additional recommendations based on category analysis.\n\n5. **Check current rankings**: Call `search_rankings` to see where the app currently ranks for tracked keywords in each store.\n\n6. **Diff against metadata**: Compare suggested and competitor keywords against the tokens present in `subtitle`, `name` (if available), and `keywords` fields from the local metadata.\n\n7. **Surface gaps**: Report all gaps ranked by popularity score (highest first). Include the source (competitor analysis vs. suggestion).\n\n### Cross-Field Combo Strategy\n\nWhen recommending keyword additions, consider how single words combine across indexed fields (title + subtitle + keywords). For example:\n- Adding \"namaz\" to keywords when \"vakti\" is already present enables matching the search \"namaz vakti\" (66 popularity)\n- Adding \"holy\" to keywords when \"Quran\" is in the subtitle enables matching \"holy quran\" (58 popularity)\n\nFlag high-value combos in recommendations.\n\n### Skip Conditions\n\n- Astro MCP not connected → skip with note: \"Connect Astro MCP for keyword gap analysis\"\n- App not tracked in Astro → skip with note: \"Add app to Astro with `mcp__astro__add_app` for gap analysis\"\n- Store not tracked for a locale → report the gap and skip its rankings; tracking setup requires separate authorization\n\n## Output Format\n\nPresent results as a single audit report. The report covers only the latest version directory.\n\n```\n### ASO Audit Report\n\n**App:** [name] | **Primary Locale:** [locale]\n**Metadata source:** [path including version number]\n\n#### Field Utilization\n\n| Field | Value | Length | Limit | Usage |\n|-------|-------|--------|-------|-------|\n| Name | ... | X | 30 | X% |\n| Subtitle | ... | X | 30 | X% |\n| Keywords | ... | X | 100 | X% |\n| Promotional Text | ... | X | 170 | X% |\n| Description | (first 50 chars)... | X | 4000 | X% |\n\n#### Offline Checks\n\n| # | Check | Severity | Field | Locale | Detail |\n|---|-------|----------|-------|--------|--------|\n| 1 | Keyword waste | ⚠️ | keywords | en-US | \"quran\" duplicated in subtitle |\n\n**Summary:** X errors, Y warnings across Z locales\n\n#### Keyword Gap Analysis (Astro MCP)\n\n| Keyword | Popularity | In Metadata? | Suggested Action |\n|---------|-----------|--------------|-----------------|\n| quran recitation | 72 | ❌ | Add to keywords |\n\n#### Recommendations\n\n1. [Highest priority action — errors first]\n2. [Next priority — keyword waste]\n3. [Utilization improvements]\n4. [Keyword gap opportunities]\n```\n\n## Notes\n\n- Offline checks work without any network access — they read local files only.\n- Astro gap analysis is additive — the audit is useful even without it.\n- Run this skill after `asc metadata pull` to ensure canonical metadata files are current.\n- For keyword-only follow-up after the audit, prefer the canonical keyword workflow:\n  - `asc metadata keywords diff --app \"APP_ID\" --version \"1.2.3\" --dir \".\u002Fmetadata\"`\n  - `asc metadata keywords apply --app \"APP_ID\" --version \"1.2.3\" --dir \".\u002Fmetadata\" --confirm`\n  - `asc metadata keywords sync --app \"APP_ID\" --version \"1.2.3\" --dir \".\u002Fmetadata\" --input \".\u002Fkeywords.csv\"` when importing external keyword research\n- After making changes, re-run the audit to verify fixes.\n- The Field Utilization table includes promotional text for completeness, but no check validates its content (it is not indexed by Apple).\n","# asc ASO audit\n\nRun a two-phase ASO audit: offline checks against local metadata files, then keyword gap analysis via Astro MCP.\nWhen available, include Apple-generated app tags as a discoverability signal.\n\n## Preconditions\n\n- Metadata pulled locally into canonical files via `asc metadata pull --app \"APP_ID\" --version \"1.2.3\" --dir \".\u002Fmetadata\"`.\n- If metadata came from `asc migrate export` or `asc localizations download`, normalize it into the canonical `.\u002Fmetadata` layout before running this skill.\n- For Astro gap analysis: app tracked in Astro MCP (optional — offline checks run without it).\n- For Apple-generated discoverability tags: `asc app-tags list --app \"APP_ID\" --output json` works when the API returns tags for the app.\n\n## Before You Start\n\n1. Read `references\u002Faso_rules.md` to understand the rules each check enforces.\n2. Identify the **latest version directory** under `metadata\u002Fversion\u002F` (highest semantic version number). Use this for all version-level fields.\n3. The **primary locale** is `en-US` unless the user specifies otherwise.\n\n## Metadata File Paths\n\n- **App-info fields** (`subtitle`): `metadata\u002Fapp-info\u002F{locale}.json`\n- **Version fields** (`keywords`, `description`, `whatsNew`): `metadata\u002Fversion\u002F{latest-version}\u002F{locale}.json`\n- **App name**: May not be present in exported metadata. If `name` is missing from the app-info JSON, fetch it via `asc apps info list` or ask the user. Do not flag it as a missing-field error.\n\n## Phase 1: Offline Checks\n\nRun these 5 checks against the local metadata directory. No network calls required.\n\n### 1. Keyword Waste\n\nTokenize the `subtitle` field (and `name` if available). Flag any token that also appears in the `keywords` field — it is already indexed and wastes keyword budget.\n\n```\nSeverity: ⚠️ Warning\nExample:  \"quran\" appears in subtitle AND keywords — remove from keywords to free 6 characters\n```\n\nHow to check:\n1. Read `metadata\u002Fapp-info\u002F{locale}.json` for `subtitle` (and `name` if present)\n2. Read `metadata\u002Fversion\u002F{latest-version}\u002F{locale}.json` for `keywords`\n3. Tokenize subtitle (+ name):\n   - **Latin\u002FCyrillic scripts:** split by whitespace, strip leading\u002Ftrailing punctuation, lowercase\n   - **Chinese\u002FJapanese\u002FKorean:** split by `、` `，` `,` or iterate characters — each character or character-group is a token. Whitespace tokenization does not work for CJK.\n   - **Arabic:** split by whitespace, then also generate prefix-stripped variants (remove ال prefix) since Apple likely normalizes definite articles. For example, \"القرآن\" in subtitle should flag both \"القرآن\" and \"قرآن\" in keywords.\n4. Split keywords by comma, trim whitespace, lowercase\n5. Report intersection (including fuzzy matches from prefix stripping)\n\n### Optional: App Tag Alignment\n\nApp tags are Apple-generated labels that can appear in search results and product pages. They are not editable ASO metadata, but they are useful evidence for whether Apple's classification matches the intended positioning.\n\n```bash\nasc app-tags list --app \"APP_ID\" --output json\nasc app-tags view --app \"APP_ID\" --id \"TAG_ID\" --output json\n```\n\nUse tags as context only:\n- If visible tags reinforce the subtitle\u002Fkeyword strategy, note the alignment.\n- If tags point to an unintended category or use case, recommend metadata\u002Fcategory changes that may improve future classification.\n- Do not promise that changing metadata will immediately change Apple-generated tags.\n\n### Optional: Official Apple Search Plan\n\nWhen both App Store Connect and Apple Ads credentials are configured, use the\nexperimental, read-only plan to join the selected metadata with official paid\nsearch evidence:\n\n```bash\nasc optimize search plan \\\n  --app \"APP_ID\" \\\n  --version \"1.2.3\" \\\n  --ad-account \"AD_ACCOUNT_ID\" \\\n  --country \"US\" \\\n  --genre \"PRODUCTIVITY_UTILITIES\" \\\n  --locale \"en-US\" \\\n  --out-dir \".asc\u002Foptimization\u002F1.2.3\" \\\n  --output markdown\n```\n\n- Authenticate App Store Connect with `asc auth` and Apple Ads separately with\n  `asc ads auth login`; the two credential sets are independent.\n- Treat the generated CSV and JSON files as review artifacts. The command does\n  not apply metadata, exact keywords, or negative keywords, and partial Apple\n  Ads source failures stay visible in the report.\n- Keep Apple's popularity, app-specific paid reach, paid search outcomes, and\n  metadata coverage distinct. Do not infer organic rank or keyword difficulty\n  from this plan.\n\n### 2. Underutilized Fields\n\nFlag fields using less than their recommended minimum:\n\n| Field | Minimum | Limit | Rationale |\n|-------|---------|-------|-----------|\n| Keywords | 90 chars | 100 | 90%+ usage maximizes indexing |\n| Subtitle | 20 chars | 30 | 65%+ usage recommended |\n\n```\nSeverity: ⚠️ Warning\nExample:  keywords is 62\u002F100 characters (62%) — 38 characters of indexing opportunity unused\n```\n\n### 3. Missing Fields\n\nFlag empty or missing required fields: `subtitle`, `keywords`, `description`, `whatsNew`.\n\nNote: `name` may not be in the export — only flag it if the app-info JSON explicitly contains a `name` key with an empty value.\n\n```\nSeverity: ❌ Error\nExample:  subtitle is empty for locale en-US\n```\n\n### 4. Bad Keyword Separators\n\nCheck the `keywords` field for formatting issues:\n- Spaces after commas (`quran, recitation`)\n- Semicolons instead of commas (`quran;recitation`)\n- Pipes instead of commas (`quran|recitation`)\n\n```\nSeverity: ❌ Error\nExample:  keywords contain spaces after commas — wastes 3 characters\n```\n\n### 5. Cross-Locale Keyword Gaps\n\nCompare `keywords` fields across all available locales. Flag locales where keywords are identical to the primary locale (`en-US` by default) — this usually means they were not localized.\n\n```\nSeverity: ⚠️ Warning\nExample:  ar keywords identical to en-US — likely not localized for Arabic market\n```\n\nHow to check:\n1. Load keywords for all locales\n2. Compare each non-primary locale against the primary\n3. Flag exact matches (case-insensitive)\n\n### 6. Description Keyword Coverage\n\nCheck whether keywords appear naturally in the `description` field. While Apple does **not** index descriptions for search, users who see their search terms reflected in the description are more likely to download — this improves conversion rate, which indirectly boosts rankings.\n\n```\nSeverity: 💡 Info\nExample:  3 of 16 keywords not found in description: namaz, tarteel, adhan\n```\n\nHow to check:\n1. Load `keywords` and `description` for each locale\n2. For each keyword, check if it appears as a substring in the description (case-insensitive)\n3. Account for inflected forms: Arabic root matches, verb conjugations (e.g., \"memorizar\" ≈ \"memorices\"), and case declensions (e.g., Russian \"сура\" ≈ \"суры\")\n4. Report missing keywords per locale — recommend weaving them naturally into existing sentences\n5. Do NOT flag: Latin-script keywords in non-Latin descriptions (e.g., \"quran\" in Cyrillic text) — these target separate search paths\n\n## Phase 2: Astro MCP Keyword Gap Analysis\n\nIf Astro MCP is available and the app is tracked, run keyword gap analysis. **Run this per store\u002Flocale, not just for the US store** — keyword popularity varies dramatically across markets.\n\n### Steps\n\n1. **Get current keywords**: Call `get_app_keywords` with the app ID to retrieve tracked keywords and their current rankings.\n\n2. **Check multi-store tracking**: Query existing tracking for each locale's App Store territory. Report untracked stores as unavailable and continue the audit. Use `add_keywords` only when the user separately authorizes tracking setup; empty rankings for an untracked store do not prove poor performance.\n\n3. **Extract competitor keywords**: Call `extract_competitors_keywords` with 3-5 top competitor app IDs to find keyword gaps. This is the highest-value Astro tool — it reveals keywords competitors rank for that you don't. Run this per store when possible.\n\n4. **Get suggestions**: Call `get_keyword_suggestions` with the app ID for additional recommendations based on category analysis.\n\n5. **Check current rankings**: Call `search_rankings` to see where the app currently ranks for tracked keywords in each store.\n\n6. **Diff against metadata**: Compare suggested and competitor keywords against the tokens present in `subtitle`, `name` (if available), and `keywords` fields from the local metadata.\n\n7. **Surface gaps**: Report all gaps ranked by popularity score (highest first). Include the source (competitor analysis vs. suggestion).\n\n### Cross-Field Combo Strategy\n\nWhen recommending keyword additions, consider how single words combine across indexed fields (title + subtitle + keywords). For example:\n- Adding \"namaz\" to keywords when \"vakti\" is already present enables matching the search \"namaz vakti\" (66 popularity)\n- Adding \"holy\" to keywords when \"Quran\" is in the subtitle enables matching \"holy quran\" (58 popularity)\n\nFlag high-value combos in recommendations.\n\n### Skip Conditions\n\n- Astro MCP not connected → skip with note: \"Connect Astro MCP for keyword gap analysis\"\n- App not tracked in Astro → skip with note: \"Add app to Astro with `mcp__astro__add_app` for gap analysis\"\n- Store not tracked for a locale → report the gap and skip its rankings; tracking setup requires separate authorization\n\n## Output Format\n\nPresent results as a single audit report. The report covers only the latest version directory.\n\n```\n### ASO Audit Report\n\n**App:** [name] | **Primary Locale:** [locale]\n**Metadata source:** [path including version number]\n\n#### Field Utilization\n\n| Field | Value | Length | Limit | Usage |\n|-------|-------|--------|-------|-------|\n| Name | ... | X | 30 | X% |\n| Subtitle | ... | X | 30 | X% |\n| Keywords | ... | X | 100 | X% |\n| Promotional Text | ... | X | 170 | X% |\n| Description | (first 50 chars)... | X | 4000 | X% |\n\n#### Offline Checks\n\n| # | Check | Severity | Field | Locale | Detail |\n|---|-------|----------|-------|--------|--------|\n| 1 | Keyword waste | ⚠️ | keywords | en-US | \"quran\" duplicated in subtitle |\n\n**Summary:** X errors, Y warnings across Z locales\n\n#### Keyword Gap Analysis (Astro MCP)\n\n| Keyword | Popularity | In Metadata? | Suggested Action |\n|---------|-----------|--------------|-----------------|\n| quran recitation | 72 | ❌ | Add to keywords |\n\n#### Recommendations\n\n1. [Highest priority action — errors first]\n2. [Next priority — keyword waste]\n3. [Utilization improvements]\n4. [Keyword gap opportunities]\n```\n\n## Notes\n\n- Offline checks work without any network access — they read local files only.\n- Astro gap analysis is additive — the audit is useful even without it.\n- Run this skill after `asc metadata pull` to ensure canonical metadata files are current.\n- For keyword-only follow-up after the audit, prefer the canonical keyword workflow:\n  - `asc metadata keywords diff --app \"APP_ID\" --version \"1.2.3\" --dir \".\u002Fmetadata\"`\n  - `asc metadata keywords apply --app \"APP_ID\" --version \"1.2.3\" --dir \".\u002Fmetadata\" --confirm`\n  - `asc metadata keywords sync --app \"APP_ID\" --version \"1.2.3\" --dir \".\u002Fmetadata\" --input \".\u002Fkeywords.csv\"` when importing external keyword research\n- After making changes, re-run the audit to verify fixes.\n- The Field Utilization table includes promotional text for completeness, but no check validates its content (it is not indexed by Apple).\n",{"name":5,"description":7},"main","c24f526343de0e3daddc559ae8c8061c7bee9168","skills\u002Fapple\u002F.vendor\u002Fapp-store-connect\u002Fasc-aso-audit",0,"https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max","https:\u002F\u002Fgithub.com\u002Fbuidangminh23","https:\u002F\u002Fminhspark.com","2026-11-13 18:28:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add buidangminh23\u002Fdesign-pro-max --skill asc-aso-audit",{"tool":39,"command":40},"bunx","bunx skills add buidangminh23\u002Fdesign-pro-max --skill asc-aso-audit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add buidangminh23\u002Fdesign-pro-max --skill asc-aso-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fapp-store-connect\u002Fasc-aso-audit\u002FSKILL.md",true,[47,51,57],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":16},"LICENSE","许可证",1070,{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Faso_rules.md","REFERENCE","参考文档",4068,"https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fapp-store-connect\u002Fasc-aso-audit\u002Freferences\u002Faso_rules.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"UPSTREAM.json",1539,"https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fapp-store-connect\u002Fasc-aso-audit\u002FUPSTREAM.json",[62,70,78,85,93,101],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":20},"01M7E9TYRPZ0JSFX8S1PS0M33C","icons-pro-max","A portable icon catalog and rendering guide for the current project: payment methods, QR codes, social\u002Fapp brand marks, download badges, the lucide-react UI icon set, 145 tech-stack logos, 86 full-color AI provider marks, 516 Claude connector icons, and 25 Microsoft app logos. Gives the exact asset path, React component, canonical size, brand color, render recipe, and accessibility rule for each icon — plus an anti-slop checklist so an agent never redraws a logo, recolors a brand mark, distorts an aspect ratio, or re-inlines a duplicated icon. Use whenever adding, rendering, swapping, or auditing an icon anywhere in a website, app, or document.","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Ficons-pro-max\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Ficons-pro-max\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":20},"01M7E9TN6D8X0EMC5JK28WDKMY","design-spacing-rhythm","The most complete spacing & alignment skill for AI-generated UI and written documents. Reads the layout, sets three dials (SPACING_STEP \u002F DENSITY \u002F ALIGNMENT_RIGOR), derives ONE scale, and lets proximity carry meaning — establishing a spacing scale, vertical rhythm, optical alignment, whitespace hierarchy, responsive\u002Ffluid density, accessibility floors, component recipes, document & long-form (Word \u002F Docs \u002F PDF \u002F Markdown) spacing, and an anti-slop checklist. Every rule is CONTEXTUAL: read the situation, then pull only what fits. Not a blanket \"add more padding\" pass.","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-spacing-rhythm\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-spacing-rhythm\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7E9TFK8SVDBE8B91XG8WW8A","apple","For Apple app UI and code (SwiftUI, Xcode, HIG) and scroll scenes. Use when a question or task needs HIG reviews, App Store Connect (app records, TestFlight, signing, notarizing, ad hoc, What's New, ASO, Apple Ads, Wall of Apps, screenshots), SwiftData, Swift 6, Swift Testing, Core Data, Xcode builds, disk space, Tuist apps or pinned or scrubbed web sections. Not for launch\u002Fpreview videos, captioned screenshots, Play Store art, GSAP, web springs (apple-design) or Swift questions (write-swift).","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7E9T9G0A9FS85F09P6CQBG2","xcode-disk-cleanup","Audit and safely clean Xcode-related developer storage on macOS. Use whenever a developer mentions low disk space, Xcode storage, DerivedData, simulator devices or runtimes, stale beta platforms in Xcode Settings, DeviceSupport, archives, dSYMs, CocoaPods caches, simulator dyld caches, project .build folders, downloaded Xcode DMGs\u002FXIPs, duplicate Xcode installers, or old Xcode applications. Also use this skill proactively when you hit low storage during other work, such as a build, download, or install failing with an out-of-disk-space error. Always measure first, report recoverable GiB with evidence, and obtain explicit itemized approval before any mutation.","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fxcode-disk-cleanup\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fxcode-disk-cleanup\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M7E9T5BN7V6BZE4QKVCCJXKK","xcode-project-analyzer","Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fxcode-build\u002Fxcode-project-analyzer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fxcode-build\u002Fxcode-project-analyzer\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7E9T17K73CZFF5ZJ3B8VT79","xcode-compilation-analyzer","Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fxcode-build\u002Fxcode-compilation-analyzer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbuidangminh23\u002Fdesign-pro-max\u002Fblob\u002Fmain\u002Fskills\u002Fapple\u002F.vendor\u002Fxcode-build\u002Fxcode-compilation-analyzer\u002FSKILL.md",[],[]]