AI Agent Observability
v1.1.0Evaluate and monitor AI agent fleets across six key dimensions to score health, identify issues, and optimize performance for ops teams managing 1-100+ agents.
⭐ 0· 544·0 current·0 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name and description claim fleet observability, and the content is a plausible checklist and prompt for that purpose. However, the skill is purely instruction-only (no code, no declared integrations, no env vars), so it cannot actually perform automated monitoring by itself — it can only guide an agent or human to perform the assessment. The claim to 'Run the agent observability assessment against our current deployment' is disproportionate to what's provided (no connectors, no credentials, no CLI/API guidance).
Instruction Scope
SKILL.md contains open-ended runtime prompts that ask the agent to evaluate the 'current deployment' and to gather counts, spend, alerts, and recent failures. The instructions do not confine how the agent should obtain that information (no explicit APIs/paths to query, no declared env vars). That vagueness grants broad discretion — an autonomous agent could attempt to read environment variables, query cloud APIs, inspect files, or contact external endpoints to satisfy the prompt, which is scope creep relative to the simple documentation/assessment intent.
Install Mechanism
No install spec and no code files — lowest-risk install footprint. Nothing will be written to disk by the skill itself because there is no install step.
Credentials
The skill declares no required environment variables, credentials, or config paths, which is consistent with an instruction-only checklist. However, the assessment questions (monthly spend, monitoring existence, alerting targets) typically require privileged access to billing, monitoring, or deployment APIs; those are not declared, creating an implicit gap. If an agent pursues answers programmatically, it may request credentials later — the skill does not justify or constrain that need.
Persistence & Privilege
always is false and there are no persistence or system-modifying instructions. Autonomous invocation is allowed (platform default) but the skill does not request elevated or persistent privileges itself.
What to consider before installing
This skill is essentially a checklist and a prompt template rather than a connector or monitoring tool. Before installing or invoking it, consider: 1) It will not automatically collect metrics — if you ask an autonomous agent to 'run the assessment' it may try to gather data from your environment; restrict that agent's permissions (least privilege) and network access. 2) Prefer using it as a human-facing guide or with a sandboxed agent that only has read-only, narrowly scoped access to specific monitoring/billing APIs you explicitly provision. 3) If you intend automated collection, define exactly which APIs/endpoints the agent may call and supply dedicated read-only credentials; update the SKILL.md to list required env vars and safe query patterns. 4) If you have sensitive billing or production telemetry, require human approval for any actions that access those systems. These steps will reduce the risk that an ambiguous prompt leads to unintended access or data exposure.Like a lobster shell, security has layers — review code before you run it.
agentsvk977nx0gwy66qajrcy92j6pr5h81nw5tlatestvk977nx0gwy66qajrcy92j6pr5h81nw5tmonitoringvk977nx0gwy66qajrcy92j6pr5h81nw5tobservabilityvk977nx0gwy66qajrcy92j6pr5h81nw5topsvk977nx0gwy66qajrcy92j6pr5h81nw5tproductionvk97de692ef7ezp2ej68rtf59kh81ntq2srevk97de692ef7ezp2ej68rtf59kh81ntq2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.