asoscan-setup
Connect ASOScan Accounts and Configure Integrations
ASOScan setup spans assistant connections, API credentials, webhook destinations, and app store permissions. This skill guides each setup path and explains verification steps and account restrictions.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "asoscan-setup" from https://skillstore.io/skills/asoscan-asoscan-setup.md and its manifest at https://skillstore.io/api/skills/asoscan-asoscan-setup/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-setup". I want to connect ASOScan to Claude but have no API key.
Expected outcome:
- If ASOScan tools are unavailable, add the ASOScan connector or plugin from Claude's directory and authorize your account.
- An API key is only needed for coding agents without connected ASOScan tools.
- After connecting, the assistant can check usage through get_usage.
Using "asoscan-setup". The ASOScan usage check returns 403.
Expected outcome:
- A 403 indicates that your plan does not include API access.
- Review your plan before retrying; creating another key does not resolve a plan restriction.
Using "asoscan-setup". Can you create my Teams webhook through the API?
Expected outcome:
- Webhook endpoints must be added in the ASOScan dashboard.
- Confirm the current Microsoft Workflows setup, then select Microsoft Teams as the ASOScan delivery format.
- Enter the workflow destination, choose events, and use Send test to verify delivery.
Security Audit
Medium RiskMost alerts reflect Markdown formatting, documented setup commands, or legitimate authentication to ASOScan; no evidence found of prompt injection or unauthorized exfiltration. Five findings identify plaintext credential persistence through shell configuration or persistent environment settings. Webhook verification guidance also omits a timestamp freshness check, leaving replay prevention unspecified.
Confirmed security concerns (1)
Capability review items (5)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (23)
๐ Network access (2)
๐ Filesystem access (2)
๐ Env variables (5)
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-setup/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/asoscan-asoscan-setup?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/asoscan-asoscan-setup?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/asoscan-asoscan-setup/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/asoscan-asoscan-setup.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-setup security audit report (audit version 1) [Author version 1.3.7]. Skillstore. https://skillstore.io/skills/asoscan-asoscan-setup/audits/1BibTeX citation
@techreport{asoscan-asoscan-asoscan-setup-2026,
author = {asoscan},
title = {asoscan-setup security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/asoscan-asoscan-setup/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-setup 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-setup/audits/1"
identifiers:
- type: other
value: "skillstore:asoscan-asoscan-setup:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Connect an Assistant
Choose an assistant connection path, authorize ASOScan access, and check remaining API credits when connected tools are available.
Prepare Coding Agent Access
Create an appropriately scoped API key, configure access locally, and distinguish authentication errors from plan restrictions.
Configure Team Alerts
Select webhook events and delivery formats, connect a Slack or Teams destination, and test delivery through the ASOScan dashboard.
Try These Prompts
Help me connect my ASOScan account to Claude. Check whether ASOScan tools are available before asking me to create an API key.
Guide me through creating a read-only ASOScan API key for Codex. Keep credentials out of chat and use session-only secret handling.
Guide me through ASOScan Slack webhook setup. Check current official Slack instructions, explain event selection, and show how to test delivery.
Plan ASOScan Signed JSON webhook setup for my HTTPS endpoint. Cover HMAC validation, timestamp freshness, secret storage, and dashboard testing without registering anything automatically.
Best Practices
- Choose read-only access unless your workflow requires changes, and keep credentials in protected storage rather than shell startup files.
- Verify current official instructions before guiding users through Slack, Microsoft Teams, Google, or Apple setup.
- Verify connectivity and test webhook delivery before relying on an integration; validate signed event timestamps as well as signatures.
Avoid
- Do not paste API keys, webhook signing secrets, or private destination URLs into shared conversations or repositories.
- Do not attempt public API webhook registration or assume every account exposes the same integration features.
- Do not promise ranking improvements, store listing publication, or ad account setup from this skill.