Writing Hookify Rules
Create Reliable Hookify Rules
Hookify rules can fail when events, conditions, or regex patterns are unclear. This skill guides users toward precise rules with useful warnings and blocks.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "Writing Hookify Rules" from https://skillstore.io/skills/davila7-writing-hookify-rules.md and its manifest at https://skillstore.io/api/skills/davila7-writing-hookify-rules/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "Writing Hookify Rules". Warn when console logging is added to TypeScript files.
Expected outcome:
A file-event rule using path and new-text conditions, followed by a message recommending the project logging library.
Using "Writing Hookify Rules". Block recursive deletion commands.
Expected outcome:
A bash-event rule with a focused recursive-deletion pattern, blocking action, and guidance to verify the target path.
Using "Writing Hookify Rules". Require checks before the agent stops.
Expected outcome:
- A stop-event rule that matches completion attempts.
- A short checklist covering tests, build status, and documentation.
Security Audit
SafeAll 116 static findings are false positives caused by Markdown formatting and illustrative detection patterns. The skill contains guidance, not executable automation. No prompt injection or malicious intent was found.
Risk Factors
⚡ Contains scripts (2)
⚙️ External commands (50)
🔑 Env variables (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/davila7-writing-hookify-rules/audits/12?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-writing-hookify-rules?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-writing-hookify-rules?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-writing-hookify-rules/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-writing-hookify-rules.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
davila7. (2026). Writing Hookify Rules security audit report (audit version 12) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/davila7-writing-hookify-rules/audits/12BibTeX citation
@techreport{davila7-davila7-writing-hookify-rules-2026,
author = {davila7},
title = {Writing Hookify Rules security audit report (audit version 12)},
institution = {Skillstore},
year = {2026},
number = {12},
url = {https://skillstore.io/skills/davila7-writing-hookify-rules/audits/12},
note = {Author version 0.1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "Writing Hookify Rules security audit report (audit version 12)"
version: "0.1.0"
type: report
authors:
- name: "davila7"
date-released: "2026-07-19"
url: "https://skillstore.io/skills/davila7-writing-hookify-rules/audits/12"
identifiers:
- type: other
value: "skillstore:davila7-writing-hookify-rules:audit:12"
description: "Skillstore immutable audit report identifier"
Compare variants
4 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
writing-hookify-rules
2026-08-21
anthropics-writing-hookify-rules
2026-08-21
captaincrouton89-writing-hookify-rules
2026-08-21
davila7-writing-hookify-rules
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prevent unsafe commands
Create blocking rules for destructive shell commands while allowing normal development commands.
Enforce completion checks
Add stop rules that remind agents to run tests, builds, and documentation checks.
Protect sensitive files
Warn when edits target environment files, credentials, certificates, or other protected paths.
Try These Prompts
Create a Hookify warning rule for console logging in TypeScript files. Explain the event, pattern, and message.
Write a Hookify rule that blocks recursive deletion commands. Include a focused regex and a safer alternative.
Create a file rule that warns when API key assignments are added to environment files. Use multiple conditions.
Design three coordinated Hookify rules for command safety, production deployment prompts, and completion checks. Minimize false matches and explain tradeoffs.
Best Practices
- Test patterns against examples that should match and examples that should not match.
- Use narrow event types and conditions before choosing broad all-event rules.
- Write messages that explain the risk and provide a practical next action.
Avoid
- Do not use broad patterns that match unrelated commands, paths, or words.
- Do not block operations when a warning provides enough protection.
- Do not store local Hookify rules in version control without reviewing repository policy.