selftest
Skill0 starsChanged 13 days agoMITView on GitHub
Live capability check of myOS — actually exercises each tool instead of guessing status. Use to answer "is everything working?" honestly.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- erencivril/claude-code-failovertheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- erencivril/claude-code-failover★ 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 repository14 other files it gives its agents.
- captureSkill
- capture-to-inboxSkill
- escalate-to-architectSkill
- file-noteSkill
- interview-meSkill
- janitorSkill
- migrateSkill
- process-inboxSkill
- recallSkill
- resumeSkill
- scanSkill
- taskSkill
- weekly-reviewSkill
- learn-acceleratorSkill
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.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
After changing scripts, paths, or skills.
≈ “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
selftest
Runs the real myOS capability checks — actually exercises each tool rather than assuming it works (the "no more lying 'all fine'" rule).
When to Use
- An "is everything working / run a health check" request.
- After changing scripts, paths, or skills.
Procedure
- Run:
bash $MYOS_ENGINES/myos_selftest.sh. - Relay its output verbatim (the ✅/❌ lines).
- For any ❌, take the obvious fix if one is named (e.g. broken memory links →
bash $MYOS_ENGINES/myos_memory_sync.sh); otherwise runescalate-to-architect.
What it checks
spine + inbox resolves · inbox writable (writes and removes a file) · every template renders · the architect memory links intact · Hermes myOS skills loaded · ollama up · embedding model present · gateway active.
Pitfalls
- Relay verbatim — never summarize a ❌ into an "all good". That's the exact failure mode this skill exists to kill.
- Don't schedule a second report — if a morning brief already folds these checks in (green-collapsed to one line unless something fails), run this skill on demand only.
Verification
- The ✅/❌ block was reproduced as-is; every ❌ has either an applied fix or a queued escalation.
Cadence
On demand, and folded into a scheduled morning brief.
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.