skill-creation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Frontmatter

```
name
```
— kebab-case, matches the folder name
```
description
```
— trigger mechanism, not a summary
- Always use YAML block scalar (
```
>-
```
  ) — never write the description as an inline string
- Write as "Use this skill whenever [condition]..."
- End with "Do not wait for an explicit request — if [condition], this skill applies." unless the skill is only valid when explicitly triggered by the user
- No implementation notes or process guidance — trigger conditions only

```
name
```
— kebab-case格式，与文件夹名称保持一致
```
description
```
— 触发机制说明，而非内容摘要
- 始终使用YAML块标量（
```
>-
```
  ）——绝对不要把description写为行内字符串
- 写作格式为「Use this skill whenever [condition]...」
- 以「Do not wait for an explicit request — if [condition], this skill applies.」结尾，除非该skill仅在用户明确触发时才生效
- 不要包含实现说明或流程指引——仅描述触发条件

Body

Write directives, not descriptions — tell the agent what to do, not what the skill is about
Keep everything needed to execute the task inside the skill file
If external docs are referenced, name them explicitly
Keep under 500 lines — split large reference content into separate files

撰写指令而非描述内容——告诉Agent要做什么，而非介绍skill的用途
将执行任务所需的所有内容都放在skill文件内
如果引用了外部文档，请明确标注其名称
内容控制在500行以内——如果参考内容体量较大，请拆分到独立文件中

Example

yaml

---
name: skill-name
description: >-
  Use this skill whenever [condition]. Do not wait for an explicit
  request — if [condition], this skill applies.
---

yaml

---
name: skill-name
description: >-
  Use this skill whenever [condition]. Do not wait for an explicit
  request — if [condition], this skill applies.
---

Section

Directive one
Directive two

undefined

Directive one
Directive two

undefined