onboard
Skill2 starsChanged 8 months agoMITView on GitHub
Set up daemon monitoring — install the plugin or run the onboard script to instrument Claude Code sessions
172 other projects use a version of this.
Adopted by
Most recently taken up by
- TsukiNi22/skillstheir own version, first seen Nov 16, 2026
- TsukiNi22/ai-utilstheir own version, first seen Nov 16, 2026
- akovfoj-lang/plainframetheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- jestatsio/codebase-mentortheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
Used with
Projects with it also use soak-test, team-live-ops and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
HK-hubSkillteach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Also in 19 projects that use this
CoralGameSkillproject-stage-detect
Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.
Also in 15 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 11 projects that use this
- +5 more from lilangMax
- +2 more from CoralGame
Other versions172 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 172
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- nateherkai/AIS-OS★ 1.4ksame name
- poshan0126/dotclaude★ 871same name
- talesofai/cohub★ 585same name
- me2resh/apexyard★ 542same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 424same name
162 more not listed
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
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 160 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If you prefer to install hooks globally (all sessions, no --plugin-dir flag needed):
- Distinctive: line 37
If not found, ask the user for the path.
- Distinctive: line 53
All three checks should pass: hooks installed, OTel configured, server reachable.
- Very specific: line 59
OTel not configured: Run source $DAEMON_PATH/scripts/setup-otel.sh
- Very specific: line 60
Server not reachable: Start with cd $DAEMON_PATH && npm run dev
“Common” is measured: kept by at least 6 in 10 of the 160 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Onboard to Daemon
Set up Claude Code monitoring by installing the daemon plugin or running the setup scripts.
Option A: Plugin (Recommended)
The plugin auto-installs hooks and skills — no manual configuration needed.
claude --plugin-dir /path/to/daemon/pluginThis gives you:
- 7 HTTP hooks streaming events to daemon
/daemon:harness— query failures and improvements/daemon:analyze— trigger analysis, explore matryoshka levels/daemon:session— inspect session events and metadata
Option B: Global Hook Installation
If you prefer to install hooks globally (all sessions, no --plugin-dir flag needed):
1. Find daemon installation
# Check env var first
echo "${DAEMON_PATH:-not set}"
# Or locate the daemon directory
ls -d ~/daemon ~/projects/daemon ~/code/daemon 2>/dev/nullIf not found, ask the user for the path.
2. Run onboard script
bash $DAEMON_PATH/scripts/onboard.shThis installs hooks into ~/.claude/settings.json (merging with existing hooks) and configures OTel env vars.
3. Verify setup
bash $DAEMON_PATH/scripts/verify-setup.shAll three checks should pass: hooks installed, OTel configured, server reachable.
4. Report results
Show the verification output. If anything failed:
- Hooks not installed: Re-run
bash $DAEMON_PATH/scripts/setup-hooks.sh - OTel not configured: Run
source $DAEMON_PATH/scripts/setup-otel.sh - Server not reachable: Start with
cd $DAEMON_PATH && npm run dev
Remind the user to restart Claude Code to activate the newly installed hooks.
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.

