How do I install the Review Agent Observability skill?

Run npx skillmds@latest add diagrid-labs/review-agent-observability in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review Agent Observability safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review Agent Observability?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review Agent Observability free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review Agent Observability?

diagrid-labs (@diagrid-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review Agent Observability by diagrid-labs

Name: Review Agent Observability
Rating: 4.2 (5 reviews)
Author: diagrid-labs

Review Agent Observability

This skill reviews agent projects for observability completeness — tracing, metrics, structured logging, and trace propagation. Use this skill when the user asks to "review agent observability", "audit agent tracing", "check agent metrics", or similar.

diagrid-labs Updated Sep 10, 2026

File contents

Review Agents — Observability

Overview

Scans native dapr-agents projects for observability completeness: Dapr tracing Configuration present, sampling rate non-zero, structured logging in use, explicit log level, trace-id propagation on outbound tool calls, and README guidance for trace / metrics UIs. Framework-wrapper projects (LangGraph / CrewAI / OpenAI Agents / etc.) receive a single info finding — those frameworks ship their own observability pipelines.

Execution Order

You MUST follow these phases in strict order.

Resolve scope — Read ../shared/review-scope-prompt.md and follow it to set scope_root.
Detect target — Read ../shared/review-detect-target-agent.md. If flavor == framework-wrapper, emit one info finding explaining that observability is delegated to the wrapped framework and stop.
Load checklist — Based on language, read exactly one of:
- python → ../shared/review-agent-observability-python.md
- dotnet → ../shared/review-agent-observability-dotnet.md (stub — emits a single DAG-OBS-000 info finding)
Scan — Apply every rule. dapr.yaml, resources/tracing.yaml, tool file contents, and README.md are all potentially in scope.
Report — Format findings using ../shared/review-report-format.md.
Show final message — Emit the report from step 5 with a ## Next steps block.

Prerequisites

Read access to the project directory.

Allowed tools

Read, Grep, Glob only.

Rules

Python rules — DAG-OBS-001 … DAG-OBS-008
.NET rules — DAG-OBS-000 (stub; full checklist TBD)

Show final message

The last thing you emit MUST be the report from step 5. ## Next steps should suggest:

Run review-agent-tools, review-agent-memory, and review-agent-orchestration if not yet run.
Re-run this skill after fixing critical findings.
Optionally run the observability stack locally (docker compose -f docker-compose.observability.yaml up -d) and verify traces appear in Zipkin.

Do not add any text after the report.

---name: review-agent-observabilitydescription: This skill reviews agent projects for observability completeness — tracing, metrics, structured logging, and trace propagation. Use this skill when the user asks to "review agent observability", "audit agent tracing", "check agent metrics", or similar.---# Review Agents — Observability## OverviewScans native `dapr-agents` projects for observability completeness: Dapr tracing Configuration present, sampling rate non-zero, structured logging in use, explicit log level, trace-id propagation on outbound tool calls, and README guidance for trace / metrics UIs. Framework-wrapper projects (LangGraph / CrewAI / OpenAI Agents / etc.) receive a single `info` finding — those frameworks ship their own observability pipelines.## Execution OrderYou MUST follow these phases in strict order.1. **Resolve scope** — Read [`../shared/review-scope-prompt.md`](../shared/review-scope-prompt.md) and follow it to set `scope_root`.2. **Detect target** — Read [`../shared/review-detect-target-agent.md`](../shared/review-detect-target-agent.md). If `flavor == framework-wrapper`, emit one `info` finding explaining that observability is delegated to the wrapped framework and stop.3. **Load checklist** — Based on `language`, read exactly one of: - `python` → [`../shared/review-agent-observability-python.md`](../shared/review-agent-observability-python.md) - `dotnet` → [`../shared/review-agent-observability-dotnet.md`](../shared/review-agent-observability-dotnet.md) (stub — emits a single `DAG-OBS-000` info finding)4. **Scan** — Apply every rule. `dapr.yaml`, `resources/tracing.yaml`, tool file contents, and `README.md` are all potentially in scope.5. **Report** — Format findings using [`../shared/review-report-format.md`](../shared/review-report-format.md).6. **Show final message** — Emit the report from step 5 with a `## Next steps` block.## Prerequisites- Read access to the project directory.## Allowed tools`Read`, `Grep`, `Glob` only.## Rules- [Python rules](../shared/review-agent-observability-python.md) — `DAG-OBS-001` … `DAG-OBS-008`- [.NET rules](../shared/review-agent-observability-dotnet.md) — `DAG-OBS-000` (stub; full checklist TBD)## Show final messageThe last thing you emit MUST be the report from step 5. `## Next steps` should suggest:- Run `review-agent-tools`, `review-agent-memory`, and `review-agent-orchestration` if not yet run.- Re-run this skill after fixing critical findings.- Optionally run the observability stack locally (`docker compose -f docker-compose.observability.yaml up -d`) and verify traces appear in Zipkin.Do not add any text after the report.

Frequently asked questions