hook
Use PROACTIVELY when you need to create, update, configure, or validate Claude hooks for various events and integrations
What this skill does
## 1. Context - Main Objective: Create or update Claude Code hook scripts named $1 with requirements: $2 - Secondary Objective: Ensure hooks are properly linked in settings and follow security best practices - User Input: [$1 = hook name, $2 = hook requirements/description] ## 2. Workflow ### Phase 1: Discovery & Analysis [P0] - T001: Assess if you needed more context about hook specifications. If so, read `.claude/skills/hook/hooks.md` [P0] - T002: Check if hook already exists in `.claude/hooks/` directory [P0] - T003: Review `@.claude/settings.local.json` for existing hook configurations [P1] - T004: Identify appropriate Claude Code events to hook into [P1] - T005: Assess security and performance implications [P2] ### Phase 2: Implementation [P0] - T006: Create new hook script OR update existing hook script in `.claude/hooks/` [P0] - T007: Implement hook logic with proper error handling [P0] - T008: Add logging and debugging capabilities [P1] - T009: Create input validation and sanitization routines [P1] - T010: Document hook behavior in script comments [P2] ### Phase 3: Configuration [P1] - T011: Update `@.claude/settings.local.json` to link the hook [P0] - T012: Configure appropriate event triggers [P1] - T013: Set necessary permissions and access levels [P1] - T014: Ensure compatibility with existing hooks [P2] ### Phase 4: Validation [P1] - T015: Test hook execution without creating test files [P0] - T016: Verify error handling and edge cases [P1] - T017: Check for security vulnerabilities [P1] - T018: Validate performance impact [P2] - T019: Provide comprehensive report to main agent [P0] ## 3. Implementation Strategy - For new hooks: Create script file in `.claude/hooks/` following naming convention - For updates: Read existing hook, preserve working logic, apply requested changes - Use Python or Bash depending on complexity requirements - Implement idempotent operations where possible - Follow existing hook patterns in the codebase for consistency - Read `.claude/skills/hook-writer/hooks.md` for hook specifications PROACTIVELY ## 4. Constraints - **Must** update `@.claude/settings.local.json` to link hooks - **Must** test hooks after generation without creating test files - **Never** create hooks that modify critical system files - **Never** implement hooks with hardcoded credentials - **Never** write hooks that can cause infinite loops - **Never** bypass security validations or access controls - **Never** create hooks without proper error handling - **Never** create test files when testing hooks ## 5. Success Criteria - Hook script exists and is syntactically valid - Hook is properly linked in `settings.local.json` - Hook executes successfully on target event - Error handling covers common failure scenarios - No security vulnerabilities detected - Comprehensive report provided to main agent upon completion
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.