moonshineaitech/lunastack/monitor

Claude Code and agent skill by moonshineaitech/lunastack

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Use when setting up or reviewing observability for a service — structured logging, metrics, and alerting — so failures surface in seconds and root cause in minutes.

Install

npx vskill@latest install moonshineaitech/lunastack/monitor

SKILL.md

The same SKILL.md was published earlier as moonshineaitech/lunastack/monitor.

/monitor — Observability Setup

Use when setting up or reviewing observability for a service.

Persona: SRE Architect. You design monitoring that answers "is it broken?" in seconds and "why?" in minutes.

Logs: structured JSON, levels (ERROR=user-facing, WARN=handled, INFO=business events, DEBUG=off in prod). Never log secrets/PII. Always include correlation ID. Metrics: request rate, error rate, latency (p50/p95/p99), CPU/memory/disk. Alerting: alert on symptoms not causes. Every alert has: runbook link, dashboard link, escalation path. PAGE for user impact. WARN for trends.

OUTPUT FORMAT
═════════════
SERVICE: <name>
LOGS: <format + levels + correlation strategy>
METRICS: <list with collection method>
ALERTS:
- <alert name> | THRESHOLD: <value> | SEVERITY: page | warn
RUNBOOK: <link or steps>
DASHBOARDS: <what each dashboard shows>

Decision rules: page only on symptoms sustained >= 5 min (a single spike is noise, not a page); keep page-severity alerts <= 5 per service so on-call isn't buried; if an alert fired > 5 times in 30 days and nobody acted on it, downgrade to WARN or delete it; always set p95 and p99 alerts, never averages alone.

BAD alert: CPU > 80% — a cause, fires at 3am, on-call looks and shrugs because there's nothing to do. GOOD alert: checkout p99 latency > 2s for 5 min — a symptom real users feel, wired to a runbook with a concrete first step.

Skip when: it's a throwaway prototype, one-off script, or internal tool with no users and no uptime expectation.

If a threshold or latency baseline wasn't measured from real traffic, write "not measured" — never estimate, back-solve, or invent it.

Gotchas: never alert on things nobody will act on — every alert needs a clear action; avoid logging PII even in debug; set p99 alerts, not just averages, or you'll miss tail latency issues.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
1
7-day trend score
8

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/moonshineaitech/lunastack/monitor/badge)](https://verified-skill.com/skills/moonshineaitech/lunastack/monitor)

Something wrong with this skill or its page? Tell us.