monitoring-setup
Skill2 starsChanged 8 months agoMITView on GitHub
Configures application monitoring, log collection, and alerting. Generates setup for Datadog, Grafana+Prometheus, CloudWatch, and Sentry with startup-appropriate thresholds.
- Reads credentials
- Installs packages
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 131
Create health check endpoints
- Distinctive: line 134
Create cloud provider accounts
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Monitoring Setup - Observability Configuration
Overview
Sets up the "detect before users complain" system. Minimum viable monitoring that grows with your startup.
1. When to Apply
| Trigger | Behavior |
| Post-launch monitoring setup | Full observability stack |
| "monitoring", "alerting" | Tool-specific configuration |
| First production incident | Retroactive monitoring gaps |
2. Monitoring Stack by Budget
| Budget | Stack | Monthly Cost |
| $0 | Sentry (free) + UptimeRobot + CloudWatch basic | $0 |
| $0-50 | Sentry + Grafana Cloud (free) + Better Uptime | $0-50 |
| $50-500 | Datadog (Pro) or Grafana Cloud (Pro) | $50-500 |
3. Essential Alerts (Day 1)
## Must-Have Alerts
| Alert | Condition | Channel | Priority |
|-------|-----------|---------|----------|
| **Site Down** | Health check fails 3x | Slack + PagerDuty | P0 |
| **Error Rate Spike** | >5% 5xx in 5 min | Slack | P1 |
| **Slow Response** | p95 > 2s for 5 min | Slack | P2 |
| **DB Connections** | >80% pool used | Slack | P1 |
| **Disk Space** | >85% used | Slack | P2 |
| **Memory** | >90% for 10 min | Slack | P1 |
| **SSL Expiry** | <14 days to expiry | Email | P2 |4. Quick Setup: Sentry (Error Tracking)
// Next.js — sentry.client.config.ts
import * as Sentry from "@sentry/nextjs"
Sentry.init({
dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
tracesSampleRate: 0.1, // 10% of transactions
replaysSessionSampleRate: 0, // Save cost, enable when needed
environment: process.env.NODE_ENV,
})# FastAPI — main.py
import sentry_sdk
from sentry_sdk.integrations.fastapi import FastApiIntegration
sentry_sdk.init(
dsn=os.getenv("SENTRY_DSN"),
traces_sample_rate=0.1,
environment=os.getenv("ENVIRONMENT", "production"),
integrations=[FastApiIntegration()],
)5. Health Check Endpoint
// app/api/health/route.ts
export async function GET() {
const checks = {
status: 'ok',
timestamp: new Date().toISOString(),
uptime: process.uptime(),
checks: {
database: await checkDB(),
redis: await checkRedis(),
}
}
const allHealthy = Object.values(checks.checks).every(c => c === 'ok')
return Response.json(checks, { status: allHealthy ? 200 : 503 })
}6. Tool Coordination
| Tool | Purpose |
| Write | Generate config files, health endpoints |
| Read | Analyze existing monitoring setup |
| Bash | Install SDKs (npm install @sentry/nextjs) |
7. Boundaries
Will:
- Generate monitoring configurations for major platforms
- Set up error tracking (Sentry), uptime monitoring, basic APM
- Define alert thresholds appropriate for startups
- Create health check endpoints
Will Not:
- Create cloud provider accounts
- Set up PagerDuty/OpsGenie on-call rotations
- Build custom dashboards (recommend tools instead)
- Monitor business metrics (use metrics-tracker)
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- hieutrtr/ai1-skills★ 8same name
- The-Utopia-Studio/skills★ 6same name
- xcrrr/claude-skills★ 6same name
- accolver/skill-maker★ 4same name
- vijaysuperpositionist/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- brand-voiceSkill
- community-builderSkill
- email-sequenceSkill
- growth-experimentSkill
- landing-page-genSkill
- pitch-deckSkill
- referral-programSkill
- budget-plannerSkill
- fundraising-prepSkill
- legal-checklistSkill
- meeting-notesSkill
- okr-builderSkill
- postmortem-writerSkill
- retrospective-guideSkill
- risk-registerSkill
- sop-writerSkill
- experiment-designerSkill
- metrics-trackerSkill
- prd-writerSkill
- scope-cutterSkill
- user-interview-guideSkill
- ai-integrationSkill
- api-first-designSkill
- db-schema-designerSkill
- deploy-pipelineSkill
- infra-as-codeSkill
- mvp-scaffoldSkill
- test-generatorSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

