skill-sukirman1901-frontend-expert-monitoring · by Install
$ agentstack add skill-sukirman1901-frontend-expert-monitoring ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sukirman1901-frontend-expert-monitoring) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 (
ui-feel//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 fe-devtools for local audits; this skill for shipped signal.
Workflow
- Errors — boundary + reporting; scrub PII
- Performance — sample traces; watch LCP/INP/CLS on key routes
- Analytics — few high-value events, not every click
- 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
- [ ] Error boundary on app shell / critical routes
- [ ] DSN/env via env vars — not hardcoded secrets in git
- [ ] Sample rates sane for traffic
- [ ] No PII in events by default
- [ ] Alerts have an owner
- [ ] Key product events listed (not clickstream noise)
Depth
Full guide: references/monitoring.md. Related: web-performance for build-time CWV; fe-devtools for lab audits.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sukirman1901
- Source: sukirman1901/frontend-expert
- License: MIT
- Homepage: https://github.com/sukirman1901/frontend-expert
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.