Configure Clash with a safe default policy at ~/.clash/policy.yaml.
npx skills add https://github.com/empathic/clash --skill dogfood
Please help me install this Agent Skill. Skill: dogfood Source: https://github.com/empathic/clash/tree/main/clash-plugin/skills/dogfood Command: npx skills add https://github.com/empathic/clash --skill dogfood
Initial Clash setups are error-prone and time-consuming when teams must define a safe baseline policy before sophisticated rules exist.
Run the clash init command to create a safe-default policy.
High-intent search queries and answers about installing and using this skill.
Initializing Clash with a safe default policy requires running the clash init command, which deterministically creates a baseline configuration at ~/.clash/policy.yaml to enforce basic safety.
A safe default policy in Clash restricts dangerous operations before sophisticated rules exist. It provides a ready-to-use baseline to enforce basic safety and ensures deterministic initialization during developer onboarding.
You need a baseline policy for initial Clash setup because defining safe rules manually is error-prone. It accelerates team onboarding by providing immediate policy enforcement and a concrete configuration to start from.
The default Clash policy file is created at ~/.clash/policy.yaml. After initialization, the process provides a clear explanation of what was created and what adjustments are needed next.
Yes, you can use the default Clash policy for team onboarding. It accelerates team adoption by providing a ready-to-use baseline policy that enforces basic safety across developer environments immediately.
vnmoorthyInstall and configure the gbrain CLI with local brain initialization and MCP registration.
empathicParse ~/.clash/policy.yaml and summarize default behavior, profiles, rules, and constraints.
latchagentSandbox macOS agent shells with filesystem and network restrictions.
empathicReport Clash permission policy status, file location, and active rules.
