appeeky/aso-skills

competitor-tracking

When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/appeeky/aso-skills --skill competitor-tracking

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Competitor Tracking

You set up and run ongoing competitor surveillance — catching metadata changes, keyword shifts, rating drops, and new feature launches before they impact your rankings.

One-Time Analysis vs Ongoing Tracking

competitor-analysis skillThis skill (competitor-tracking)
FrequencyOne-time deep diveWeekly/monthly recurring
OutputStrategy documentChange log + alerts
FocusGap analysis, positioningWhat changed and why it matters
DataSnapshotDelta (before vs after)

Setup: Define Your Watchlist

  1. Check for app-marketing-context.md
  2. Ask: Who are your top 3–5 competitors? (get App IDs if possible)
  3. Ask: How often do you want to review? (weekly recommended)
  4. Ask: What are you most concerned about? (keywords, ratings, creative, pricing)

Use Appeeky to identify competitors if unknown:

bash
GET /v1/keywords/ranks?keyword=meditation&country=us&limit=10
GET /v1/apps/:id/intelligence  # check competitors array

What to Track

Metadata Changes

Check weekly using Appeeky:

bash
GET /v1/apps/:id  # title, subtitle, description

Watch for:

  • Title changes — new keyword being targeted, repositioning
  • Subtitle changes — testing new hooks or keywords
  • Description changes — messaging strategy shift (Google Play especially)
  • Screenshot updates — new creative direction or A/B test winner shipped

Keyword Ranking Changes

bash
GET /v1/apps/:id/keywords  # their ranking keywords
GET /v1/keywords/ranks?keyword=[shared keyword]  # who's ranking where

Watch for:

  • Keywords they're newly ranking for (they optimized for this — should you?)
  • Keywords they dropped (opportunity to capture)
  • A competitor jumping above you for a shared keyword

Ratings and Reviews

bash
GET /v1/apps/:id/reviews?sort=recent&limit=20
GET /v1/apps/:id  # current rating

Watch for:

  • Rating drop (they shipped a bad update — opportunity to highlight your stability)
  • Surge of 1-stars around a specific complaint (user pain point you could solve)
  • New positive reviews praising a feature you don't have

Chart Positions

bash
GET /v1/market/movers?genre=[genre_id]&country=us
GET /v1/categories/:id/top?country=us&limit=25

Watch for:

  • A competitor entering or exiting top 10 in your category
  • New competitor entering your space from a chart rise

Pricing and Paywall

Manually check every 4–6 weeks:

  • Trial length changes
  • Price changes (lower = aggressive growth; higher = LTV optimization)
  • New paywall format or plans

Weekly Competitive Report Template

Run this analysis every Monday:

Competitive Update — Week of [Date]

Apps tracked: [list names]

CHANGES DETECTED:
━━━━━━━━━━━━━━━━━
[Competitor Name]
  Metadata: [changed / no change]
    → [specific change if any]
  Top keywords: [gained X / lost Y / stable]
  Rating: [X.X → X.X] ([+/-N] ratings this week)
  Chart position: [#N → #N in category]
  New reviews theme: [if notable]

[Repeat per competitor]

OPPORTUNITIES IDENTIFIED:
1. [Competitor X dropped keyword Y — consider targeting it]
2. [Competitor X has surge of complaints about Z — your strength]
3. [Competitor X raised price — positioning opportunity]

THREATS:
1. [Competitor X now ranks #3 for [keyword] — we're at #8]
2. [New entrant spotted: [name] — check their metadata]

ACTION ITEMS:
1. [Specific response to a change]
2. [Keyword to target based on competitor gap]

Monthly Deep-Dive Triggers

Run a full competitor-analysis when:

  • A competitor jumps 10+ positions in the category chart
  • A competitor changes their title (signals major repositioning)
  • A new competitor enters the top 10 in your category
  • Your ranking drops on a keyword a competitor recently targeted

Automation Options

Manual (recommended for small teams)

Set a calendar reminder. Run the Appeeky API calls above. Fill the template.

Semi-automated

Build a script that calls Appeeky weekly and diffs results:

bash
#!/bin/bash
APPS=("6759740679" "987654321" "111222333")
KEY="apk_your_key"

for APP_ID in "${APPS[@]}"; do
  echo "=== $APP_ID ==="
  curl -s "https://api.appeeky.com/v1/apps/$APP_ID" \
    -H "X-API-Key: $KEY" | jq '.data | {title, subtitle, rating, reviewCount}'
done

Store results weekly and diff with the previous week's output.

Appeeky MCP (in Claude/Cursor)

Ask your agent each Monday:

"Run a competitor check on apps [ID1], [ID2], [ID3] and 
compare their metadata and top keywords to last week."

The agent will use get_app, get_app_keywords, get_app_reviews to produce the report.

Competitive Response Playbook

What changedResponse
Competitor targets your #1 keyword in titleDefend: check your metadata is fully optimized; consider increasing ASA bids
Competitor drops a keyword you shareOpportunity: double down, increase bid in ASA
Competitor upgrades screenshotsAudit yours — are they still best in category?
Competitor rating drops below 4.0Mention your rating in promotional text while gap is visible
Competitor launches a feature you don't haveNote for roadmap; meanwhile highlight your differentiating strengths
New competitor enters top 10Run full competitor-analysis on them

Related Skills

  • competitor-analysis — Deep one-time competitive strategy
  • keyword-research — Act on the keyword gaps you find
  • market-movers — Catch chart-level competitor movements automatically
  • apple-search-ads — Respond to competitor keyword moves with ASA bids
  • aso-audit — Run on yourself after finding competitive gaps

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
appeeky
커뮤니티

android-aso

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

설치 수
5
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

localization

When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

review-management

When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

web-to-app-funnel

When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일