Netlify Status
Checks the latest Netlify deploy for all sites (or a specific site if named) via the Netlify API and reports ready/building/error state.
Entry verified April 21, 2026
The short answer
Pulls the auth token from ~/Library/Preferences/netlify/config.json, then queries the deploys endpoint for each of the 17 catalogued sites. Reports OK for ready, ERROR with the error message, or BUILDING/UPLOADING in progress with an option to re-run.
When to use it
Run first thing in the morning as a portfolio check, after merging a PR to confirm the deploy landed, or when something feels off and you want to rule out a stuck build. Filter to one site by name, or pass all to scan every site in the list.
Setup
- 1
Save as ~/.claude/skills/netlify-status/SKILL.md.
- 2
Token is read from /Users/bryancollins/Library/Preferences/netlify/config.json — no extra auth step.
- 3
Invoke: /netlify-status all to scan every site, or /netlify-status <name> to filter by substring.
- 4
With no argument, the skill asks which site(s) to check before running anything.
- 5
Covers 17 sites by site ID — tenderwatch, vendors, fluentatdesk, readingcurator, bawt, the flash reports, leinster pairs.
Example
You: /netlify-status Claude: 🟢 vendors.ie (2m ago) | 🟢 fluentatdesk.com (14h ago) | 🔴 readingcurator.com (1h ago — build failed)
Source & attribution
- Author
- Bryan Collins
- Licence
- MIT (author's own work)
- Type
- Original
Original pattern published under MIT — attribution preserved by convention, not licence requirement.
Caveats
Only covers Netlify. Wrap for Vercel/Cloudflare Pages separately.
56 skills across 10 categories, all licence-verified.