Monitoring
Frontend observability — Sentry error tracking, CWV/performance monitoring, analytics, OpenTelemetry, alerting. Use when adding error boundaries, tracking production bugs, measuring LCP/INP, wiring analytics, or ops asks about monitoring/observability for a web UI — not for visual design polish.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill monitoringgit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/monitoring ~/.claude/skills/monitoringPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Monitoring ## Overview Ship UI with enough production signal: errors, performance, and product analytics — without boiling the ocean. ## When to use - Add/fix Sentry (or similar) + error boundaries - Performance monitoring / CWV in production - Analytics events for key UI flows - Alerting on error spikes or CWV regressions ## When to skip - Pure visual polish (`polish` / `/polish`) - Local-only prototypes with no deploy target ## MUST (when adding observability) | Signal | Minimum | |--------|---------| | **Errors** | Boundary on app shell / critical routes + reporting; scrub PII | | **Secrets** | DSN / keys via env — never commit | | **Sample rates** | Sane defaults for traffic (don’t 100% trace huge apps blindly) | | **Analytics** | Few high-value events (signup, checkout, critical CTA) — not every click | | **Alerts** | Error rate or CWV budget with a named owner | Lab Lighthouse ≠ production monitoring — use `devtools` for local audits; this skill for **shipped** signal. ## Workflow 1. **Errors** — boundary + reporting; scrub PII 2. **Performance** — sample traces; watch LCP/INP/CLS on key routes 3. **Analytics** — few high-value events, not every click 4. **Alert** — error rate / CWV budgets that someone will actually see ## Agent boundaries - **May decide:** Vendor (Sentry vs other), which 3–5 analytics events matter - **Must not:** Hardcode DSNs; log emails/tokens; add analytics spam on every hover ## Checklist
Details
- Skill name
monitoring- Repository
- sukirman1901/frontend-expert
- Path
skills/monitoring/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Monitoring skill do?
Frontend observability — Sentry error tracking, CWV/performance monitoring, analytics, OpenTelemetry, alerting. Use when adding error boundaries, tracking production bugs, measuring LCP/INP, wiring analytics, or ops asks about monitoring/observability for a web UI — not for visual design polish.
How do I install the Monitoring skill?
Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Monitoring popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/frontend-expert
Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Anti Slop Design
9sukirman1901/frontend-expert
Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.
Appdeploy
3AppDeploy-AI/skills
Deploy web apps with backend APIs, database, file storage, AI operations, authentication, realtime, and cron jobs to a public URL. Use when the user asks to deploy, publish, or host a website or web app. No account required. Uses HTTP API via curl.
Contabo
10artguru-tech-team/claude-skills-public
Deploys infrastructure on Contabo using Cloud VPS and Object Storage. Focuses on cost‑effective provisioning and Contabo-specific CLI/API quirks. Use when: provisioning Contabo Cloud VPS, configuring Object Storage, or troubleshooting Contabo-specific issues. Keywords: contabo, cntb, VPS, cloud compute, budget hosting, best value, object storage, infrastructure
Containers
9zllovesuki/cloudflare-agent-skills
Decide when to use Cloudflare Containers instead of Workers and design container-backed workloads, native binaries, long-running processes, image processing, larger runtime shapes, and Worker frontends. Use as an escape hatch when Workers constraints do not fit.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.