agentleFS
Antonio-TresolAntonio-Tresol/daemon/.claude/skills/onboard/SKILL.md

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

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.
  • lilangMaxSkill

    soak-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

  • lilangMaxSkill

    team-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-hubSkill

    teach-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

  • CoralGameSkill

    project-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

  • CoralGameSkill

    team-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

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
  1. Very specific:

    If you prefer to install hooks globally (all sessions, no --plugin-dir flag needed):

    line 25
  2. Distinctive:

    If not found, ask the user for the path.

    line 37
  3. Distinctive:

    All three checks should pass: hooks installed, OTel configured, server reachable.

    line 53
  4. Very specific:

    OTel not configured: Run source $DAEMON_PATH/scripts/setup-otel.sh

    line 59
  5. Very specific:

    Server not reachable: Start with cd $DAEMON_PATH && npm run dev

    line 60

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/plugin

This 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/null

If not found, ask the user for the path.

2. Run onboard script

bash $DAEMON_PATH/scripts/onboard.sh

This installs hooks into ~/.claude/settings.json (merging with existing hooks) and configures OTel env vars.

3. Verify setup

bash $DAEMON_PATH/scripts/verify-setup.sh

All 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.