Create and manage xbot lifecycle hooks with YAML configuration.
npx skills add https://github.com/ai-pivot/xbot --skill hook-creator-ai-pivot
Please help me install this Agent Skill. Skill: hook-creator Source: https://github.com/ai-pivot/xbot/tree/main/tools/embed_skills/hook-creator Command: npx skills add https://github.com/ai-pivot/xbot --skill hook-creator-ai-pivot
Hook-creator helps you create and manage AI Agent lifecycle hooks so you can enforce checks, run commands, and react to events without changing the core agent logic.
Ask xbot to create a PreToolUse hook that runs a command only when the tool input contains the pattern you specify, writes it to the correct hooks.json layer, and then reloads hooks so the change takes effect immediately.
High-intent search queries and answers about installing and using this skill.
Lifecycle hooks control agent tool execution by configuring YAML logic with event matchers in hooks.json. You can add handlers for events like PreToolUse, PostToolUse, or PermissionRequest to enforce checks and run commands without altering core agent logic.
Lifecycle event hooks support three handler types: command scripts with optional filtering, HTTP web requests, and MCP tool calls with variable interpolation. Each type allows you to react to agent events using different execution methods.
Permission gating uses deny, defer, ask, and allow semantics to control tool execution. You configure these decision rules in your hooks.json file, with deny taking the highest priority, to safely guardrail agent actions before they run.
The hooks.json configuration merges across three layers: personal (~/.xbot/hooks.json), shared project (<project>/.xbot/hooks.json), and local project (<project>/.xbot/hooks.local.json). This 3-layer merge supports personal, shared, and local settings simultaneously.
Yes, you can react to agent errors by configuring an AgentError lifecycle hook. This hook uses an HTTP handler type to trigger a web request, allowing you to send post-tool notifications or execute error recovery logic automatically.
Yes, setting up cron-fired hooks requires YAML-configured hook logic. You define a CronFired event matcher with the correct timeout and async settings in your hooks.json file to trigger scheduled command or HTTP reactions across session runs.
RepairYourTechCreate and configure Claude Code plugin hooks for event-driven automation.
epieczkoValidate and simulate Betty Framework hook manifests with JSON output.
AradotsoDiscover, inspect, and execute MCP server tools from the command line.
C0ntr0lledCha0sCreate Claude Code event hooks for policy enforcement and tool orchestration.
