integrationslisted

# `/integrations` — Third-party integration page generator Integration pages capture a narrow but high-converting search behavior: prospects who already want the site's product but need to verify it plays nicely with their existing stack. These pages also stack topical authority — a SaaS with 50 integration pages outranks one with 0 even if the underlying product is identical. This skill is most useful for SaaS, API products, and developer tools. Service businesses (consulting, catering, medical) rarely need integration pages — the skill flags this at start. ## Inputs Required (asked at start if not given): - **Site** — must match a folder under `sites/[name]/`. Must have `product_type=saas` or `product_type=api` in `site-info.md`. - **Integration target** — the named tool (Salesforce, HubSpot, Zapier, Slack, Notion, etc.). Optional (per-run overrides): - **Integration type** — `native` (built-in feature) | `via-zapier` (no-code middleware) | `via-api` (custom API connection) | `via-webhook` (event-driven). Defaults to reading from site's integrations registry in `site-info.md`. - **Verified by** — `engineering` (defaults — implies actual integration code exists) | `roadmap` (planned but not shipped — flagged on page). Skill refuses if undeclared. ## Workflow This skill follows `/service`'s workflow (Steps 0–11) with the page-type-specific differences listed below. Read `.claude/skills/service/SKILL.md` end-to-end before running. ### What's unique to `/integrations`