---
name: explain-skill
description: Use this skill whenever the user asks to explain, analyze, or detail how another skill works, its core mechanisms, design rationale, or wants to learn tips and tricks for using it effectively.
---

# Explain Skill

This skill is designed to help you analyze and explain another skill in the user's workspace. When invoked, follow these steps to provide a comprehensive explanation of the target skill.

## 1. Read Target Skill
- Identify the target skill from the user's request.
- Use the `view_file` tool to read the target skill's `SKILL.md` file (typically located in `<appDataDir>/skills/<target-skill>/SKILL.md`).
- If the skill has other important files (like scripts or reference files), read those as well to gain a deep understanding.

## 2. Analysis & Output
Output your analysis to the user using the following structured format constraint:

### 🎯 1. Purpose
Briefly and clearly explain what the target skill does and in what scenarios it is designed to be triggered. If it solves a specific problem, describe what that problem is.

### ⚙️ 2. Core Mechanism & Design Rationale
- **Core Mechanism**: Detail the step-by-step workflow, tools used, and the overall logic of the skill. How does it get things done?
- **Design Rationale**: Explain the "why" behind the mechanism. Highlight how it is designed to ensure the mechanism works correctly (e.g., how it handles edge cases, specific prompt engineering techniques to avoid AI hallucinations, its approach to progressive disclosure, or fail-safes).

### 💡 3. Tips & Clever Tricks
- **Tips**: Share practical tips for the user on how they can best utilize or interact with this skill to get the most value out of it.
- **Clever Tricks**: Point out any neat design choices in the skill's instructions—such as how it manages context limits, parses output, interacts with the user, or uses theory of mind to guide the model.

### 📝 4. Summary & Takeaways
- **Design Takeaways**: Summarize the key design ideas or expression methods from "Core Mechanism & Design Rationale" and "Tips & Clever Tricks" that can be applied or adapted when creating other skills. What makes this skill well-written or effective?
- **Reference Examples**: Provide concrete examples of these takeaways. For instance, if the skill uses a clever validation prompt, extract that specific prompt block as a reusable example.

## Interaction Principles
- Keep the tone informative, insightful, and structure the content clearly using markdown.
- Quote or reference specific parts of the target skill's instructions to back up your analysis.
- Use English for the response content.