Agent Observability Stack: Distributed Tracing, Metrics, and Alerting for Multi-Agent Systems
v1.3.1Agent Observability Stack: Distributed Tracing, Metrics, and Alerting for Multi-Agent Systems. Build a complete observability stack for agent commerce: OpenT...
⭐ 0· 132·0 current·0 all-time
by@mirni
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
The skill's name and description match the SKILL.md: a long educational guide on distributed tracing, metrics, and alerting for multi-agent systems. It claims to include production Python examples and OpenTelemetry integration, which is coherent with an observability guide.
Instruction Scope
The SKILL.md is instruction-only and explicitly states it does not execute code or require credentials, and no instructions or install steps are present in the metadata. However, the guide contains full production examples that will show how to instrument agents and emit telemetry to external endpoints (GreenHelix sandbox). Users should review example code for any instructions that would capture or export sensitive payloads (full request bodies, secrets, PII) before executing in production.
Install Mechanism
No install spec and no code files are present. This lowers risk because nothing is written to disk or automatically installed by the skill.
Credentials
The registry metadata declares no required environment variables or credentials, which aligns with the SKILL.md's claim that the GreenHelix sandbox requires no API key. If you migrate examples to a real backend, credentials will likely be needed — but that is not requested by the skill itself.
Persistence & Privilege
always is false, user-invocable is true, and model invocation is allowed (normal defaults). The skill does not request persistent/higher privileges or modify other skills or system settings.
Assessment
This guide appears coherent and is instruction-only (no installers or required secrets). Before running any example code: 1) inspect the Python examples to ensure they don't collect or send entire request payloads, authentication tokens, or other sensitive data to external telemetry endpoints; 2) confirm the GreenHelix sandbox behavior (the guide claims no API key is required) and whether you need credentials for production; 3) sanitize traces/metrics to avoid leaking PII; and 4) run examples in an isolated test environment (sandbox) before deploying to production. If you see examples that read environment variables like API_KEY, TOKEN, SECRET, or that send data to unknown endpoints, treat those as red flags and ask the author for clarification.Like a lobster shell, security has layers — review code before you run it.
ai-agentvk97fw5sq1hbq0ts9pk1ezxj01h84xr64greenhelixvk97fw5sq1hbq0ts9pk1ezxj01h84xr64guidevk97fw5sq1hbq0ts9pk1ezxj01h84xr64latestvk97fw5sq1hbq0ts9pk1ezxj01h84xr64metricsvk97fw5sq1hbq0ts9pk1ezxj01h84xr64monitoringvk97fw5sq1hbq0ts9pk1ezxj01h84xr64observabilityvk97fw5sq1hbq0ts9pk1ezxj01h84xr64openclawvk97fw5sq1hbq0ts9pk1ezxj01h84xr64opentelemetryvk97fw5sq1hbq0ts9pk1ezxj01h84xr64tracingvk97fw5sq1hbq0ts9pk1ezxj01h84xr64
License
MIT-0
Free to use, modify, and redistribute. No attribution required.