agentsclimarketplace

Observability alerting

Skill planifest/planifest-framework/planifest-framework/external-skills/observability-alerting

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill observability-alerting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Observability alerting workflow for signal quality, routing policy, and actionable thresholds. Use when alert rules need design or tuning to detect incidents with clear ownership and noise control; do not use for business-feature implementation logic.

SKILL.md

1.9 KB, 329 tokens by cl100k_base, as published. Nobody here has run it

Observability Alerting

Overview

Use this skill to design alerting that catches real incidents quickly without overwhelming responders.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Alert threshold actionability rules:
    • references/alert-threshold-actionability-rules.md

Templates And Assets

  • Alert catalog template:
    • assets/alert-catalog-template.csv
  • Alert noise review checklist:
    • assets/alert-noise-review-checklist.md

Inputs To Gather

  • Critical user/system failure modes.
  • Available telemetry signals and quality.
  • On-call routing and escalation policy.
  • Historical false-positive/false-negative patterns.

Deliverables

  • Alert catalog with severity, owner, and runbook linkage.
  • Threshold and routing policy.
  • Noise-control and tuning plan.

Workflow

  1. Build initial alert catalog in assets/alert-catalog-template.csv.
  2. Set thresholds using references/alert-threshold-actionability-rules.md.
  3. Define routing/escalation by severity.
  4. Validate with assets/alert-noise-review-checklist.md.
  5. Publish tuning backlog and ownership.

Quality Standard

  • Alerts are actionable and owned.
  • Critical paths have coverage with bounded noise.
  • Paging vs non-paging intent is explicit.

Failure Conditions

  • Stop when alerts are noisy, non-actionable, or ownerless.
  • Stop when critical failure modes lack alert coverage.
  • Escalate when alert quality risks SLO breach response.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.