Skip to content
Agentmart
Submit a tool

design-observability

Design monitoring, distributed tracing, log aggregation, and alerting.

Skill by wfukatsu

IndexedMIT★ 13
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/wfukatsu-design-observability

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Design monitoring, distributed tracing, log aggregation, and alerting.

Use cases: design

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/design-observability

What's inside

Skill name
design-observability
Description
Design monitoring, distributed tracing, log aggregation, and alerting.
License
MIT
Instructions
35 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • name: missing

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Observability Design

Shared files: a path written `@rules/…`, `@skills/…`, `@templates/…` or `@docs/…` is relative to the
plugin root, `${CLAUDE_PLUGIN_ROOT}` — not to the project being worked on. Read it from there.

## Desired Outcome

- SLI/SLO definitions (per service, linked to business KPIs)
- Distributed tracing design (OpenTelemetry, correlation ID propagation)
- Log aggregation strategy (structured logging, centralized management)
- Metrics design (RED/USE methods)
- Alerting design (thresholds, escalation, dashboards)
- ScalarDB-specific metrics (transaction success rate, OCC conflict rate). On ScalarDB Cluster
  3.19+, prefer its native **OpenTelemetry support** over a bespoke exporter; verify availability
  against the project's pinned release and edition per @rules/okf-knowledge-bundle.md. When
  ScalarDB Saga is in the architecture, add saga-level signals — sagas by status, `ESCALATED` count
  (an operator queue, not a transient error), compensation failure rate — per
  @rules/scalardb-saga-patterns.md

## Output

Write all reports in the language configured in `work/pipeline-progress.json` (`options.output_language`).

| File | Content |
|------|---------|
| `reports/08_infrastructure/observability-design.md` | Overall observability design |

## Related Skills

| Skill | Relationship |
|-------|-------------|
| /architect:design-infrastructure | Related |
| /architect:review-operations | Referenced during review |

From wfukatsu/nexus-architect, MIT.

More from wfukatsu/nexus-architect

Signals

Stars
13
Forks
1
Open issues
0
Last commit (this folder)
Oct 8, 2026 (22 days ago)
Last release
Oct 9, 2026 (21 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/wfukatsu/nexus-architect
Website
nexus-architect-docs-070772.gitlab.io/
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from wfukatsu

Cite this page

design-observability skill. Agent Mart. https://agentmart.dev/skills/wfukatsu-design-observability (last updated 2026-10-24)