rule-identifier
Provides syntax and pattern guidance for creating custom Hookify rules to trigger automated responses.
Install
mkdir -p .claude/skills/rule-identifier && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/427" && unzip -o skill.zip -d .claude/skills/rule-identifier && rm skill.zipInstalls to .claude/skills/rule-identifier
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.Key capabilities
- →Generates YAML frontmatter structures
- →Defines regex pattern matching
- →Maps bash/file events to actions
- →Validates rule syntax logic
- →Configures block vs warn behaviors
How it works
Applies a template-based generator to produce rule files that adhere to the Hookify markdown schema.
Inputs & outputs
When to use rule-identifier
- →Create a custom Hookify rule
- →Configure rule event triggers
- →Debug regex patterns for rules
- →Add a new blocking rule
About rule-identifier
Assists with writing and configuring Hookify rule files (YAML frontmatter and regex patterns). It defines triggers for bash commands, file edits, and agent events.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
When not to use it
- →When creating general-purpose shell scripts
- →When writing standard application business logic
Limitations
- →Regex patterns must be simple enough for the parser
- →Limited to the specific events defined by the hookify system
How it compares
It automates the specific boilerplate formatting required for Hookify instead of writing rules manually.
Compared to similar skills
rule-identifier side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| rule-identifier (this skill) | 5 | 12mo | Review | Beginner |
| command-development | 16 | 12mo | Review | Intermediate |
| prpm-development | 6 | 11mo | Review | Intermediate |
| autonomous-agent-patterns | 4 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by anthropics
View all by anthropics →You might also like
command-development
anthropics
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
prpm-development
pr-pm
Use when developing PRPM (Prompt Package Manager) - comprehensive knowledge base covering architecture, format conversion, package types, collections, quality standards, testing, and deployment
autonomous-agent-patterns
davila7
Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool APIs, implementing permission systems, or creating autonomous coding assistants.
example-skill
anthropics
This skill should be used when the user asks to "demonstrate skills", "show skill format", "create a skill template", or discusses skill development patterns. Provides a reference template for creating Claude Code plugin skills.
command-creator
davila7
This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.
agent-orchestration-improve-agent
sickn33
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.