Add deny rules to clash policy with dry-run previews and confirmation.
npx skills add https://github.com/empathic/clash --skill deny
Please help me install this Agent Skill. Skill: deny Source: https://github.com/empathic/clash/tree/main/clash-plugin/skills/deny Command: npx skills add https://github.com/empathic/clash --skill deny
Block risky actions by adding a deny rule to the clash policy, ensuring denials take precedence over allows or prompts.
Ask Clash to add a deny rule to block a specific command, then confirm and apply.
High-intent search queries and answers about installing and using this skill.
To block risky commands using a clash policy, you add a deny rule that takes precedence over allows or prompts. This ensures specific tool invocations are blocked safely across profiles and scenarios.
Yes, you can preview a deny rule before applying it to your policy using the dry-run feature. This allows you to verify the exact rule and target profile before enforcing any changes.
Yes, a deny rule overrides existing allow rules in the clash CLI. Denials are designed to take precedence, ensuring that risky actions are strictly blocked even if prior allows exist.
The best way to enforce security permissions for specific command patterns is by adding targeted deny rules with explicit confirmation. This approach safely blocks risky tool invocations across all profiles.
You safely apply policy changes across multiple profiles by using the clash CLI with explicit confirmation. The system provides dry-run previews and safety rails to enforce rules immediately without unintended side effects.
empathicGenerate precise allow rules for Clash policy with dry-run validation.
empathicParse ~/.clash/policy.yaml and summarize default behavior, profiles, rules, and constraints.
empathicConvert Claude Code permissions into clash policy rules via the clash migrate command.
avivsinaiAutomate attendance and payslip tasks on Hilan accounts with dry-run previews and user confirmation before writes.
