offboard
Skill2 starsChanged 8 months agoMITView on GitHub
Remove daemon monitoring from this environment
2 other projects use a version of this.
Adopted by
Most recently taken up by
- damacus/agent-skillstheir own version, first seen Oct 29, 2026
- baizhine999/leader-skillstheir own version, first seen Oct 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- baizhine999/leader-skills★ 8same name
- damacus/agent-skills★ 2same 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, 2 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Remove daemon instrumentation from your Claude Code environment.
- Very specific: line 11
If you installed via plugin, simply stop using the --plugin-dir flag:
- Distinctive: line 21
No cleanup needed — plugin hooks are only active when the plugin is loaded.
- Distinctive: line 25
If you installed hooks globally via the onboard script:
≈ “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
Offboard from Daemon
Remove daemon instrumentation from your Claude Code environment.
Option A: Plugin Users
If you installed via plugin, simply stop using the --plugin-dir flag:
# Before (instrumented)
claude --plugin-dir /path/to/daemon/plugin
# After (not instrumented)
claudeNo cleanup needed — plugin hooks are only active when the plugin is loaded.
Option B: Global Hook Removal
If you installed hooks globally via the onboard script:
1. Find daemon installation
echo "${DAEMON_PATH:-not set}"
ls -d ~/daemon ~/projects/daemon ~/code/daemon 2>/dev/null2. Remove hooks
bash $DAEMON_PATH/scripts/uninstall-hooks.shThis surgically removes only daemon HTTP hooks from ~/.claude/settings.json, preserving all other hooks and settings. A backup is created automatically.
3. Verify removal
# Should return 0 matches
grep -c "api/events" ~/.claude/settings.json 2>/dev/null || echo "Clean — no daemon hooks found"4. Report
Confirm what was removed:
- HTTP hooks targeting
/api/events— removed - Other hooks and settings — preserved
- Backup saved at
~/.claude/settings.json.pre-uninstall
Note: OTel env vars only persist for the current shell. They will be gone after restart.
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.