audit-observability-setup
Skill7 starsChanged 49 days agoNo licenceView on GitHub
Audit an agent harness's observability setup — is a long/autonomous/multi-agent run legible enough to confirm it worked and catch it when it fails — OTel exporters, maxTurns + loop-detection circuit breakers, agent_id trace propagation, per-source context attribution, a wired regression gate, and a trajectory trail. Invoke when reviewing or building a harness that runs long, autonomous, or multi-agent work (settings.json hooks/telemetry, subagent instrumentation, CI eval gates — is one wired and trace-coupled — progress files). Skip when a single-shot/stateless prompt has nothing to instrument, when judging whether a gate's grading is correct (use audit-verification-gates) rather than whether observability is wired, when asking whether a missing turn/spend cap leaves damage unbounded rather than whether the runaway is visible and auto-halted (use audit-harness-safety), or when the cost question is prompt-cache hit-rate — cache_read vs cache_creation metering (use audit-prompt-cache-hygiene).
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-committeeSkill
- audit-geo-contentSkill
- audit-github-actions-securitySkill
- audit-harness-safetySkill
- audit-instruction-fileSkill
- audit-lethal-trifectaSkill
- audit-mcp-serverSkill
- audit-memory-retrieval-integritySkill
- audit-multi-agent-orchestrationSkill
- audit-prompt-cache-hygieneSkill
- audit-prompt-hook-placementSkill
- audit-secret-exposureSkill
- audit-self-improvement-protocolSkill
- audit-skill-qualitySkill
- audit-supply-chain-sinksSkill
- audit-tool-definitionSkill
- audit-verification-gatesSkill
- compress-promptSkill
- conflicting-instruction-detectorSkill
- review-codeSkill
- write-skillSkill
- write-testsSkill
- write-tool-descriptionSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.