Skip to content
Back to skills

Pf Monitor

ASecurity

Phase-2 safety net for a deployed project: sets up free uptime + error monitoring and alerts to the user, and confirms auto-rollback is configured so a bad deploy heals itself. Recommends the Azure-native free stack (App Insights availability + exceptions + Monitor email/push alert), offers Sentry or UptimeRobot, guides the account steps, keeps personal data out of reports, and records the result. Use when the user says /pf-monitor, 'set up monitoring', 'watch the site', 'alert me if it goes ...

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
developmentgoazureapidatabase

Works with

  • cli
  • api

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add singhviplove234/atelier --skill pf-monitor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pf Monitor?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pf Monitor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/singhviplove234-pf-monitor/badge)](https://www.skillsdirectory.com/skills/singhviplove234-pf-monitor)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pf-monitor
description: "Phase-2 safety net for a deployed project: sets up free uptime + error monitoring and alerts to the user, and confirms auto-rollback is configured so a bad deploy heals itself. Recommends the Azure-native free stack (App Insights availability + exceptions + Monitor email/push alert), offers Sentry or UptimeRobot, guides the account steps, keeps personal data out of reports, and records the result. Use when the user says /pf-monitor, 'set up monitoring', 'watch the site', 'alert me if it goes down', 'is it being monitored', or 'add error tracking'. Supports --check and --dry-run. Recommend-only for anything billable."
---

# /pf-monitor <slug> [--check] [--dry-run]

Put eyes on a live product and make a bad deploy heal itself. Read first:
- `${CLAUDE_PLUGIN_ROOT}/references/monitoring.md` (this stage's contract — follow it)
- `${CLAUDE_PLUGIN_ROOT}/references/cost-posture.md` (free-first; a tier is paid only when forced, on a yes)
- `${CLAUDE_PLUGIN_ROOT}/references/state-schema.md`

## 0. Flags
`--check`: report what monitoring / alerts / rollback are currently live for this project and stop. `--dry-run`: print the stack it would set up and the steps; create nothing; stop. **Token-light: on `--check` read only `state-schema.md` to parse state — skip the other references under *Read first* above and load them only on a real monitor run.**

## 1. Gate
Locate the project; read `factory.json`. Require `deploy.live_url` (a deployed site). If empty: "Deploy the site first (`/pf-deploy`) — there's nothing live to monitor yet." and stop. Seat = `pm_lane`.

## 2. Recommend the free stack (per `monitoring.md` A2, with pros & cons)
Present the choice with **pros and cons** (per `monitoring.md` A2 / `recommendations.md`), not the upside alone: **Azure-native (App Insights + Monitor)** *(Recommended — one account, one pane, $0; cons: plainer error traces, Azure-tied)* vs **Sentry + UptimeRobot** *(best-in-class errors + simple uptime, provider-neutral; cons: two more accounts/dashboards/keys)*. State the recommendation in one plain line, offer the alternative with AskUserQuestion, and keep it **minimal** — one stack unless the user asks for more. Never propose a paid tier because it is "better"; paid only when real volume forces it, with the monthly price + a yes.

## 3. Set up (what Claude can, guide the rest)
Per `monitoring.md` A–C:
- Ensure a `/api/health` route exists (returns 200 + app/DB reachability). If the repo lacks one, record it as a one-line task for the next build.
- **App Insights:** via the Azure tools, create/confirm an App Insights resource in the project's resource group (free grant), wire an availability test on `/api/health` (~5 min), confirm exceptions are captured. Its connection string is set as an env var the `/pf-setup` way — Claude pre-fills the name, the user sets the value.
- **Alerts:** create an Azure Monitor action group to the user's email + Azure-app push, with the rules from `monitoring.md` B (down 2+ checks, error-rate spike, p95 past the budget for a sustained window, cert < 14 days). Recommend email + push; SMS only on a yes with the per-message price.
- **PII scrubbing:** confirm the app strips request bodies, tokens and personal records before any error is sent (`monitoring.md` C); for Sentry, the `beforeSend` scrubber is a build task.
- **Sentry / UptimeRobot (if chosen):** open the signup/project page in Chrome, pre-fill the non-secret fields, stop; the user signs up and pastes the DSN/key, stored as an env var by name.

## 3b. Status page (client-facing or paid products)
Per `monitoring.md` F: offer the free public status page of the chosen uptime provider — on a different provider than the app — with AskUserQuestion (Yes / Not needed). On yes: open the provider's status-page setup in Chrome, pre-fill the page name and the monitors, stop; the user creates it. Record the URL as `monitoring.status_page`, and note two one-line tasks for the next build: the footer/error-page link and the `INCIDENT_BANNER` config. Remind the user that incident notices are drafted by Claude and **posted by the user**.

## 4. Verify and record
Fire **one test alert** (a deliberate failing check or a test event) and confirm it reaches the user. Record `factory.json.monitoring` (`uptime`, `errors`, `alerts`, `rollback`, `health_route`) and `log {stage:"monitor", event:"set up <stack>"}`. Report what is live and what is pending anything waiting on the user's signup/secret.

## 5. Auto-rollback
Confirm the deploy target is set for auto-rollback per `monitoring.md` D (last-good artifact kept / Container Apps previous revision; bake window; **app-only** revert; DB migration **flagged, not reverted**). If the target cannot auto-rollback, say so and give the one manual revert command for that target. This is configuration + a note, not a billable resource.

## Never
- Propose or create a paid monitoring tier because it is nicer — free-first, paid only when real volume forces it, with the price + a yes.
- Send any personal data, token or secret into an error report or alert.
- Auto-revert a database migration (flag it for a human); roll back the **app version only**.
- Enter a secret value yourself — the user sets secrets; Claude pre-fills names.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.