keyword-spy
Find Competitor Keyword Gaps with ASOScan
Competitor rankings can reveal relevant search terms missing from your tracking. This skill uses ASOScan results to summarize keyword coverage, shared rankings, and untracked opportunities.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "keyword-spy" from https://skillstore.io/skills/asoscan-keyword-spy.md and its manifest at https://skillstore.io/api/skills/asoscan-keyword-spy/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "keyword-spy". Illustrative example: find untracked terms for a tracked task app competitor in the United States.
Expected outcome:
- Coverage: 120 returned keywords, including 90 community terms and 30 discovered terms.
- Candidate: daily planner, competitor rank 8, community origin, not tracked; relevant to your planning features.
- Shared term: task manager, competitor rank 12, discovered origin.
- Discovery status: cached. Validate candidate relevance before adding tracking.
Using "keyword-spy". Illustrative example: inspect a newly tracked competitor with no cached discovery.
Expected outcome:
- Coverage: six community terms and no discovered terms.
- Discovery status: none. Background discovery has not supplied cached results.
- This result is not a complete keyword footprint. Repeating the request immediately will not trigger a fresh crawl.
Security Audit
SafeAll 25 static findings are false positives: Markdown formatting, documented API operations, ASOScan URLs, and intended bearer authentication. The skill prohibits printing credentials and requires approval before data changes. No evidence found of credential exfiltration, prompt injection, or unauthorized account access.
Risk Factors
โ๏ธ External commands (22)
๐ Network access (2)
๐ Env variables (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/asoscan-keyword-spy/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/asoscan-keyword-spy?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/asoscan-keyword-spy?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/asoscan-keyword-spy/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/asoscan-keyword-spy.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
asoscan. (2026). keyword-spy security audit report (audit version 1) [Author version 1.3.7]. Skillstore. https://skillstore.io/skills/asoscan-keyword-spy/audits/1BibTeX citation
@techreport{asoscan-asoscan-keyword-spy-2026,
author = {asoscan},
title = {keyword-spy security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/asoscan-keyword-spy/audits/1},
note = {Author version 1.3.7}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "keyword-spy security audit report (audit version 1)"
version: "1.3.7"
type: report
authors:
- name: "asoscan"
date-released: "2026-11-15"
url: "https://skillstore.io/skills/asoscan-keyword-spy/audits/1"
identifiers:
- type: other
value: "skillstore:asoscan-keyword-spy:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Find competitor tracking gaps
Compare a tracked competitor with your app and shortlist relevant ranking terms that you do not track.
Review an app keyword footprint
Inspect your app ranking terms and separate community coverage from cached discovery results.
Prepare a competitive keyword review
Summarize shared ranking terms and propose candidates for later validation across client apps.
Try These Prompts
Show available ranking keywords for my app [app name] in [country]. Report coverage and discovery status.
For tracked competitor [competitor name], find relevant keywords my app [app name] does not track in [country]. Explain each selection.
Compare [my app] with tracked competitor [competitor name] in [country]. Summarize shared terms, competitor ranks, origins, and untracked relevant terms.
Check whether [store URL] is tracked for [my app]. Ask before adding it. Analyze [country] rankings, note cache limits, and shortlist relevant untracked terms.
Best Practices
- Confirm the target app and country before requesting keyword data.
- Filter opportunities for product relevance and review tracking status before recommending candidates.
- Keep credentials private and obtain approval before adding competitors or making other data changes.
Avoid
- Treating every competitor ranking keyword as relevant to your app.
- Repeating requests to force discovery or claiming cached results provide exhaustive coverage.
- Adding competitors without approval or assuming a read-only key permits account changes.