agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/spec-observability/SKILL.md

spec-observability

Skill0 starsChanged 16 days agoMITView on GitHub

Specify logs, metrics, or traces for a named failure mode using systems this program already has. Use when the user asks for an observability spec, instrumentation for ops, or /spec-observability. Do not invent dashboards or SLOs.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not invent dashboards, vendors, or SLOs.

    line 19
  2. Very specific:

    If there is no observability system in context, write unknown and stop for a human.

    line 34
  3. Very specific:

    Read AGENTS.md if present.

    line 43

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

Spec observability

Say what we will see when this fails. This is not write-nfr, not write-runbook, and not spec-analytics (product events).

Do not invent dashboards, vendors, or SLOs.

Is this the right skill?

SignalDo this instead
Product analytics eventsspec-analytics
Diagnose / mitigate stepswrite-runbook
Numeric targetswrite-nfr

Required inputs

  • A named failure mode (design, runbook, or incident)
  • context/systems-of-record.md (observability row)

If there is no observability system in context, write unknown and stop for a human. Do not pick a vendor.

Human decisions (do not invent)

  • New dashboard or vendor
  • Page thresholds

Procedure

  1. Read AGENTS.md if present. Read context/systems-of-record.md and the runbook/design.
  2. Find the home: docs/ops/observability-<slug>.md.
  3. Open references/observability-template.md. Copy every heading. Write n/a when unused.
  4. Each signal: kind (log / metric / trace), name if it already exists, when it fires, how it shows up in the existing system — or unknown.
  5. Point the runbook at this file.

Output

  • Path: docs/ops/observability-<slug>.md
  • Template: references/observability-template.md

Quality bar

  • Failure mode is named
  • Signals use the existing observability system or unknown
  • No invented SLO or vendor
  • Unused headings are n/a

Done

  1. Path
  2. Signal count + unknown count
  3. Next skill: write-runbook (link symptoms here) or implement-change

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