empathic
Official@empathic
Manage and validate granular permission policies for Claude Code environments using structured YAML configuration and audit analysis.
Agent Skills by empathic
Showing 11 vetted skills indexed across 1 GitHub repositories.
explain
Explain which policy rule matches a given tool invocation.
allow
Generate precise allow rules for Clash policy with dry-run validation.
test
Test Clash policy against hypothetical tool invocations to verify allowed, denied, or approval actions.
status
Report Clash permission policy status, file location, and active rules.
onboard
Guide users through interactive Clash policy onboarding for Claude Code.
describe
Parse ~/.clash/policy.yaml and summarize default behavior, profiles, rules, and constraints.
edit
Edit clash policy rules in ~/.clash/policy.yaml with dry-run previews.
deny
Add deny rules to clash policy with dry-run previews and confirmation.
migrate
Convert Claude Code permissions into clash policy rules via the clash migrate command.
audit
Parse audit JSONL files into readable tables of permission decisions.
dogfood
Configure Clash with a safe default policy at ~/.clash/policy.yaml.
Frequently Asked Questions About empathic
FAQPage SchemaWhat specific security tasks does this organization enable?▼
These capabilities enable the management, validation, and auditing of Clash policy files. Users can generate allow or deny rules, perform dry-run validations of policy changes, and parse audit logs to verify permission decisions within Claude Code environments.
Which technical personas benefit from these capabilities?▼
Security engineers and developers managing Claude Code environments benefit from these capabilities. They are designed for technical users who need to enforce strict access controls, maintain policy consistency across environments, and troubleshoot permission denials through structured configuration management.
What are the prerequisites for implementing these policies?▼
Implementation requires an existing Claude Code environment and the presence of a policy configuration file located at ~/.clash/policy.yaml. Users must have read and write access to this directory to utilize the editing, migration, and validation functions provided.