Skip to content
Get packs

Error Monitoring Setup

Guides an agent to set up, check and review production error monitoring for a web app

Source Download skill
Repository
thedaviddias/Front-End-Checklist
Stars
74,632
Licence
MIT
Files
2 files

What it does

When installed, the agent can check whether a web project has production error monitoring (such as Sentry, Datadog or Bugsnag) capturing crashes, unhandled promise rejections, framework errors, failed network requests and Core Web Vitals. It can also help integrate an SDK, tag events with release and environment, set alert thresholds, and review monitoring code for patterns that hide errors. The skill is a written checklist and guidance; the files shown contain no executable scripts.

Great for

  • Developers launching a new production web app who want error visibility from day one
  • Teams reviewing incident response readiness or investigating why errors go unnoticed
  • Front-end engineers auditing existing monitoring initialisation code

Skip it if

  • Projects that only need local debugging, since this targets production observability and adds setup work
  • Anyone expecting the agent to pick a vendor or manage accounts for them, because the skill does not handle account creation or billing; adding a third-party SDK also sends error data, possibly including user context, to an outside service that should be reviewed for privacy compliance

Try asking

  • “Set up error monitoring for my new React app and tag events with release and environment”
  • “Review my monitoring init code and flag missing user context or swallowed errors”
  • “Check whether my production site captures unhandled promise rejections and failed network requests”
  • “Help me configure alerts so critical errors page the on-call team”
Step-by-step guide: how to use Error Monitoring SetupInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    error-monitoring.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip error-monitoring.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip error-monitoring.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the agent your framework and monitoring vendor up front so it can follow the right references/rule.md examples
  • Keep API keys and DSNs out of the code it writes; load them from environment variables or a secrets manager
  • Review any SDK changes before deploying, especially filters that drop events

What's inside

  • references/rule.md
  • SKILL.md

Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.