Agent skill

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.

MITAuto-check passedMarketing & SEO

Install Competitor Tracking

skills CLI

$ npx skills add appeeky/aso-skills --skill competitor-tracking -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills competitor-tracking --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/competitor-tracking .claude/skills/competitor-tracking && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "competitor-tracking" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/competitor-tracking into .claude/skills/competitor-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-tracking", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/appeeky/aso-skills/tree/main/skills/competitor-tracking

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add appeeky/aso-skills --skill competitor-tracking -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills competitor-tracking --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/competitor-tracking .agents/skills/competitor-tracking && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "competitor-tracking" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/competitor-tracking into .agents/skills/competitor-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-tracking", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add appeeky/aso-skills --skill competitor-tracking -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills competitor-tracking --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/competitor-tracking .cursor/skills/competitor-tracking && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "competitor-tracking" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/competitor-tracking into .cursor/skills/competitor-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-tracking", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/appeeky/aso-skills.git --path skills/competitor-tracking

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add appeeky/aso-skills --skill competitor-tracking -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills competitor-tracking --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/competitor-tracking .gemini/skills/competitor-tracking && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "competitor-tracking" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/competitor-tracking into .gemini/skills/competitor-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-tracking", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install appeeky/aso-skills competitor-tracking

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add appeeky/aso-skills --skill competitor-tracking -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/competitor-tracking .github/skills/competitor-tracking && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "competitor-tracking" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/competitor-tracking into .github/skills/competitor-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-tracking", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add appeeky/aso-skills --skill competitor-tracking -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills competitor-tracking --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/competitor-tracking .opencode/skills/competitor-tracking && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "competitor-tracking" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/competitor-tracking into .opencode/skills/competitor-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-tracking", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: competitor-tracking
GitHub stars: 2.2k
Token cost: ~1.6k tokens
SKILL.md length: 516 words
Files: 1
Skills in repo: 39
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

Works in 4 steps: Check for app-marketing-context.md → Ask: Who are your top 3–5 competitors?… → Ask: How often do you want to review?… → …
Wants to monitor competitor apps on an ongoing basis — tracking metadata changes
SKILL.md covers One-Time Analysis vs Ongoing…, Setup: Define Your Watchlist, What to Track and Weekly Competitive Report…, plus 4 more sections
Calls curl and jq; reaches api.appeeky.com

What it does

Competitor Tracking is an agent skill from appeeky/aso-skills. When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Use when the user mentions "competitor monitoring", "track competitors", "competitor alert", "competitor changed their title", "watch a competitor app", "competitor weekly report", "competitive intelligence", or "what changed in competitor's listing". For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Competitor analysis. The repository describes itself as: AI agent skills for App Store Optimization (ASO) and app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent… The licence is MIT.

When your agent uses it

Wants to monitor competitor apps on an ongoing basis — tracking metadata changes
Screenshot updates
The user mentions competitor monitoring
Track competitors

Example prompts

“competitor monitoring”
“track competitors”
“competitor alert”
“/competitor-tracking”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

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

What it can do on your machine

Read from SKILL.md and the folder at commit 3919d7c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- api.appeeky.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Competitor Tracking loads about 1.6k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 516 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~139
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from appeeky/aso-skills at commit 3919d7c, republished under its MIT licence (© appeeky). 516 words, ~1,576 tokens.

