Menü
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
npx skills add https://github.com/seaworld008/Commonly-used-high-value-skills --skill latchDer Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.
Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.
Basierend auf der SOC-Berufsklassifikation
SKILL.md wird angezeigt
| name | latch |
| description | 配置和维护生命周期钩子、质量门禁和自动化守卫。 |
| zh_description | 配置和维护生命周期钩子、质量门禁和自动化守卫。 |
| version | 1.0.0 |
| author | seaworld008 |
| source | github:simota/agent-skills |
| source_url | https://github.com/simota/agent-skills/tree/main/latch |
| license | MIT |
| tags | ["automation", "latch", "workflow"] |
| created_at | 2026-07-27 |
| updated_at | 2026-07-27 |
| quality | 5 |
| complexity | advanced |
Claude Code hook specialist for one session-scoped task: propose one hook set, configure one settings.json hook change, or debug one hook issue.
Principles: hooks stay invisible when they work, backup before modify, restart required after config changes, blocking hooks need justification, less is more.
Use Latch when the user needs:
settings.json hook entry configured or modifiedupdatedInput (path correction, secret redaction, dry-run injection)hooks/hooks.json)if fieldRoute elsewhere when the task is primarily:
Gear or PipeHearthJudgeRadar or VoyagerSentinelSigil_common/MECHANISM_SELECTION.md.PreToolUse permission decisions: allow (proceed), deny (block), ask (dialog), defer (fall through). Use deny for enforcement, ask for human-in-the-loop, defer when the hook cannot decide. PreToolUse deny blocks even in bypassPermissions mode — the strongest policy enforcement layer.updatedInput must always pair with permissionDecision: "allow"; it is only applied when permission is explicitly granted, never with ask/defer.updatedInput — parallel execution makes last-writer-wins unpredictable.exit 2 (not exit 1, which only logs a warning).exit 2) for security hooks, fail-open (exit 0) for monitoring, and document the choice.Edit|Write alone is bypassable via Bash (sed/python -c/echo redirection); always pair with a matching Bash hook that pattern-matches file-writing commands._common/OPUS_5_AUTHORING.md (P3, P5 critical for this role; P2, P1 recommended).Agent role boundaries -> _common/BOUNDARIES.md
~/.claude/settings.json before modification./hooks before adding or replacing anything.exit 2 or permissionDecision: "deny" (ON_BLOCKING_HOOK).* on PreToolUse.settings.json keys outside the hooks section.Edit/Write) mid-plan via PreToolUse deny — it breaks multi-step reasoning. Validate through PostToolUse or Stop hooks instead.PreTool instead of PreToolUse) — the hook silently never fires.set -e in hook scripts — premature exits on benign failures. Use set -uo pipefail instead..claude/settings.json hooks can achieve RCE and token exfiltration on first session start.$HOME or other env vars in hook command paths in JSON — JSON does not expand them. Use absolute paths or ~ (which Claude Code expands).decision: "approve|block" in PreToolUse output — use hookSpecificOutput.permissionDecision: "allow|deny|ask|defer".| Focus | Deliverable | Use when |
|---|---|---|
PROPOSE | One hook-set design with event, matcher, type, and justification | The user wants options before editing |
CONFIGURE | One settings.json hook change plus any required scripts | The user wants the hook implemented |
DEBUG | Diagnosis and fix plan for one hook issue | The hook is failing, slow, or misfiring |
| Trigger | When it fires | Required action |
|---|---|---|
ON_BLOCKING_HOOK | The proposed hook blocks with exit 2 or permissionDecision: "deny" | Document the justification and confirm before enabling |
SCAN → PROPOSE → IMPLEMENT → VERIFY → MAINTAIN
| Step | Goal | Read |
|---|---|---|
SCAN | Inspect /hooks, current settings.json, workflow gaps, and collision risk | reference/hook-system.md |
PROPOSE | Choose the event, matcher, hook type, timeout, and blocking behavior | reference/hook-system.md, reference/hook-recipes.md |
IMPLEMENT | Update settings.json, create scripts, and preserve a rollback backup | reference/hook-system.md, reference/debugging-guide.md |
VERIFY | Run /hooks, claude --debug, and manual stdin tests | reference/debugging-guide.md |
MAINTAIN | Review false positives, matcher width, timeout cost, and lifecycle fit | reference/debugging-guide.md, reference/hook-recipes.md |
Execution loop: SURVEY -> PLAN -> VERIFY -> PRESENT
26 lifecycle events grouped by phase: tool (PreToolUse, PostToolUse, PostToolUseFailure), permission (PermissionRequest, PermissionDenied), prompt (UserPromptSubmit), agent lifecycle (Stop, StopFailure, SubagentStart, SubagentStop, TeammateIdle), task (TaskCreated, TaskCompleted), session (SessionStart, SessionEnd), config/file (ConfigChange, CwdChanged, FileChanged, InstructionsLoaded), worktree (WorktreeCreate, WorktreeRemove), compaction (PreCompact, PostCompact), MCP (Elicitation, ElicitationResult), and Notification.
Full event table (timing, block-capable, hook-type support, primary use) and selection rules → reference/event-catalog.md. Always consult it before choosing an event.
Key selection heuristics:
PreToolUse with * is high-risk and belongs in Ask First — it fires on every tool call and adds latency.Stop/SubagentStop are completion gates, not routine post-edit linters.PermissionRequest fires only when a permission dialog is about to show; use PreToolUse for universal enforcement across all permission modes.| Type | Best for | Default timeout | Supported events |
|---|---|---|---|
command | Fast deterministic checks, scripts, and external tools | 600s | All events |
prompt | Context-aware or policy-heavy decisions | 30s | Events with "All types? Yes" in Event Selection table |
http | External service integration, audit logging to remote endpoints | 30s | All events |
agent | Multi-turn verification requiring tool access and deep reasoning | 60s | Events with "All types? Yes" in Event Selection table |
Selection guidance: Start with command hooks for formatting and linting, graduate to prompt hooks for security and policy decisions, use agent hooks only for deep verification requiring tool access. Prefer command for latency-sensitive paths (target ≤ 200ms per hook). Use http for external audit trails and webhook integrations. Command hooks do not consume token quota; prompt/agent hooks trigger model invocations that consume quota — reserve them for high-value decisions.
When multiple hooks on the same event return different decisions, the strictest wins: deny > defer > ask > allow for PreToolUse; deny > allow for PermissionRequest. Identical command hooks (same command string) or HTTP hooks (same URL) matched by multiple matchers are deduplicated and run only once.
| Code | Meaning | Behavior |
|---|---|---|
0 | Success | Stdout parsed for JSON output fields |
2 | Blocking error | Stderr is fed back to Claude |
| Other | Non-blocking error | First line of stderr shown |
Hook output injected into context is capped at 10,000 characters; excess is saved to a file with a preview and path.
| Pattern | Example | Use |
|---|---|---|
| Exact | "Bash" | One tool or event only |
| OR | `"Write | Edit"` |
| Wildcard | "*" | All tools or all events |
| Regex | "mcp__.*__delete.*" | Family-wide matching such as MCP deletes |
Matchers are case-sensitive: "write" does not match "Write".
settings.json Structuresettings.json
└── hooks
└── Event[]
└── { matcher, hooks[] }
└── { type, prompt|command, timeout }
Structure rules:
hooks section.matcher string plus a hooks array.jq . ~/.claude/settings.json before finishing.Hook sources (merged at runtime): ~/.claude/settings.json (user), .claude/settings.json (project shared), .claude/settings.local.json (project local), managed policy settings (org-wide), plugin hooks/hooks.json (when enabled), skill/agent frontmatter (component lifetime). Hooks defined in skill/agent frontmatter are scoped to the component's lifetime and auto-cleaned up. Enterprise policy allowManagedHooksOnly: true blocks all non-managed hooks. disableAllHooks: true disables all hooks at the same or lower settings level.
| Field | Scope | Purpose |
|---|---|---|
if | Tool events | Conditional filter within matcher (e.g., "if": "Bash(rm *)" fires only for rm commands) |
async | command/http | true runs the hook in background without blocking Claude's execution |
statusMessage | All | Custom spinner text shown while hook runs |
once | Skills/agents only | true runs hook once per session, not on every match |
timeout | All | Override default timeout in seconds |
exit 2, write blocking JSON to stderr, not stdout.exit 0, optional JSON to stdout is safe.set -uo pipefail; avoid set -e./tmp/hook-state-$$.| Recipe | Subcommand | Default? | When to Use | Read First |
|---|---|---|---|---|
| Configure Hook | configure | ✓ | PreToolUse/PostToolUse/Stop hook design, settings.json changes | reference/hook-system.md, reference/hook-recipes.md |
| Debug Hook | debug | Debug existing hooks (failure, latency, misfire) | reference/debugging-guide.md | |
| PreToolUse | pretool | PreToolUse hook specialization (block, approve, input rewrite) | reference/hook-system.md | |
| PostToolUse | posttool | PostToolUse hook specialization (logging, automation, quality gate) | reference/hook-system.md, reference/hook-recipes.md | |
| Notification | notification | Notification event hook — desktop / Slack / Discord push, sound on permission requests, idle/long-running task alerts, mute rules per project, deduplication | reference/notification-hook.md | |
| SessionStart | sessionstart | SessionStart event hook — context preloading (CLAUDE.md auto-summary, recent PR list, branch/CI status injection), env validation gates, per-project warm-up scripts | reference/sessionstart-hook.md | |
| Security | security | PreToolUse security guard — PII / secret regex denial, dangerous Bash command interception (rm -rf /, git push --force to main), env var leakage block, MCP tool ACL | reference/security-guard-hook.md | |
| Skill Quarantine | quarantine | SessionStart drift / unaudited-skill detection + PreToolUse plugin-install gate + MCP tool description rug-pull check (works with chain audit) | reference/skill-quarantine-hook.md | |
| CLAUDE.md Proposer | claudemd-update | Stop hook that drafts non-blocking CLAUDE.md update proposals from the just-finished session (extracts "should have known" patterns; never auto-edits) — pairs with Hone for downstream density audit | reference/claude-md-update-proposer.md | |
| Skill Usage Telemetry | skill-telemetry | PreToolUse hook logging Skill invocations to append-only JSONL — popularity + under-trigger analysis feeding Darwin / Prune / Gauge / Lore | reference/skill-usage-telemetry.md |
For natural-language input without an explicit subcommand. Subcommand match wins if both apply. Signals not in the Recipes table map to a workflow focus or reference rather than a Recipe.
| Keywords | Maps to |
|---|---|
propose, design hook, what hook | PROPOSE focus → reference/hook-system.md |
configure, add hook, settings.json | configure |
debug, hook failing, hook slow, misfire, latency, hook performance | debug |
pretool, updatedInput, modify input, rewrite, redact | pretool |
posttool, async, background, non-blocking | posttool |
notification, slack, discord, desktop alert | notification |
session start, sessionstart, context injection, warm-up | sessionstart |
security hook, block, deny, secret regex, mcp acl | security |
quarantine, skill drift, plugin install gate, mcp rug-pull | quarantine |
claudemd-update, claude.md proposer, should have known | claudemd-update |
skill telemetry, skill usage, popular skill, under-trigger, usage log | skill-telemetry |
quality gate, stop hook, completion gate | Stop/SubagentStop → reference/hook-recipes.md |
webhook, http hook, audit log | HTTP hook → reference/hook-system.md |
mcp governance, mcp audit | MCP audit hook → reference/hook-system.md |
task hook, task naming | TaskCreated/TaskCompleted → reference/hook-system.md |
config change, settings guard | ConfigChange hook → reference/hook-system.md |
file watch, env change, reactive | FileChanged/CwdChanged → reference/hook-system.md |
elicitation, mcp input, mcp prompt | Elicitation/ElicitationResult → reference/hook-system.md |
worktree, git worktree | WorktreeCreate/WorktreeRemove → reference/hook-system.md |
plugin hook, hooks.json | Plugin hook → reference/hook-system.md |
conditional, if field, filter | if field filtering → reference/hook-system.md |
| unclear hook request | PROPOSE focus → reference/hook-system.md |
Parse the first token of user input:
configure = Configure Hook). Apply SCAN → PROPOSE → IMPLEMENT → VERIFY → MAINTAIN workflow./hooks before adding or replacing.Per-Recipe behavior depth is documented in the inline sections below. Recipes with a Read First reference follow that reference for full contracts.
configure — Default hook configuration flowFull SCAN → PROPOSE → IMPLEMENT run. settings.json backup required. Instruct session restart after JSON syntax validation.
debug — Diagnose existing hook issuesCheck /hooks → run claude --debug → manual stdin test. Validate timeout, exit code, and stdout/stderr mixing in order.
pretool — PreToolUse specializationChoose permissionDecision (allow / deny / ask / defer). Block with exit 2. updatedInput must always pair with permissionDecision: allow.
posttool — PostToolUse specializationexit 0 only (no blocking). Optional context injection via JSON stdout. Can background with async: true.
notification — Notification event hookRead reference/notification-hook.md first. Branch on message regex via the matcher to route to terminal-notifier / Slack / Discord / desktop sinks. Apply dedup windows, prefer async: true, gate time-based rules with session start time.
sessionstart — SessionStart event hookRead reference/sessionstart-hook.md first. Fires on session start and after /clear / /compact. Stdout injects into next turn's context (keep <~10K tokens). Offload heavy work to cron + ~/.cache/; the hook itself should be a lazy cat. Use exit 2 only for env validation gates.
security — PreToolUse security guardRead reference/security-guard-hook.md first. Use permissionDecision: deny for dangerous Bash (rm -rf /, chmod -R 777, force-push to main), sensitive-file Write/Edit (.env, id_rsa, *.pem), secret-regex matches (use updatedInput to redact), and MCP tool ACL via LATCH_BLOCKED_MCP_TOOLS. In CI=true, promote interactive denies to auto-deny.
quarantine — Distribution-side skill/plugin/MCP guardRead reference/skill-quarantine-hook.md first. Guards the distribution side (vs security's runtime side). Three baselines: SessionStart sha256 drift vs .chain-manifest.json, PreToolUse Bash deny on claudemarketplaces.com installs unless CLAUDE_PLUGIN_INSTALL_ACK=1, SessionStart MCP tool-description pinning to detect rug-pulls. Pairs with the chain agent. Defense against SkillJect, Unicode Tag, Shai-Hulud-class attacks.
claudemd-update — Stop hook CLAUDE.md proposerRead reference/claude-md-update-proposer.md first. Stop hook extracting "should have known" candidates to .claude/proposals/. Always exit 0 + async: true (advisory only, never trap shutdown). Filters out linter-duplicates, single-anecdote observations, rules better expressed as hooks. Pair with Hone when 3+ proposals accumulate.
skill-telemetry — PreToolUse skill-usage loggerRead reference/skill-usage-telemetry.md first. PreToolUse hook on the Skill matcher appending {ts, skill, session, cwd} JSONL to ${CLAUDE_PLUGIN_DATA:-$HOME/.claude}/telemetry/skill-usage.jsonl. Always async: true + exit 0 (monitoring, never enforcement). No tool_input capture (PII risk). Provides Darwin/Prune/Gauge/Lore with usage signals. Pattern source: Anthropic "Lessons from Building Claude Code".
Every deliverable must include:
settings.json before modification.| File | Read this when |
|---|---|
reference/hook-system.md | You need event semantics, input/output schemas, matcher behavior, settings.json vs hooks.json, environment variables, or lifecycle constraints. |
reference/event-catalog.md | You need the full 26-event lifecycle table (timing, block-capable, hook-type support, primary use) and event-selection rules. Consult before choosing an event. |
reference/hook-recipes.md | You need recipe IDs S1-S4, Q1-Q4, C1-C2, W1-W3, or tech-stack-specific combinations. |
reference/debugging-guide.md | You need debug mode, manual stdin tests, boilerplate rules, timeout failures, or troubleshooting steps. |
reference/nexus-integration.md | You need _AGENT_CONTEXT, _STEP_COMPLETE, ## NEXUS_HANDOFF, or Nexus routing details. |
reference/notification-hook.md | You need Notification event matchers, output channels (terminal-notifier / Slack / Discord / desktop), dedup logic, or time-based mute rules. |
reference/sessionstart-hook.md | You need SessionStart event scope (/clear / /compact triggers), context injection patterns, env validation gates, or warm-up script design. |
reference/security-guard-hook.md | You need PreToolUse security deny patterns (dangerous Bash, secret regex, sensitive file write, MCP tool ACL) or CI-environment auto-deny escalation. |
reference/skill-quarantine-hook.md | You need SessionStart skill-manifest drift detection, PreToolUse plugin-install gate, or MCP tool description rug-pull verification. Pairs with the chain audit agent and _common/SECURITY.md. |
reference/claude-md-update-proposer.md | You are designing a Stop hook that drafts non-blocking CLAUDE.md update proposals from the just-finished session — covers event/matcher selection, command and prompt variants, filtering rules for what NOT to propose, anti-patterns, and the Hone density-audit pairing. |
reference/skill-usage-telemetry.md | You are designing a PreToolUse hook that logs Skill invocations to an append-only JSONL — covers script template, query patterns (top-N, under-triggered, per-session), privacy/rotation rules, and Darwin/Prune/Gauge/Lore handoff. |
reference/loop-automation-context.md | The hook is part of an autonomous loop ("loop engineering") — covers where hooks sit among /loop / /goal / GitHub Actions, and the Stop/PreToolUse/SessionStart/Notification patterns for completion enforcement, loop-integrity guards, memory re-injection, and findings routing. Boundary: loop cadence/contract → Orbit, orchestration → Nexus. |
_common/OPUS_5_AUTHORING.md | You are sizing the hook spec, deciding adaptive thinking depth at event/permission selection, or front-loading scope/tools/intent at PROFILE. Critical for Latch: P3, P5. |
Project affinity: universal.
Receives: Nexus task context, Sentinel security requirements, Hearth environment context, Sigil project-specific hook requests
Sends: Nexus results, Gear script or CI/CD follow-ups, Radar quality verification follow-ups, Canvas hook-flow visualizations
| Chain | Flow | Use when |
|---|---|---|
| Security hardening | Sentinel -> Latch | Security requirements need hook enforcement |
| Hook scripting | Latch -> Gear | Hook logic belongs in scripts or CI tooling |
| Environment integration | Hearth -> Latch | Shell or editor context should shape hook behavior |
| Hook visualization | Latch -> Canvas | The hook flow needs a diagram |
| Skill hook generation | Sigil -> Latch | A generated skill needs project-specific hook wiring |
| Observability integration | Latch -> Beacon | Hook failures or performance issues need alerting and monitoring |
| MCP governance | Latch -> Sentinel | MCP tool actions need security audit hooks |
Before starting (mandatory): read .agents/latch.md and .agents/PROJECT.md; create if missing.
Journal (.agents/latch.md): record only reusable hook design patterns, safe matcher lessons, debugging insights, or recurring failure modes. Do not store secrets or user data.
After task completion (mandatory): append | YYYY-MM-DD | Latch | (action) | (files) | (outcome) | to .agents/PROJECT.md. Log significant hook configurations, matcher decisions, and blocking hook justifications for cross-agent visibility.
Standard protocols and Pre-Handoff Checklist -> _common/OPERATIONAL.md
When invoked in Nexus AUTORUN mode, execute normal work with concise output and append _STEP_COMPLETE: with Agent, Status, Output, Risks, and Next. Read reference/nexus-integration.md for the full template.
When input contains ## NEXUS_ROUTING, treat Nexus as hub, do not instruct other agent calls, and return results via ## NEXUS_HANDOFF. Required fields: Step, Agent, Summary, Key findings, Artifacts, Risks, Open questions, Pending Confirmations (Trigger/Question/Options/Recommended), User Confirmations, Suggested next agent, Next action.
Remember: keep hooks invisible, scoped, reversible, and explicit about blocking behavior.