Update to ASOScan App Store Optimization

{
  "description": "When the user wants to set up ASOScan, for example to connect the ASOScan plugin or connector in ChatGPT or Claude, get an API access key for a coding agent, set up webhooks (including Slack or Microsoft Teams alerts), or connect Google Play Console or App Store Connect. Also use when the user mentions \"connect ASOScan\", \"connect my ASOScan account\", \"get my API key\", \"set up webhooks\", \"send alerts to Slack\", \"connect my Play Console\", \"connect my App Store account\", or \"how do I hook this up\". Works with no account and no key.",
  "included_files": [],
  "name": "asoscan-setup",
  "skill_md_contents": "---\nname: asoscan-setup\ndescription: When the user wants to set up ASOScan, for example to connect the ASOScan plugin or connector in ChatGPT or Claude, get an API access key for a coding agent, set up webhooks (including Slack or Microsoft Teams alerts), or connect Google Play Console or App Store Connect. Also use when the user mentions \"connect ASOScan\", \"connect my ASOScan account\", \"get my API key\", \"set up webhooks\", \"send alerts to Slack\", \"connect my Play Console\", \"connect my App Store account\", or \"how do I hook this up\". Works with no account and no key.\nmetadata:\n  version: 1.3.1\n---\n\n# ASOScan Setup & Connect\n\nGuides the user through configuring ASOScan: getting an **API key**, setting up\n**webhooks** (incl. Slack / Teams), and **connecting** their Play Console / App\nStore Connect accounts. **No API key needed to run this skill** — it's how they get\nset up.\n\n> ⚑ **Third-party UIs change — verify live, don't recite from memory.** For any\n> step that happens **outside** ASOScan (Slack, Microsoft Teams / Power Automate,\n> Google Play Console / Google Cloud, App Store Connect), **look up the current\n> official instructions with web search before walking the user through them**, and\n> prefer ASOScan's own up-to-date tutorials/docs where linked below. The\n> **ASOScan-side** steps in this skill are current; the **external** steps you must\n> confirm live each time.\n>\n> **Gating note:** webhooks and connections may not appear in every account —\n> they're rolling out and depend on the plan/feature flags. If the user doesn't see\n> a section, tell them the feature may not be enabled for their account yet.\n\n---\n\n## 0. Connect your ASOScan account (ChatGPT, Claude, Claude Code)\n\nFirst check: can you call the ASOScan tools (for example `get_usage`)?\n\n- **Yes**: the account is connected. Call `get_usage` (free) and tell the user how many API credits are left. Skip the API key section; it is only for coding agents without the tools.\n- **No, and you are in ChatGPT or Claude**: tell the user to connect their ASOScan account. In ChatGPT, add the ASOScan plugin from the plugin directory. In Claude, add the ASOScan connector or plugin from the directory. Then sign in to ASOScan (or create an account; new accounts start with a free trial) and allow access. Allowing changes lets ASOScan add apps, keywords and competitors, save drafts, and post review replies the user approves.\n- **No, and you are in Claude Code**: `claude plugin marketplace add ASOScan/aso-skills`, then `claude plugin install asoscan@asoscan`, then sign in when Claude Code asks. Or use an API key (section 1).\n- **No, and you are in another coding agent**: use an API key (section 1).\n\nTo disconnect an assistant later: ASOScan **Settings → Connected AI apps → Disconnect**.\n\n---\n\n## 1. Get your ASOScan API key\n\nCopy this checklist and tick each step:\n\n```\nAPI key setup\n- [ ] 1. Create an ASOScan account + add at least one app\n- [ ] 2. Settings → API access → New key name → Read-only / Read+write → Create key\n- [ ] 3. Copy the key now (asosk_live_… is shown once)\n- [ ] 4. export ASOSCAN_API_KEY=\"asosk_live_…\"\n- [ ] 5. Verify → expect 200 + your usage\n```\n\n**Details:**\n1. Sign up at **asoscan.com** and add an app. The API is **owner-scoped** — it works\n   on the apps in your account, so you need at least one.\n2. **Settings → API access** → type a **New key name** → choose **Read-only** or\n   **Read + write** (write lets the skills add keywords & competitors) → **Create\n   key**. **Copy it now — `asosk_live_…` is shown only once.**\n3. Set it as an environment variable:\n   ```bash\n   export ASOSCAN_API_KEY=\"asosk_live_…\"     # bash/zsh (add to ~/.zshrc to persist)\n   ```\n   ```fish\n   set -Ux ASOSCAN_API_KEY \"asosk_live_…\"     # fish\n   ```\n   ```powershell\n   setx ASOSCAN_API_KEY \"asosk_live_…\"        # Windows PowerShell — open a new terminal after\n   ```\n4. Verify — a `200` with your usage means you're set:\n   ```bash\n   curl -s \"https://asoscan.com/api/public/v1/usage\" -H \"Authorization: Bearer $ASOSCAN_API_KEY\"\n   ```\n   A `401` names what went wrong (no key sent, wrong prefix, unknown or revoked key);\n   a `403` means the plan doesn't include API access.\n\n   Working from a clone of this repo? `bash scripts/asoscan-check.sh` does the same\n   thing. It ships with the repo, not inside an installed skill, so the relative path\n   only resolves from the repo root — use the `curl` above otherwise.\n\nIf the **API access** section isn't visible, the plan may not include API access —\nsee **asoscan.com/pricing**. Once the key works, come back and use any data skill.\n\n---\n\n## 2. Webhooks — get pushed events (Slack / Teams / your endpoint)\n\n**What they are:** ASOScan can POST an event to a URL you own the moment something\nhappens — a rank drop, a competitor metadata change, a new opportunity, etc. — so\nyour team reacts without polling.\n\n**Where:** ASOScan **dashboard → Settings → Webhooks**. Webhooks are **configured in\nthe dashboard, not via the public API** — a skill can't self-register them; guide\nthe user, don't `curl` it.\n\n**Steps (ASOScan side) — the form is inline on that page:**\n1. Go to **Settings → Webhooks**.\n2. **Delivery format** — pick **Signed JSON** (your own HTTPS endpoint), **Slack**,\n   or **Microsoft Teams**.\n3. **Endpoint URL** — paste the destination (see per-format below).\n4. **Events** — tap the event chips to choose which fire. The page shows the live,\n   authoritative list (e.g. rank updated, app-sync completed, competitor metadata\n   changed, review analyzed, new opportunities).\n5. **Label** (optional) — a name like \"Ops Slack relay\".\n6. Click **Add endpoint**, then **Send test** on the new row to confirm it lands.\n\n**Signed JSON endpoint:** each delivery is **HMAC-SHA256 signed** — header\n`X-ASOScan-Signature: t=<timestamp>,v1=<hex>` over `\"{timestamp}.{rawBody}\"`. Verify\nit with a stdlib HMAC check (no SDK). The signing secret (`whsec_…`) is shown\n**once** when you add the endpoint. For Slack/Teams there's no secret to manage —\nthe channel URL is the secret.\n\n**Slack:** the user needs a Slack **Incoming Webhook URL** for the target channel,\nthen paste it into ASOScan with format = Slack.\n> **Look up the current Slack steps live** (Slack changes this UI) — search Slack's\n> official docs for creating an *Incoming Webhook* / Slack app with an incoming\n> webhook. ASOScan also has a walkthrough: **asoscan.com/blog/send-aso-alerts-to-slack**.\n\n**Microsoft Teams:** Teams delivery is built for the **Power Automate \"Workflows\"**\npath (Microsoft is retiring the old Office 365 \"Incoming Webhook\" connector), so the\nuser creates a Workflow that \"posts to a channel when a webhook request is received\"\nand pastes that workflow URL into ASOScan with format = Teams.\n> **Look up the current Microsoft Teams / Power Automate steps live** — search\n> Microsoft's official docs for the *\"Post to a channel when a webhook request is\n> received\"* Workflows template. ASOScan walkthrough:\n> **asoscan.com/blog/send-aso-alerts-to-microsoft-teams**.\n\nHonesty: webhooks shorten your reaction time — they are **not** a ranking signal.\n\n---\n\n## 3. Connect Google Play Console or App Store Connect\n\nConnecting a store account lets ASOScan read the app's own reviews, ratings and listing text and post the review replies the user approves.\n\n1. Open the app in ASOScan and click **Connect** in the app header. (Settings → Connections only lists and disconnects accounts.)\n2. Pick Google Play or App Store Connect and follow the wizard. The wizard shows the current steps and links the official Google and Apple guides; follow it rather than steps from memory.\n3. For anything that happens on Google's or Apple's side, look up the current official instructions with web search before guiding the user.\n\nIf the user does not see **Connect**, the feature may not be enabled for their account yet.\n\nHonesty: connected accounts read reviews, ratings and listing text and post approved review replies. ASOScan does not publish listing text to the stores.\n\n## 4. Ad accounts\n\nThis skill does not cover ad accounts. Point the user to the ASOScan app.\n\n---\n\n## Related\n\n- **aso-fundamentals** — learn ASO while you get set up (no key needed).\n- The **data skills** — once the key is set: keyword-intelligence, keyword-opportunities,\n  keyword-spy, competitor-analysis, review-insights, metadata-audit — your real numbers.\n\nFull API reference + try-it console: <https://asoscan.com/api/developers>\n"
}