quip-setuplisted

# Quip Bot setup Guide a WordPress site owner from public-site research to a reviewed Quip Bot configuration. Keep human credentials out of the AI conversation and make every production change explicit and reviewable. ## When to use - "Set up Quip Bot on my WordPress site." - "Research my site before configuring Quip Bot." - "Help me plan the Quip Bot knowledge base." - "Connect this WordPress site to the Quip Bot setup flow." - "Review whether Quip Bot is ready to go live." - "Resume my Quip Bot setup." ## Do not use - For general WordPress administration outside Quip Bot. - To obtain, rotate, or expose an AI-provider secret. - To enable paid Quip Bot capabilities that the account does not own. - To bypass WordPress capabilities, nonces, consent, or a human approval step. - To write through SSH, direct database access, or undocumented plugin internals. ## Current release state Version 0.3.0 is a public alpha with two complete setup paths. - The **API path is the default**: Quip Bot ships its stable public setup API (`quipbot/v1/setup`, API version 1.0, plugin 4.3.0+), and this skill ships the local credential helper (`helper/quip-setup-helper.mjs`) that holds the temporary WordPress Application Password in the macOS Keychain. The agent composes non-secret JSON envelopes and reads non-secret responses; it never sees a credential. - The path is chosen by the public `GET /setup/compatibility` gate, not by a version string: `available: true`, `"1.0"` in `sche