agentsclimarketplace

Website resilience

Skill paulgrape/skill-auditor/templates/website-resilience

Audit Agent Skills against repo reality — score alignment, detect drift, fill gaps

Install
npx -y skills add paulgrape/skill-auditor --skill website-resilience

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Graceful-failure essentials for a website — custom error pages with correct status codes, 503 maintenance pages, graceful degradation without JavaScript, web app manifest, and uptime monitoring. Use when building error pages, offline behaviour, or resilience of a site.

SKILL.md

1.2 KB, 187 tokens by cl100k_base, as published. Nobody here has run it

Website resilience

Graceful failure — error pages, offline, redirects. Curated from the Website Specification — Resilience (CC BY 4.0).

Required

  • Custom error pages (404, 500) that return the correct HTTP status, explain what went wrong in plain language, and offer a way forward without leaking implementation details.

Recommended

  • Maintenance pages return HTTP 503 with a Retry-After header.
  • Graceful degradation: core content and primary navigation keep working when JavaScript fails.
  • Web app manifest (manifest.json) declaring name, icons, start URL, theme colour, display mode.
  • Monitor uptime from outside your own infrastructure; run a status page on a separate host.

Optional

  • Service worker serving a cached offline fallback page.

Full item list and rationale: https://specification.website/checklist/

Gives 0 of the 12 instructions most monitoring observability skills give in 187 tokens

Counted across 481 of the 483 authors here whose files we hold, read 2026-08-06

  • link every alert to a runbookin 43 of 481, across 35 files
  • use structured json loggingin 36 of 481, across 31 files
  • alert on user-facing symptomsin 20 of 481, across 15 files
  • emit structured JSON logs with stable event namesin 18 of 481, across 13 files
  • propagate trace context across boundariesin 16 of 481
  • use histograms for latency trackingin 14 of 481, across 9 files
  • use OpenTelemetry for distributed tracingin 13 of 481, across 8 files
  • include a correlation ID on every log linein 13 of 481, across 8 files
  • Define service level objectivesin 10 of 481, across 7 files
  • Call useAzureMonitor before importing other modulesin 9 of 481, across 2 files
  • stop and ask for clarification if inputs are missingin 9 of 481, across 2 files
  • define on-call questions before adding telemetryin 9 of 481, across 4 files

Said here and by no other author read

  • Create custom 404 and 500 error pages
  • Return correct HTTP statuses on error pages
  • Explain errors in plain language
  • Offer a way forward on error pages
  • Provide maintenance pages returning HTTP 503
  • Include a Retry-After header on 503 pages

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.