CtrlK
BlogDocsLog inGet started
Tessl Logo

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. 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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable monitoring playbook with concrete API calls, an executable automation script, a weekly report template, and clear workflow cadence and triggers. It is concise without explaining concepts Claude already knows and needs no external references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains basic concepts (what metadata, keywords, or ratings are) and every section is actionable rather than padded; not score 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Provides fully executable guidance throughout: concrete Appeeky API calls (e.g. "GET /v1/apps/:id"), a copy-paste bash script using curl and jq, and named MCP tools (get_app, get_app_keywords, get_app_reviews), matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced: a numbered 1–4 setup, a weekly "Run this analysis every Monday" cadence, an explicit report template, and listed monthly deep-dive triggers; no validation cap applies since this is read-only monitoring rather than a destructive or mutating batch operation.

3 / 3

Progressive Disclosure

The skill is a single self-contained file with well-organized sections and clear headers, and there are no nested or multi-level references to get lost in; no bundle files exist, so the well-organized inline structure is appropriate per the simple-skill scoring note.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, complete on both what and when, and clearly distinguished from related skills via explicit cross-references. It uses third-person voice and contains no vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features" — matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (ongoing monitoring of competitor apps with the listed change types) and when (a "Use when the user mentions..." clause with explicit triggers), matching the score-3 anchor.

3 / 3

Trigger Term Quality

Provides broad natural-language triggers users would actually say ("competitor monitoring", "track competitors", "competitor alert", "watch a competitor app", "competitor weekly report", "competitive intelligence", "what changed in competitor's listing"), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (ongoing tracking) and explicitly differentiates from sibling skills ("For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements, see market-movers."), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.