asoscan-router
Route ASO Tasks Through ASOScan
App store optimization requests often stall when account setup or task selection is unclear. This router checks prerequisites and directs requests to relevant ASOScan specialists.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "asoscan-router" from https://skillstore.io/skills/asoscan-asoscan-router.md and its manifest at https://skillstore.io/api/skills/asoscan-asoscan-router/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 "asoscan-router". How does ASO work? I do not have an API key.
Expected outcome:
Route: aso-fundamentals. General ASO guidance does not require an API key or access to your account.
Using "asoscan-router". My ASOScan account has no apps. Help me start tracking my published app.
Expected outcome:
- Please provide your App Store or Google Play link and the country you want to track.
- Adding an app uses two API credits and one app slot.
- Please also provide store links for competitors you want to track.
Using "asoscan-router". Which workflow handles a full ASO review of my tracked app?
Expected outcome:
- First, resolve the app in your ASOScan account.
- Start with metadata-audit for listing quality and the ASO score.
- Then use keyword-opportunities and competitor-analysis for keyword gaps and rival comparisons.
Security Audit
SafeAll 37 static findings are false positives: Markdown delimiters, tool names, documented service URLs, and intended authentication or shell operations. The API example uses quoted arguments and sends the service-specific key only to the documented ASOScan HTTPS endpoint. No evidence found of credential exfiltration, system reconnaissance, malicious execution, or audit-directed prompt injection in the supplied file.
Risk Factors
⚙️ External commands (29)
🌐 Network access (3)
🔑 Env variables (3)
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-asoscan-router/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/asoscan-asoscan-router?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/asoscan-asoscan-router?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/asoscan-asoscan-router/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/asoscan-asoscan-router.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). asoscan-router security audit report (audit version 1) [Author version 1.3.7]. Skillstore. https://skillstore.io/skills/asoscan-asoscan-router/audits/1BibTeX citation
@techreport{asoscan-asoscan-asoscan-router-2026,
author = {asoscan},
title = {asoscan-router security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/asoscan-asoscan-router/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: "asoscan-router 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-asoscan-router/audits/1"
identifiers:
- type: other
value: "skillstore:asoscan-asoscan-router:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Start Tracking a Published App
Guide app identification, country selection, competitor setup, and initial recommendations before choosing a specialist workflow.
Coordinate Keyword and Competitor Research
Resolve a tracked app and route ranking, keyword opportunity, or rival comparison requests to the appropriate specialist.
Direct Review and Listing Work
Send sentiment analysis and review reply requests to review insights, and localized listing requests to metadata audit.
Try These Prompts
Explain app store optimization basics and route me to general guidance without accessing account data.
Help me set up [app store link] for [country]. Check my ASOScan connection and ask before credit-consuming changes.
For [tracked app] in [country], find the right workflow for keyword opportunities and competitor rankings. Reuse existing results when possible.
Coordinate an ASO review of [tracked app] in [country]. Start with metadata, then keyword opportunities and competitor analysis. Confirm paid calls first.
Best Practices
- Specify the app store link and tracking country; provide full store links for competitors.
- Keep API keys in the environment and avoid printing or sharing their values.
- Confirm credit-consuming operations and reuse keyword research results to avoid repeat charges.
Avoid
- Assuming the router includes specialist implementations or generates account data without a connection.
- Guessing the tracking country or sending bare competitor identifiers instead of store links.
- Repeating expensive keyword research calls or promising install and revenue outcomes from ASO data.