setuplisted
Install: claude install-skill sitetiller/ai-visibility-skills
# Connect your data sources
Goal: get each credential working with the least access it needs, keep it out of chat and out of git, and prove it works with one real command per service. Public-site checks (`crawlers`, `page`, `sitemap`, `pages`, `links`, `schema`) need no setup. Only the services below do.
## Inputs
- Which services the user wants: Search Console, Bing, GA4, CrUX, IndexNow.
- Their site as verified in each tool (for Search Console, a domain property `sc-domain:example.com` or a URL-prefix property `https://www.example.com/`).
## Rules before anything else
1. **Never ask the user to paste a key, token or JSON file into chat.** Tell them to set it in their own shell or a local `.env` and confirm with the test commands below.
2. **Gitignore secrets first:** add `.env`, key files such as `gsc-key.json`, and `.sitetiller/` to `.gitignore` before the key exists.
3. **Read-only where the vendor allows it.** Google: `webmasters.readonly` and `analytics.readonly`. Bing and CrUX keys cannot be scoped (see below), so say so.
4. **Windows PowerShell sets variables differently:** `$env:NAME = "value"` instead of `export NAME=value`.
## Search Console (Google)
The CLI uses either a service account key or a short-lived access token.
**Option A: service account (best for repeat use)**
1. In a Google Cloud project, enable the **Google Search Console API**.
2. Create a service account and a JSON key. Console: Service accounts, the account, Keys, Add key, Create new key, JSO