allow

Generate precise allow rules for Clash policy with dry-run validation.

33|5|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/empathic/clash --skill allow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: allow
Source: https://github.com/empathic/clash/tree/main/clash-plugin/skills/allow
Command: npx skills add https://github.com/empathic/clash --skill allow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clash policy management is manual and error-prone when granting specific tool permissions; this Skill guides users to craft precise allow rules that align with their security posture.

Core Features & Use Cases

  • Generate focused allow rules for tool invocations in Clash's policy.
  • Propose safe constraints and dry-run steps to validate changes before applying.
  • Use-case: when you need to permit a subset of commands like "bash git *" while denying dangerous actions.

Quick Start

Quickly add an allow rule to your policy to grant safe operations while preserving security.

Frequently Asked Questions about allow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add allow rules to Clash policy for specific bash commands without compromising security?

Adding allow rules to Clash policy involves constructing precise permissions for specific tool invocations like bash, validating changes through a dry-run preview, and deploying via the Clash CLI while preserving deny-first safety semantics.

What is the safest way to permit filesystem access for git in a Clash security policy?

The safest way to permit filesystem access in a Clash security policy is crafting focused allow rules that grant selective access to safe operations, followed by a structured workflow of dry-run validation and user confirmation before final deployment.

Can I test Clash policy changes before applying them to live permissions?

Yes, you can test Clash policy changes by using a dry-run preview step to validate the proposed allow rules before applying them, ensuring that deny-first safety semantics are preserved and dangerous actions are blocked prior to final deployment.

How do Clash allow rules handle selective tool invocations while denying dangerous actions?

Clash allow rules handle selective tool invocations by generating focused permissions that permit safe subsets of commands like bash git star, while the underlying deny-first safety semantics automatically block dangerous actions outside the allowed scope.

Does Clash policy support allowing a subset of shell tool commands while restricting others?

Clash policy supports allowing a subset of shell tool commands by applying precise allow rules tailored to common shell tools, enabling safe usage of specific operations while maintaining a restrictive security posture for unauthorized actions.

Why do my Clash policy allow rules fail to prevent dangerous bash actions?

Clash policy allow rules may fail if not precisely constructed; the Skill enforces a structured workflow with rule construction and dry-run previews to ensure dangerous bash actions remain denied under the deny-first safety semantics.