site-check
Answer 'is this site down or is it just me' properly — curl status/timing diagnostics, DNS cross-check, and TLS certificate reads, assembled into a where-it's-broken diagnosis. Use when asked is this website down, why can't I reach this site, check if my site is up, or is the SSL certificate expired. Produces the layered diagnosis (DNS → TLS → HTTP → content), response timing, cert expiry, and the rerunnable commands.
npx skills add mohitagw15856/pm-claude-skills --skill site-check --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Site Check Skill "Is it down or is it me?" is a diagnosis, not a yes/no — a site can fail at DNS, at TLS, at HTTP, or only from your network, and each failure names a different fix. This skill runs the layers in order with plain curl, reads the evidence (status codes, cert dates, resolver agreement), and answers with *where* it's broken, which is the answer that was actually needed. ## What This Skill Produces - **The verdict** — up / down-for-everyone-probably / broken-at-layer-X / likely-just-you, with the evidence - **The layer results** — DNS resolution, TLS handshake + cert expiry, HTTP status, response timing - **The interpretation** — what a 503 vs. a timeout vs. a cert error vs. NXDOMAIN each means, in words - **The commands** — every check rerunnable ## Required Inputs Ask for these if not provided: - **The URL/domain** — as the user experiences it (scheme and path matter; `example.com` up and `example.com/app` down is a real and common state) - **The symptom** — error message, spinner, cert warning — it picks which layer to check first - **Whose site** — theirs (deeper diagnostics welcome) vs. someone else's (status check, politely) ## Framework: The Layer Walk 1. **HTT
- What This Skill Produces
- Required Inputs
- Framework: The Layer Walk
- Output Format
- Quality Checks
- Anti-Patterns
What does the site-check skill do?
Answer 'is this site down or is it just me' properly — curl status/timing diagnostics, DNS cross-check, and TLS certificate reads, assembled into a where-it's-broken diagnosis. Use when asked is this website down, why can't I reach this site, check if my site is up, or is the SSL certificate expired. Produces the layered diagnosis (DNS → TLS → HTTP → content), response timing, cert expiry, and the rerunnable commands.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill site-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.