observal-ops
View traces, spans, metrics, feedback, telemetry health, and agent insight reports, including suggestions that reuse components already in the registry. Use when the user wants to see traces, check metrics, view top items, submit ratings, diagnose telemetry, or discuss how an agent is doing.
npx skills add Observal/Observal --skill observal-ops --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Observal Ops: Observability and Telemetry ## Critical Rules 1. **EXECUTE commands**: run them in your shell. Set timeout to 60 seconds. 2. **Pass `--output json`** on every command for stable, machine-readable output. 3. **When in doubt about a flag, run `<command> --help` first.** --- ## Procedure: Observe ```bash observal ops metrics ITEM_NAME --type agent --output json observal ops metrics ITEM_NAME --type mcp --watch observal ops top --type agent --output json observal ops top --type mcp --output json observal ops traces --limit 20 --output json observal ops traces --platform kiro --days 7 --output json observal ops traces --turn --limit 5 observal ops traces --span --limit 3 observal ops spans TRACE_ID --output json observal ops feedback ITEM_NAME --type mcp --output json ``` --- ## Procedure: Rate Component ```bash observal ops rate MCP_NAME --stars 5 --type mcp --comment 'Worked great' observal ops rate AGENT_NAME --stars 4 --type agent ``` `--stars` (1-5) and `--type` are required. `--comment` is optional. --- ## Procedure: Telemetry Health ```bash observal ops telemetry status observal ops telemetry test ``` `status` is the reliable check: it queries server event counts
- Critical Rules
- Procedure: Observe
- Procedure: Rate Component
- Procedure: Telemetry Health
- Procedure: Agent Insights
- Reuse suggestions: components the registry already has
- When a report suggests nothing to reuse
- Output Contract
observal ops metrics ITEM_NAME --type agent --output json observal ops metrics ITEM_NAME --type mcp --watch observal ops top --type agent --output json observal ops top --type mcp --output json observal ops traces --limit 20 --output json observal ops traces --platform kiro --days 7 --output json observal ops traces --turn --limit 5 observal ops traces --span --limit 3 observal ops spans TRACE_ID --output json observal ops feedback ITEM_NAME --type mcp --output json
What does the observal-ops skill do?
View traces, spans, metrics, feedback, telemetry health, and agent insight reports, including suggestions that reuse components already in the registry. Use when the user wants to see traces, check metrics, view top items, submit ratings, diagnose telemetry, or discuss how an agent is doing.
How do I install it?
Run `npx skills add Observal/Observal --skill observal-ops --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Observal/Observal, a repository with 2,254 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.