agentleFS
Sign inStart free
gclmgclm/super-stack/skills/planning/observability-design/SKILL.md

observability-design

Skill0 starsChanged 7 months agoMITView on GitHub

Design logs, metrics, traces, alerts, and debugging signals so systems can be operated and diagnosed before incidents expose blind spots.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    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
  1. Distinctive:

    Use this skill when a feature, service, background job, or integration needs better operational visibility before shipping or during a …

    line 8
  2. Distinctive:

    avoid noisy telemetry that is expensive but not actionable

    line 21
  3. Distinctive:

    ensure debugging evidence exists before production pressure hits

    line 22
  4. Distinctive:

    Check cardinality, privacy, and cost constraints.

    line 33

“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.

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

Observability Design

Use this skill when a feature, service, background job, or integration needs better operational visibility before shipping or during a reliability improvement pass.

Read First

  • current logs, metrics, traces, dashboards, or alerting setup
  • the flows or failure modes that matter most
  • on-call, debugging, and incident response expectations
  • docs/reference/requirements.md and harness/state.md if they exist
  • harness/history.md if it exists

Goals

  • make important system behavior visible
  • tie signals to real failure modes and operator questions
  • avoid noisy telemetry that is expensive but not actionable
  • ensure debugging evidence exists before production pressure hits

Steps

  1. Define the operator questions the system must answer.
  2. Identify the key flows and failure modes.
  3. Map signals to those flows:
    • structured logs
    • metrics
    • traces
    • events
  4. Check cardinality, privacy, and cost constraints.
  5. Define alerting only where an operator can take action.
  6. Recommend the smallest useful observability set with trade-offs.

Output

Report:

  • target flows and failure modes
  • recommended logs, metrics, and traces
  • alerting guidance
  • privacy or cost constraints
  • gaps in current visibility
  • recommendation

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.

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.

Check your setup, free