agent-system-live-quality-ops
Skill2 starsChanged 9 months agoMITView on GitHub
Operate and validate AgentSystem live quality alarm (systemd timer + alert state) to keep memory/proactivity/consistency regressions visible in real time.
In this repository27 other files it gives its agents.
- Agent BrowserSkill
- agent-governanceSkill
- agent-system-learning-loopSkill
- agent-system-memory-proactivity-opsSkill
- agent-system-output-hygiene-opsSkill
- agent-system-stability-opsSkill
- auto-updaterSkill
- deep-researchSkill
- domaindetailsSkill
- hnSkill
- humanizerSkill
- memory-hygieneSkill
- model-usageSkill
- nano-pdfSkill
- news-aggregator-skillSkill
- orchestrator-loopSkill
- prompt-guardSkill
- security-reviewSkill
- self-improvementSkill
- structured-brainstormingSkill
- subagent-executionSkill
- summarizeSkill
- systematic-debuggingSkill
- tavilySkill
- tdd-workflowSkill
- topic-monitorSkill
- verification-gateSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when you need to verify that live quality alerts are active and not silently failing.
- Distinctive: line 30
Verify latest health report and alarm state file exist.
- Distinctive: line 31
Check if alert suppression/cooldown is working as expected.
- Distinctive: line 32
If timer is inactive, enable it and re-run a dry check.
≈ “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.
Files
AgentSystem Live Quality Ops
Use this skill when you need to verify that live quality alerts are active and not silently failing.
Quick Start
- Dry-run alarm logic:
bash /Users/user/clawd/scripts/agent-system-live-quality-alarm.sh --dry-run- Inspect timer + last run:
bash scripts/check_live_alarm.sh- Force a manual alert test (optional):
bash /Users/user/clawd/scripts/agent-system-live-quality-alarm.sh --force-alert --dry-runWorkflow
- Confirm
hachix-agent-system-live-quality-alarm.timeris active. - Verify latest health report and alarm state file exist.
- Check if alert suppression/cooldown is working as expected.
- If timer is inactive, enable it and re-run a dry check.
- Record findings in reports or memory notes.
Resources
scripts/check_live_alarm.sh: one-shot operational status summary./Users/user/clawd/scripts/agent-system-live-quality-alarm.sh: main alarm runner./Users/user/clawd/reports/agent-system-plan2-health-latest.json: last health metrics snapshot.
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.