How do I install the Ancplua Ancplua Claude Plugins Writing Rules skill?

Run npx skillmds@latest add tomevault-io/ancplua-ancplua-claude-plugins-writing-rules in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ancplua Ancplua Claude Plugins Writing Rules skill do?

Writing Hookify Rules It is listed under Coding & Dev Tools on SkillMD.

Is Ancplua Ancplua Claude Plugins Writing Rules safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ancplua Ancplua Claude Plugins Writing Rules?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ancplua Ancplua Claude Plugins Writing Rules free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ancplua Ancplua Claude Plugins Writing Rules?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ancplua Ancplua Claude Plugins Writing Rules by tomevault-io

Name: Ancplua Ancplua Claude Plugins Writing Rules
Author: tomevault-io

File contents

Writing Hookify Rules

When to Use

User asks to create, write, or configure hookify rules
User wants to prevent specific behaviors in Claude Code

Process

Identify the behavior to prevent
Choose the event type (bash, file, stop, prompt, all)
Write the pattern (regex or conditions)
Create the rule file in .claude/hookify.{name}.local.md
Test immediately — rules take effect on next tool use

Rule File Format

---
name: rule-identifier
enabled: true
event: bash|file|stop|stopfailure|prompt|all
pattern: regex-pattern-here
---

Message shown to Claude when rule triggers.

Event Types

Event	Matches Against	Use For
`bash`	Command text	Dangerous commands, privilege escalation
`file`	File path + content	Debug code, sensitive files, security risks
`stop`	Always (use `.*`)	Completion checklists, required steps
`stopfailure`	`error_type`, `error_message`	API error alerts, rate limit handling
`prompt`	User prompt text	Deployment gates, process enforcement
`all`	All events	Cross-cutting concerns

Actions

warn (default): Show message, allow operation
block: Prevent operation entirely

Advanced: Multiple Conditions

conditions:
  - field: file_path
    operator: regex_match
    pattern: \.env$
  - field: new_text
    operator: contains
    pattern: API_KEY

Operators: regex_match, contains, equals, not_contains, starts_with, ends_with

Fields: bash → command | file → file_path, new_text, old_text, content | prompt → user_prompt

All conditions must match for the rule to trigger.

File Organization

Location: .claude/hookify.{descriptive-name}.local.md
Gitignore: Add .claude/*.local.md to .gitignore
Naming: Start with verb: warn-dangerous-rm, block-console-log, require-tests

See references/ for regex patterns, examples, and common pitfalls.

If Connectors Available

~~github~~ Commit generated rule files and open a PR for team review
~~slack~~ Notify the team when a new blocking rule is added to the project
~~linear~~ Track rule creation as a task linked to the behavior it guards against

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: ancplua-ancplua-claude-plugins-writing-rulesdescription: Writing Hookify Rules---# Writing Hookify Rules## When to Use- User asks to create, write, or configure hookify rules- User wants to prevent specific behaviors in Claude Code## Process1. **Identify the behavior** to prevent2. **Choose the event type** (bash, file, stop, prompt, all)3. **Write the pattern** (regex or conditions)4. **Create the rule file** in `.claude/hookify.{name}.local.md`5. **Test immediately** — rules take effect on next tool use## Rule File Format```markdown---name: rule-identifierenabled: trueevent: bash|file|stop|stopfailure|prompt|allpattern: regex-pattern-here---Message shown to Claude when rule triggers.```## Event Types| Event | Matches Against | Use For ||-------|----------------|---------|| `bash` | Command text | Dangerous commands, privilege escalation || `file` | File path + content | Debug code, sensitive files, security risks || `stop` | Always (use `.*`) | Completion checklists, required steps || `stopfailure` | `error_type`, `error_message` | API error alerts, rate limit handling || `prompt` | User prompt text | Deployment gates, process enforcement || `all` | All events | Cross-cutting concerns |## Actions- `warn` (default): Show message, allow operation- `block`: Prevent operation entirely## Advanced: Multiple Conditions```yamlconditions: - field: file_path operator: regex_match pattern: \.env$ - field: new_text operator: contains pattern: API_KEY```**Operators:** `regex_match`, `contains`, `equals`, `not_contains`, `starts_with`, `ends_with`**Fields:** bash → `command` | file → `file_path`, `new_text`, `old_text`, `content` | prompt → `user_prompt`All conditions must match for the rule to trigger.## File Organization- **Location:** `.claude/hookify.{descriptive-name}.local.md`- **Gitignore:** Add `.claude/*.local.md` to `.gitignore`- **Naming:** Start with verb: `warn-dangerous-rm`, `block-console-log`, `require-tests`See `references/` for regex patterns, examples, and common pitfalls.## If Connectors Available- ~~github~~ Commit generated rule files and open a PR for team review- ~~slack~~ Notify the team when a new blocking rule is added to the project- ~~linear~~ Track rule creation as a task linked to the behavior it guards against---> Converted and distributed by [TomeVault](https://tomevault.io/claim/ancplua) — claim your Tome and manage your conversions.

Frequently asked questions

Ancplua Ancplua Claude Plugins Writing Rules