selftest
Skill1 starsChanged 33 days agoMITView on GitHub
Check that the failover plugin still works with the installed Claude Code version. Runs only when the user invokes it.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- CipherNovaa/agent-skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- CipherNovaa/agent-skills★ 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
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 9
Run the self-test and report its result to the user:
- Distinctive: line 17
If it passed, say so in one line.
- Very specific: line 18
If it failed, show which steps failed and the log path it printed, and suggest updating the plugin (/plugin marketplace update …
- Distinctive: line 19
If it was skipped, say why.
≈ “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
Failover self-test
Run the self-test and report its result to the user:
"${CLAUDE_PLUGIN_ROOT}/scripts/selftest.sh" --forceIt starts one headless Claude Code session against a local mock API with a stub fallback agent, so it costs no tokens and sends nothing off the machine. It takes up to a minute.
- If it passed, say so in one line.
- If it failed, show which steps failed and the log path it printed, and suggest updating the plugin (
/plugin marketplace update claude-code-failover) or reporting the failure with the log at https://github.com/erencivril/claude-code-failover/issues. - If it was skipped, say why.
The same check runs by itself in the background the first time a session starts after Claude Code or the plugin changes version. It covers plugin loading, prompt capture, the StopFailure hook and the detached handoff. It cannot cover the automatic wake-up of an interactive session, which only happens with a terminal attached.
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.