agentleFS
Edmonds-Commerce-LimitedEdmonds-Commerce-Limited/claude-code-hooks-daemon/.claude/skills/configure/SKILL.md

configure

Skill4 starsChanged 16 days agoMITView on GitHub

View and modify hooks daemon handler configuration - enable/disable handlers, change priorities, set handler options

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use calendar, setup and 2 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.
  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 7 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 3

    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. Distinctive:

    Follow its output exactly.

    line 18
  2. Distinctive:

    If omitted: Show config summary

    line 56
  3. Very specific:

    If list: Show all handlers with options

    line 57
  4. Distinctive:

    Every handler's configurable options, values, defaults, and examples are documented there.

    line 117
  5. Very specific:

    All handlers also accept the common properties enabled (bool) and priority (int).

    line 125
  6. Very specific:

    Use /configure list to see what options are set in your current config.

    line 127

“Common” is measured: kept by at least 6 in 10 of the 43 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

/configure - Handler Configuration Skill

Run this first

Claude Code loads this markdown and nothing else — the file below is not run for you, and it holds the procedure to follow (Plan 00324):

bash "${CLAUDE_SKILL_DIR:-.claude/skills/configure}/invoke.sh" <the arguments the user typed>

Follow its output exactly; what is written here is orientation.

Description

View and modify the hooks daemon configuration interactively. Supports listing handlers, viewing individual handler settings, and changing options (enabled, priority, handler-specific options) with automatic daemon restart and verification.

Usage

# Show summary of current config (daemon settings + handler overview)
/configure

# List all handlers with their configurable options
/configure list

# Show config for one handler
/configure sed_blocker

# Set a handler option
/configure sed_blocker blocking_mode=direct_invocation_only

# Disable a handler
/configure sed_blocker enabled=false

# Re-enable a handler
/configure sed_blocker enabled=true

# Override a handler's priority
/configure sed_blocker priority=15

# Set options on handlers with nested options block
/configure git_stash mode=deny
/configure markdown_organization track_plans_in_project=CLAUDE/Plan

Parameters

  • handler (optional): Handler config key (e.g., destructive_git, sed_blocker)
    • If omitted: Show config summary
    • If list: Show all handlers with options
  • option=value (optional): Key-value pair to set
    • enabled=true|false -- Enable or disable the handler
    • priority=N -- Override handler priority (integer)
    • <option_key>=<value> -- Set a handler-specific option

What It Does

Show Summary (/configure)

  1. Reads .claude/hooks-daemon.yaml
  2. Displays daemon settings (log_level, idle_timeout, etc.)
  3. Lists all handlers grouped by event type with enabled/disabled status and priority

List Handlers (/configure list)

  1. Reads .claude/hooks-daemon.yaml
  2. For each handler, shows:
    • Config key, event type, enabled status, priority
    • Any configurable options and their current values
    • Available options from source code (with defaults)

Show Handler (/configure <handler>)

  1. Reads .claude/hooks-daemon.yaml
  2. Locates handler under its event type section
  3. Displays all current settings and available options
  4. Cross-references docs/guides/HANDLER_REFERENCE.md for description

Set Option (/configure <handler> <option>=<value>)

  1. Reads .claude/hooks-daemon.yaml
  2. Locates the handler under handlers.<event_type>
  3. Updates the setting:
    • enabled and priority: Set directly on the handler block
    • Other options: Set under the handler's options: sub-block
  4. Saves the file (preserving YAML structure and comments where possible)
  5. Restarts daemon to apply changes
  6. Verifies daemon status is RUNNING
  7. Reports result

Python Path Detection

The skill detects the correct Python path automatically:

# Self-install mode (daemon development)
./bin/hooks-daemon <command>

# Normal install mode
.claude/hooks-daemon/bin/hooks-daemon <command>

The wrapper resolves the fingerprint-keyed venv itself, so there is no interpreter path to detect or hardcode.

Handler Options Reference

📖 Single source of truth: Handler Reference

Every handler's configurable options, values, defaults, and examples are documented there. Do not duplicate that content here.

Quick examples of what options look like:

  • sed_blocker → blocking_mode (strict | direct_invocation_only)
  • git_stash → mode (warn | deny)
  • markdown_organization → track_plans_in_project, plan_workflow_docs

All handlers also accept the common properties enabled (bool) and priority (int).

Use /configure list to see what options are set in your current config.

Config File Location

The skill reads and writes to:

<project-root>/.claude/hooks-daemon.yaml

Output

On successful option change:

Updated sed_blocker.options.blocking_mode = direct_invocation_only

Restarting daemon...
Daemon: RUNNING (PID 12345)

Change applied successfully.

On show handler:

Handler: sed_blocker
  Event type: pre_tool_use
  Enabled: true
  Priority: 11
  Type: Blocking

  Options:
    blocking_mode: strict (default)
      Values: strict | direct_invocation_only
      Description: Controls which invocations are blocked

Error Handling

Handler not found:

Handler "destrutive_git" not found.
Did you mean: destructive_git?

Invalid option:

Unknown option "blcoking_mode" for sed_blocker.
Available options: blocking_mode

Daemon fails to restart:

WARNING: Daemon failed to start after config change.
Check logs: .claude/hooks-daemon/bin/hooks-daemon logs
Consider reverting the change.

Requirements

  • .claude/hooks-daemon.yaml must exist
  • Python venv must be available (self-install or normal install)
  • Daemon must be installed and operational

Documentation

SINGLE SOURCE OF TRUTH: docs/guides/CONFIGURATION.md for config syntax Handler options: docs/guides/HANDLER_REFERENCE.md

Version

Introduced in: v2.16.0

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.