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.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「asoscan-setup」を使用しています。 I want to connect ASOScan to Claude but have no API key.
期待される結果:
- 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.
「asoscan-setup」を使用しています。 The ASOScan usage check returns 403.
期待される結果:
- 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.
「asoscan-setup」を使用しています。 Can you create my Teams webhook through the API?
期待される結果:
- 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.
セキュリティ監査
中リスクMost 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.
確認済みのセキュリティ上の懸念 (1)
機能レビュー項目 (5)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
リスク要因
⚙️ 外部コマンド (23)
🌐 ネットワークアクセス (2)
📁 ファイルシステムへのアクセス (2)
🔑 環境変数 (5)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/asoscan-asoscan-setup/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/asoscan-asoscan-setup?utm_source=security_passport_badge)HTMLバッジ
<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>埋め込みカード
<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>学術引用 (APA · BibTeX · CFF)
APA形式の引用
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形式の引用
@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 スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
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.
これらのプロンプトを試す
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.
ベストプラクティス
- 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.
回避
- 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.