Install
$ agentstack add skill-using-system-oddyssey-observability-cli-guides ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Observability CLI Guides
A selection map over the query CLIs of the major observability backends. Pick the observed stack's backend, read its reference file, then follow the linked official docs — the fetched page is the source of truth, not memory. The method is the same everywhere: authenticate, discover what the service emits, then query what you discovered.
Pick the backend
| Backend | CLI | Reference | | --- | --- | --- | | Grafana (local oddyssey stack, self-hosted, Cloud) | gcx | [references/grafana.md](references/grafana.md) | | Datadog | Pup CLI (pup) | [references/datadog.md](references/datadog.md) | | Dynatrace | dtctl (DQL) | [references/dynatrace.md](references/dynatrace.md) | | Azure Monitor (App Insights, Log Analytics) | az (KQL) | [references/azure-monitor.md](references/azure-monitor.md) | | AWS CloudWatch + X-Ray | aws | [references/cloudwatch.md](references/cloudwatch.md) | | Splunk (Enterprise / Cloud Platform, Observability Cloud) | splunk (SPL) | [references/splunk.md](references/splunk.md) |
Each reference covers: setup and authentication, the discovery-then-query commands per signal (metrics, traces, logs, profiles where the backend has them), and Planning notes with the backend's coverage gaps and quirks.
For the local oddyssey stack (the Grafana case), the setup-local-stack skill carries the ready-made gcx context — isolated config and datasource UIDs. gcx is the stack's mandatory query CLI.
Rules
- Recommendations and commands must come from the reference's linked docs,
fetched — never from memory; CLIs move fast.
- Credentials come from the environment or the caller (env vars, secret
stores); never invent, echo, or store them.
- Planning notes are a snapshot (last verified 2026-08); the fetched
official page always overrides them.
- If the stack's backend is not in the table, say so and fall back to the
backend's documented REST API over curl — the discover-then-query method still applies.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: using-system
- Source: using-system/oddyssey
- License: MIT
- Homepage: https://github.com/using-system/oddyssey#readme
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.