agentleFS
metacircu1armetacircu1ar/hive_skills/skills/audit/audit-resilience-and-observability/SKILL.md

audit-resilience-and-observability

Skill4 starsChanged 2 months agoMITView on GitHub

Audit web applications for production resilience and debugging readiness. Use when reviewing UI error boundaries, request handlers, external IO, background jobs, health checks, logging, incident diagnostics, database backups, or launch readiness for operational failure modes.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check whether the app can fail gracefully, recover predictably, and produce enough evidence to debug production incidents.

    line 8
  2. Distinctive:

    Verify error boundaries or equivalent app-level crash handlers wrap UI roots and major route boundaries.

    line 13
  3. Distinctive:

    Check timeouts, retries, idempotency, and duplicate-event handling around external services.

    line 18
  4. Distinctive:

    Verify a health endpoint exists.

    line 20
  5. Distinctive:

    Check that production logs include request IDs, user/account IDs where safe, route/action names, error classes, provider event IDs, and job …

    line 24
  6. Distinctive:

    Check that failures in background jobs and webhooks are observable.

    line 26
  7. Distinctive:

    Look for documented database backup strategy, retention, and restore testing.

    line 28
  8. Very specific:

    Search for resilience terms such as ErrorBoundary, error boundary, try, catch, timeout, retry, queue, job, worker, email, webhook, health, …

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit Resilience And Observability

Check whether the app can fail gracefully, recover predictably, and produce enough evidence to debug production incidents.

Workflow

  1. UI crash containment:
    • Verify error boundaries or equivalent app-level crash handlers wrap UI roots and major route boundaries.
    • Confirm users see recoverable states rather than a blank screen.
  2. Request-path resilience:
    • Find synchronous email, SMS, webhook calls, AI calls, payment calls, or other external IO inside request handlers.
    • Recommend queueing or async jobs for slow or failure-prone operations where user response does not require completion.
    • Check timeouts, retries, idempotency, and duplicate-event handling around external services.
  3. Health checks:
    • Verify a health endpoint exists.
    • Confirm it checks real dependencies needed to serve traffic, such as database, cache, queue, storage, and required external APIs where appropriate.
    • Distinguish shallow liveness from deeper readiness.
  4. Logging and incident debugging:
    • Check that production logs include request IDs, user/account IDs where safe, route/action names, error classes, provider event IDs, and job IDs.
    • Confirm sensitive values are redacted.
    • Check that failures in background jobs and webhooks are observable.
  5. Backup and restore:
    • Look for documented database backup strategy, retention, and restore testing.
    • Flag apps that only mention backups without a restore verification path.

Useful Searches

Search for resilience terms such as ErrorBoundary, error boundary, try, catch, timeout, retry, queue, job, worker, email, webhook, health, ready, live, logger, request_id, trace, Sentry, Bugsnag, backup, and restore.

Output

Produce sections for:

  • UI crash handling.
  • External IO and queueing.
  • Health checks.
  • Logging and tracing.
  • Backups and restore.

Each finding needs file and line or documentation path, operational impact, suggested fix, and a verification step. Prioritize issues that would cause data loss, long outages, duplicate charges/emails, or impossible incident diagnosis.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.