agent-status
Skill0 starsChanged 5 months agoMITView on GitHub
Health dashboard for all agents — last-run timestamp, launchd loaded status, recent errors, missed slots. Use when the user asks "agents 状态" / "哪个 agent 漏跑了" / "/agent-status".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Ormus-Solutions/ormus-agent-opstheir own version, first seen Nov 8, 2026
- HermeticOrmus/ormus-agent-opstheir own version, first seen Apr 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- HermeticOrmus/ormus-agent-ops★ 0same name
- Ormus-Solutions/ormus-agent-ops★ 0same 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.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 45
Read-only: Never delete stamps or touch launchd.
- Distinctive: line 46
Use Asia/Tokyo dates throughout.
- Very specific: line 48
If .stamps/<slot> is missing entirely, mark (missing) not (unknown).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
agent-status
Generate a one-shot health snapshot across every agent in this repo.
Procedure
- Read the canonical agent list from the root
CLAUDE.mdagents table. Slots are encoded in the "触发" column (e.g.,launchd(morning2/afternoon/night + catchup)). - Read every stamp under
.stamps/. Each file's contents is the date of the last successful run (TZ=Asia/Tokyo). The filename is the slot. - Check launchd state with
launchctl list 2>/dev/null | grep -E 'com\.(financial_news|brain_science|notes_sync|daily_brief)\.'. Columns: PID · LastExitStatus · Label. PID-means not currently running, which is normal for scheduled jobs. - Tail each agent log (last 30 lines of
agents/<name>/<name>.log). Look for:Traceback^\[重试\]ERROR|Failed|failedexit [1-9]429|503|TimeoutError
- Render the table below.
Output format
## Agent Status — <today JST>
| agent | slot | last stamp | launchd | last exit | recent error |
|----------------|------------|------------|---------|-----------|--------------|
| financial_news | morning2 | 2026-05-19 | loaded | 0 | — |
| financial_news | afternoon | 2026-05-18 | loaded | 0 | — |
| brain_science | night | (missing) | loaded | 1 | Groq 429 |
| ... | | | | | |
### Missed slots
- brain_science.morning — stamp missing for today
### Suggested actions
- `rm .stamps/brain_morning && agents/brain_science/run.sh morning`Constraints
- Read-only. Never delete stamps or touch launchd.
- Use Asia/Tokyo dates throughout.
- Agents without launchd plist (paper_reader, shukatsu_youtube) show
launchd: manual. - If
.stamps/<slot>is missing entirely, mark(missing)not(unknown). - For agents with multiple slots, output one row per slot.
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.

