← ClaudeAtlas

kappmaker-asolisted

Research App Store keywords for a KAppMaker app via the Astro MCP and produce the keyword report — primary keywords, sub-niche clusters, and what was discarded and why. Use when the user asks about ASO, app store keywords, search ranking or which keywords to target. For writing the actual title, subtitle and keyword fields use kappmaker-aso-metadata.
KAppMaker/KAppMaker-CLI · ★ 3 · Data & Documents · score 64
Install: claude install-skill KAppMaker/KAppMaker-CLI
# KAppMaker — ASO Keyword Research ## Before starting **Read `AiGuidelines/` first** — the PRD and positioning already answer most questions. This is a skill-driven procedure: you (Claude) execute it with your own tools. No `kappmaker` binary is involved and none needs to be installed. ### ASO Keyword Research — Find high-value keywords via Astro MCP This is a **skill-driven procedure**, not an external CLI command. You (Claude) drive it using the [Astro MCP](https://tryastro.app/docs/mcp/) tools (real-time App Store search data, competitor keywords, popularity + difficulty scores) when they're available in the session, and write the curated keyword list to `AiGuidelines/keywords.md` for the user to review and feed into other ASO commands. Output of this workflow is the natural input to the **Localize ASO Metadata** workflow below — research first, then expand the chosen keywords across the 9 US-indexed locales with `mode=keyword-expansion`. **Trigger phrases**: - `Using kappmaker, research keywords for <base keyword>` - `Using kappmaker, find aso keywords [for/around/related to] <topic>` - `Using kappmaker, keyword research <base>` - "find keywords", "keyword research", "aso keyword discovery", "find sub-niche keywords" **Argument parsing**: - `base` / `base keyword` — required eventually, but can be derived if missing. Resolution order: 1. Explicit value in the user message (`base="ai image generator"` or in-line: "research keywords for AI image generator") 2. If