skills.rest
mattmacleod16-svg
mattmacleod16-svgCOMMUNITY
Explore all skills by this author →
GitHub

rule-identifier

Define Hookify watch patterns and messages in YAML frontmatter files.

1|Updated Feb 25, 2026
Search Tags:#security#claude#yaml#rules#hookify#pattern-matching
One-click install
npx skills add https://github.com/mattmacleod16-svg/freedomforge-max --skill rule-identifier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rule-identifier
Source: https://github.com/mattmacleod16-svg/freedomforge-max/tree/main/.agents/skills/rule-identifier
Command: npx skills add https://github.com/mattmacleod16-svg/freedomforge-max --skill rule-identifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Defining useful Hookify rules can be error-prone without a clear, reusable structure. This skill provides a YAML-driven template for creating and documenting guard rules that trigger on specific hook events.

Core Features & Use Cases

  • Declarative rule definitions stored as .claude/hookify.{rule-name}.local.md files.
  • Supports standard fields (name, enabled, event, pattern) and advanced conditions for multi-criteria matching.
  • Provides guidance and examples for crafting safe, effective hook rules across bash, file, stop, and prompt events.

Quick Start

Create a new file at .claude/hookify.my-rule.local.md with proper frontmatter and a rule body to start enforcing your first hook pattern.

Frequently Asked Questions about rule-identifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define safe Hookify rules using YAML patterns?▼

Hookify rule definitions use YAML frontmatter containing fields like name, enabled, event, pattern, and optional condition blocks to trigger on specific hook events. The skill validates these required fields and supports advanced conditions for multi-criteria matching across bash, file, stop, and prompt events.

What hook events can I target with Hookify pattern-matching rules?▼

Hookify pattern-matching rules support bash, file, stop, and prompt events. You configure the target event in the YAML frontmatter's event field and define matching patterns to trigger specific messages or guidance during AI interactions.

How do I add advanced conditions to my Hookify rules?▼

Advanced conditions can be added to Hookify rules using optional condition blocks in the YAML frontmatter for multi-criteria matching. These condition blocks work alongside the standard pattern field to refine when and how your guard rules trigger across different event types.

Does this approach require dependencies to validate YAML frontmatter for Hookify files?▼

No dependencies are required to validate YAML frontmatter for Hookify files. The skill operates standalone to check required fields like name, enabled, event, and pattern, ensuring your declarative rule definitions are structurally sound before execution.

What is the best way to structure a Hookify rule file for AI interactions?▼

The best way to structure a Hookify rule file is using declarative YAML frontmatter for configuration and a structured rule body for immediate guidance. Store the file at .claude/hookify.{rule-name}.local.md with required fields validated to ensure safe, effective pattern enforcement.

Related Skills

Explore More Software Engineering Skills→
dmedina-devdmedina-dev
1

Writing Hookify Rules

Create Hookify rules with YAML frontmatter to monitor Bash commands, file edits, prompts, and stop events.

Community
Basic
SOLEROMSOLEROM

writing-hookify-rules

Define markdown-based hookify rules to monitor Claude interactions across events.

Community
Intermediate
shinnytechshinnytech

skill-developer

Create and manage Claude Code skills with YAML frontmatter and hooks.

Official
Advanced
brixtonphambrixtonpham

writing-hookify-rules

Create Hookify rules with YAML frontmatter and regex patterns.

Community
Intermediate