describe

Parse ~/.clash/policy.yaml and summarize default behavior, profiles, rules, and constraints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explain active Clash policy in plain-English terms by reading the local policy file and translating rules into understandable language for policy owners and operators.

Core Features & Use Cases

  • Converts the policy.yaml definitions (default behavior, profiles, and rules) into a human-readable summary.
  • Highlights potential gaps or ambiguities in the policy to support compliance reviews and risk assessment.
  • Helps communicate security posture to stakeholders without needing YAML fluency.

Quick Start

Describe the current policy in plain English by invoking the describe skill.

Frequently Asked Questions about describe

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

FAQPage Schema
How do I explain clash policy.yaml rules in plain English?

To explain clash policy.yaml rules in plain English, the Skill parses your local configuration and translates default behavior, profiles, and constraints into a human-readable structured summary for operators.

What is the best way to audit local clash policy configurations for compliance?

The best way to audit local clash policy configurations for compliance is to generate a plain-English summary that highlights potential gaps, ambiguities, and filesystem constraints directly from your policy.yaml file.

Can I translate clash security rules for stakeholders without YAML fluency?

Yes, you can translate clash security rules for stakeholders without YAML fluency by converting the policy.yaml definitions into a natural language summary that clearly communicates the current security posture.

How do I identify potential issues in my clash policy.yaml?

You identify potential issues in your clash policy.yaml by parsing the file to detect gaps, ambiguities, and filesystem constraints, producing a structured report that flags risks for review.

Does the policy explanation tool require specific dependencies to read local clash configurations?

No, the policy explanation tool requires no external dependencies to read local clash configurations, directly parsing the ~/.clash/policy.yaml file to output its structured plain-English summary.