agentleFS
Sign inStart free
tonmoy007tonmoy007/forge-plugins/skills/forge-monitor/SKILL.md

forge-monitor

Skill2 starsChanged 5 months agoMITView on GitHub

Run Stage 9 of the Forge pipeline — observability and monitoring. Use when

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If it exits non-zero, STOP: present its message verbatim and do not proceed — the prior stage must be completed first (or use …

    line 26
  2. Very specific:

    Read pipeline/state.md — confirm Forge project.

    line 30
  3. Distinctive:

    If stage > 9, ask if the user wants to update the health report.

    line 32
  4. Very specific:

    Read agents/observer.md to load the Observer persona.

    line 37
  5. Very specific:

    Read pipeline/08-deploy/deploy-plan.md and pipeline/01-srs/srs.md NFR section.

    line 39
  6. Distinctive:

    Follow the Observer workflow: derive SLIs/SLOs from NFRs, check available signals, assess health.

    line 40
  7. Very specific:

    Write pipeline/09-monitor/observability.md and pipeline/09-monitor/health-report.md.

    line 41
  8. Very specific:

    Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py advance --to 9 to mark Stage 9 active.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/forge:monitor — Monitoring & Observability

When to Use

  • User says /forge:monitor
  • User wants to set up observability, define SLOs, check system health, or review metrics
  • Working in a Forge project at Stage 8 or 9

Pre-flight Check

Entry gate (REQ-GATE-ENTRY-001) — before adopting the persona, verify the prior stage's artifact exists:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py preflight --stage 9

If it exits non-zero, STOP: present its message verbatim and do not proceed — the prior stage must be completed first (or use /forge:force-advance to skip intentionally).

  1. Read pipeline/state.md — confirm Forge project.
  2. Confirm pipeline/08-deploy/deploy-plan.md exists (or package-spec.md for CLI/library projects). If neither: "Complete Stage 8 first (/forge:deploy)."
  3. If stage > 9, ask if the user wants to update the health report.
  4. Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 9 to load project-type overrides. If the profile sets skip: true (library), skip this stage and report that monitoring is N/A for the project type. Otherwise, treat each additional_criteria (e.g., API: 4xx/5xx alerts, p99 latency; ML: model drift, data quality, inference latency) as required SLI/SLO/alert entries.

Steps

  1. Read agents/observer.md to load the Observer persona.
  2. Adopt that persona — you are now the Observer.
  3. Read pipeline/08-deploy/deploy-plan.md and pipeline/01-srs/srs.md NFR section.
  4. Follow the Observer workflow: derive SLIs/SLOs from NFRs, check available signals, assess health. Add every profile criterion as a tracked signal with threshold and alert.
  5. Write pipeline/09-monitor/observability.md and pipeline/09-monitor/health-report.md.
  6. Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py advance --to 9 to mark Stage 9 active.

Verification

After running, confirm:

  • pipeline/09-monitor/observability.md exists with SLIs, SLOs, and alert thresholds
  • pipeline/09-monitor/health-report.md exists with current status
  • pipeline/state.md shows current_stage: 9

Next Step

Derive the hint from the canonical stage table — never hardcode it (REQ-NEXTHINT-001, single source of truth). Run the helper and present its output to the user verbatim:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py next-hint --stage 9

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free