writing-hookify-rules Skill
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. Published by anthropics in claude-plugins-official.
Decision snapshot
Is this a fit?
Documentation, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
24 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is writing-hookify-rules Skill?
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. Published by anthropics in claude-plugins-official. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Writing
- Documentation use cases
- Writing use cases
Declared skill metadata
- Source file: plugins/hookify/skills/writing-rules/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use writing-hookify-rules Skill
- Use it for documentation.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-plugins-official
- Skill file: plugins/hookify/skills/writing-rules/SKILL.md
What it does
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.
Skill instructions
Writing Hookify Rules Overview Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in .claude/hookify.{rule-name}.local.md files. Rule File Format Basic Structure markdown --- name: rule-identifier enabled: true event: bash|file|stop|prompt|all pattern: regex-pattern-here --- Message to show Claude when this rule triggers. Can include markdown formatting, warnings, suggestions, etc. Frontmatter Fields name (required): Unique identifier for the rule - Use kebab-case: warn-dangerous-rm, block-console-log - Be descriptive and action-oriented - Start with verb: warn, prevent, block, require, check enabled (required): Boolean to activate/deactivate - true: Rule is active - false: Rule is disabled (won't trigger) - Can toggle without deleting rule event (required): Which hook event to trigger on - bash: Bash tool commands - file: Edit, Write, MultiEdit tools - stop: When agent wants to stop
Verified compatibility and discovery
Frequently asked questions
What is writing-hookify-rules?
writing-hookify-rules is a open-source AI agent skill with Copy skill directory. 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.
Who is writing-hookify-rules best for?
writing-hookify-rules is best for reusing agent instructions, scripts, and references, documentation workflows, writing workflows.
How do I install writing-hookify-rules?
Install or run writing-hookify-rules using Copy skill directory. Check writing-hookify-rules for the latest setup command.
Is writing-hookify-rules actively maintained?
writing-hookify-rules may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
