AppKittieAppKittie/aso-mcp-skills/SKILL.md

appkittie

Skill8 starsChanged 15 days agoMITView on GitHub

Use when the user wants mobile app intelligence for the Apple App Store or Google Play with AppKittie, including app discovery, ASO keyword research, metadata optimization, competitor analysis, growth, revenue, ad intelligence, review analysis, or shared marketing context. Use AppKittie MCP tools or the REST API for live data when available.

In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ad-intelligenceSkill
- app-discoverySkill
- app-marketing-contextSkill
- competitor-analysisSkill
- creator-discoverySkill
- growth-analysisSkill
- keyword-researchSkill
- metadata-optimizationSkill
- onboarding-analysisSkill
- revenue-analysisSkill
- review-analysisSkill

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Use this skill as the AppKittie entry point for mobile app store research.
line 8
Distinctive:
Read only the focused workflow that matches the user's intent:
line 12
Distinctive:
Prefer live AppKittie data.
line 31
Very specific:
If MCP tools are unavailable, use the REST API at https://appkittie.com/api/v1 when the user has provided an AppKittie API key.
line 48
Distinctive:
If no live data access is available, explain what needs to be connected before making data-backed claims.
line 50
Distinctive:
Treat downloads, revenue, growth, ads, and keyword metrics as estimates or signals unless AppKittie says otherwise.
line 56
Distinctive:
When one workflow naturally leads to another, say so and load the next focused workflow only if needed.
line 58

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

AppKittie

Use this skill as the AppKittie entry point for mobile app store research. It is a wrapper for the focused workflows in skills/, which lets agents that require a root SKILL.md import the repository directly.

Route the Request

Read only the focused workflow that matches the user's intent:

User intent	Load
Discover, browse, filter, or explore apps	`skills/app-discovery/SKILL.md`
Find or prioritize App Store or Google Play keywords	`skills/keyword-research/SKILL.md`
Rewrite titles, subtitles, keyword fields, or descriptions	`skills/metadata-optimization/SKILL.md`
Compare apps or analyze a competitive landscape	`skills/competitor-analysis/SKILL.md`
Analyze fast movers, trends, or growth windows	`skills/growth-analysis/SKILL.md`
Benchmark revenue, pricing, IAPs, or monetization	`skills/revenue-analysis/SKILL.md`
Analyze Meta ads, Apple Search Ads, creatives, or UA angles	`skills/ad-intelligence/SKILL.md`
Find influencers, creators, or organic content for an app or niche	`skills/creator-discovery/SKILL.md`
Analyze user reviews, complaints, sentiment, or feature requests	`skills/review-analysis/SKILL.md`
Capture reusable app, audience, rival, and goal context	`skills/app-marketing-context/SKILL.md`

For tool coverage and parameter details, read tools/REGISTRY.md only when you need the exact API or MCP field matrix.

Data Access

Prefer live AppKittie data. Use the MCP tools if the client exposes them:

search_apps
get_app_detail
get_app_historicals
get_app_countries
list_store_rankings
get_store_ranking_history
search_ads
get_ad_detail
list_creators
list_organic_content
get_keyword_difficulty
batch_keyword_difficulty
get_app_reviews
get_supported_countries

If MCP tools are unavailable, use the REST API at https://appkittie.com/api/v1 when the user has provided an AppKittie API key. Send the key as Authorization: Bearer <key>. Do not expose, log, or repeat API keys.

If no live data access is available, explain what needs to be connected before making data-backed claims. Do not invent AppKittie metrics.

Operating Rules

Clarify only the missing inputs that block the request, such as app id, country, store, category, competitors, or seed keywords.
State the filters, storefront, country, and time window used for any live data pull.
Treat downloads, revenue, growth, ads, and keyword metrics as estimates or signals unless AppKittie says otherwise.
Synthesize findings into decisions, tables, and next actions instead of dumping raw JSON.
When one workflow naturally leads to another, say so and load the next focused workflow only if needed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free