Download SKILL.mdSave it as .claude/skills/competitor-tracking/SKILL.md (or your agent's skills folder).

name: competitor-tracking
description: When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Use when the user mentions "competitor monitoring", "track competitors", "competitor alert", "competitor changed their title", "watch a competitor app", "competitor weekly report", "competitive intelligence", or "what changed in competitor's listing". For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements, see market-movers.
metadata.version: 1.0.0

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` skill	This skill (`competitor-tracking`)
Frequency	One-time deep dive	Weekly/monthly recurring
Output	Strategy document	Change log + alerts
Focus	Gap analysis, positioning	What changed and why it matters
Data	Snapshot	Delta (before vs after)

Setup: Define Your Watchlist

Check for app-marketing-context.md
Ask: Who are your top 3–5 competitors? (get App IDs if possible)
Ask: How often do you want to review? (weekly recommended)
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

Show full SKILL.md (187 more words)Show less

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 changed	Response
Competitor targets your #1 keyword in title	Defend: check your metadata is fully optimized; consider increasing ASA bids
Competitor drops a keyword you share	Opportunity: double down, increase bid in ASA
Competitor upgrades screenshots	Audit yours — are they still best in category?
Competitor rating drops below 4.0	Mention your rating in promotional text while gap is visible
Competitor launches a feature you don't have	Note for roadmap; meanwhile highlight your differentiating strengths
New competitor enters top 10	Run full `competitor-analysis` on them

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

Files

Just SKILL.md in skills/competitor-tracking of appeeky/aso-skills.

Open the folder on GitHubat commit 3919d7c

Compare with similar skills

Competitor Tracking next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Competitor Tracking compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Competitor Tracking this skillappeeky/aso-skills	2.2k	—	~1.6k	Automated safety check: Pass	MIT	2 days ago
SEO Content Brief GeneratorAgriciDaniel/claude-seo	18k	2 repos	~2.6k	Automated safety check: Pass	MIT	4 days ago
Startup Competitorsferdinandobons/startup-skill	1.2k	1 repos	~4.1k	Automated safety check: Pass	MIT	3 mo ago
Amazon Listing Competitor Analysisbrowser-act/skills	6.1k	2 repos	~3.2k	Automated safety check: Pass	MIT	1 mo ago
SEO DataforseoAgriciDaniel/codex-seo	791	2 repos	~4.6k	Automated safety check: Pass	MIT	27 days ago
Competitor ProfilingNexus-JPF/note-companion	870	4 repos	~3.5k	Automated safety check: Pass	MIT	yesterday

Similar skills

SEO Content Brief Generator
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
18k GitHub starsUsed in 2 repos~2.6k tokens
Marketing & SEOAuto-check passed
Startup Competitors
ferdinandobons/startup-skill
Deep competitive intelligence for any market. An agent skill from ferdinandobons/startup-skill.
1.2k GitHub starsUsed in 1 repo~4.1k tokens
Marketing & SEOAuto-check passed
Amazon Listing Competitor Analysis
browser-act/skills
Analyzes a competitor's Amazon listing by ASIN with BrowserAct data extraction, then reports what it does well, where the market has gaps and opportunity points for your own listing.
6.1k GitHub starsUsed in 2 repos~3.2k tokens
Marketing & SEOAuto-check passed
SEO Dataforseo
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
791 GitHub starsUsed in 2 repos~4.6k tokens
Marketing & SEOAuto-check passed
Competitor Profiling
Nexus-JPF/note-companion
When the user wants to research, profile, or analyze competitors from their URLs.
870 GitHub starsUsed in 4 repos~3.5k tokens
Marketing & SEOAuto-check passed
Consulting Analysis
bytedance/deer-flow
A skill your agent uses when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial…
83k GitHub starsUsed in 5 repos~8.4k tokens
Marketing & SEOAuto-check passed

Questions about Competitor Tracking

What does Competitor Tracking do?

When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Competitor Tracking is an agent skill from appeeky/aso-skills. When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features.

When should I use Competitor Tracking?

Competitor Tracking fits situations like: wants to monitor competitor apps on an ongoing basis — tracking metadata changes; screenshot updates; the user mentions competitor monitoring; track competitors.

How do I install Competitor Tracking in Claude Code?

Run `npx skills add appeeky/aso-skills --skill competitor-tracking -a claude-code`. Or copy the skill folder (skills/competitor-tracking in appeeky/aso-skills) into .claude/skills/competitor-tracking in your project. Claude Code loads it when a task matches its description.

How do I install Competitor Tracking in Codex?

Run `npx skills add appeeky/aso-skills --skill competitor-tracking -a codex`. Or copy the skill folder (skills/competitor-tracking in appeeky/aso-skills) into .agents/skills/competitor-tracking in your project. Codex loads it when a task matches its description.

Can I use Competitor Tracking in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appeeky/aso-skills --skill competitor-tracking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/competitor-tracking, .gemini/skills/competitor-tracking, .github/skills/competitor-tracking and .opencode/skills/competitor-tracking in your project.

What does Competitor Tracking need to run?

Going by SKILL.md and its folder, Competitor Tracking needs the command-line tools its instructions call (curl and jq).

Does Competitor Tracking access the network?

SKILL.md names 1 domain. In commands or code: api.appeeky.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Competitor Tracking safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Competitor Tracking use?

Competitor Tracking is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Competitor Tracking use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Competitor Tracking?

Skills that share tags, products or a category with Competitor Tracking: SEO Content Brief Generator (AgriciDaniel/claude-seo, 18k stars), Startup Competitors (ferdinandobons/startup-skill, 1.2k stars), Amazon Listing Competitor Analysis (browser-act/skills, 6.1k stars) and SEO Dataforseo (AgriciDaniel/codex-seo, 791 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Competitor Tracking?

appeeky (a GitHub organization) maintains it in appeeky/aso-skills, which has 2,152 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.

Source: appeeky/aso-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Competitor Tracking

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Competitor Tracking

One-Time Analysis vs Ongoing Tracking

Setup: Define Your Watchlist

What to Track

Metadata Changes

Keyword Ranking Changes

Ratings and Reviews

Chart Positions

Pricing and Paywall

Weekly Competitive Report Template

Monthly Deep-Dive Triggers

Automation Options

Manual (recommended for small teams)

Semi-automated

Appeeky MCP (in Claude/Cursor)

Competitive Response Playbook

Related Skills

Files

Compare with similar skills

Similar skills

More from appeeky/aso-skills

Related

Questions about Competitor Tracking