Menu

Individual skill

observability-design

0upvotes

Making multi-agent workflows visible and debuggable for designers and developers.

gemini-extension/design-agent-orchestration/skills/observability-design/SKILL.md

Read pinned source

Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
202
Repository last updated
Jun 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Observability Design
You can't improve what you can't see. Observability design makes the internal workings of multi-agent systems visible — so designers can understand user experience problems, developers can debug failures, and teams can improve the system over time.
## What to Make Observable
- **Workflow execution**: Which agents were involved, in what order, with what results
- **Decision points**: What decisions were made, what alternatives were considered, why one was chosen
- **Handoff details**: What context transferred between agents, was anything lost
- **Timing**: How long each agent took, where bottlenecks occur
- **Failures**: What failed, how it was recovered, what the user experienced
- **Quality signals**: Output quality scores, user satisfaction signals, task success markers
## Observability for Different Audiences
**For designers:**
- User journey view: What did the user experience across the whole workflow?
- Pain point identification: Where did users struggle, abandon, or express frustration?
- Quality patterns: Which outputs are high and low quality, and why?
**For developers:**
Back to top