daily-check
Skill0 starsChanged 7 months agoMITView on GitHub
This skill activates when the user asks about: system health, daily check, Ollama status, MCP health, disk usage, disk space, RAM check, available memory, token budget, token usage, API keys working, is everything running, health status, check system. Also triggers at session start if the last check was more than 24 hours ago (CC-15: auto-trigger when ~/.watchdog/daily_report.json timestamp > 24h old or missing).
2 other projects use a version of this.
Adopted by
Most recently taken up by
- pschlieker/getbacklanetheir own version, first seen Nov 8, 2026
- logly/mureotheir own version, first seen Apr 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- logly/mureo★ 64same name
- pschlieker/getbacklane★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 41
If cron is set up (via install.sh Phase 11), runs daily at 09:00:
- Distinctive: line 56
If critical issues found (Ollama down, API key expired, disk >90%):
≈ “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
Daily Health Check Skill
Automated daily system health monitoring for Claude Code setups.
Trigger Phrases
| Intent | Phrases | Routes To |
| Full check | daily check, system health, is everything running, health status | /daily-check |
| Ollama | ollama status, is ollama running, ollama models | /daily-check |
| MCP | MCP health, MCP status, are MCPs working | /daily-check |
| Disk | disk usage, disk space, how much disk | /daily-check |
| RAM | RAM check, available memory, how much memory | /daily-check |
| Tokens | token budget, token usage, API usage | /daily-check |
| API Keys | API keys working, are keys valid | /daily-check |
What It Checks
| Component | Check |
| Ollama | Running, models loaded, response time |
| MCP Servers | Connected, responding |
| API Keys | Claude, OpenRouter, GitHub, Telegram |
| Disk | Usage % on home drive |
| RAM | Available memory |
| Token Usage | Claude API usage vs quota |
| Agent Registry | sync_agents.py --check — drift detection |
Report Location
Results saved to ~/.watchdog/daily_report.json and logged in ~/.watchdog/daily.log.
Auto-Schedule
If cron is set up (via install.sh Phase 11), runs daily at 09:00:
0 9 * * * bash ~/.claude/config/daily-check.sh >> ~/.watchdog/daily.log 2>&1Running Manually
/daily-check
# or:
bash ~/.claude/config/daily-check.shAlerts
If critical issues found (Ollama down, API key expired, disk >90%):
- Sends Telegram notification if bot is running
- Logs to
~/.watchdog/alerts.log| Reset | reset daily check, force fresh check, clear daily report |/daily-check-reset| | Summary | show last report, last check results, what was the result |/daily-check-summary|
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.