openclaw/reporting-governance-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

skills: explain kal intake fields

Browse Source
This commit is contained in:
Eve
2026-04-16 16:48:38 +08:00
parent 1c16de7122
commit 18f0bf6049
1 changed files with 16 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
skills/kal/SKILL.md
View File

@@ -9,7 +9,7 @@ When this skill triggers, first collect the minimum input needed for a KAL run,
## Primary behavior
If the user says only `啟動KAL` or gives an incomplete kickoff, use a friendly intake reply: one short lead-in sentence plus the same 4-line template.
If the user says only `啟動KAL` or gives an incomplete kickoff, use a friendly intake reply: one short lead-in sentence plus the same 4-line template, followed by short field guidance.
Default wording:
@@ -19,6 +19,12 @@ topic: ""
seed: ""
goal: ""
scope: ""
說明：
- topic：你想研究的主題是什麼
- seed：先給我起始材料，例如網址 / repo / 關鍵字 / 文件
- goal：你最後想得到什麼，例如摘要 / 比較 / 評估 / 決策建議
- scope：要納入或排除什麼範圍
```
Keep the lead-in short and natural. Do not add analysis yet.
@@ -32,11 +38,13 @@ Keep the lead-in short and natural. Do not add analysis yet.
## Response rules
- If the user only says `啟動KAL`, return one short friendly lead-in sentence plus the 4-line template.
- If the user gives some fields but not all, return the same template with known values filled in and missing ones left empty; a short natural lead-in is allowed.
- If the user only says `啟動KAL`, return one short friendly lead-in sentence plus the 4-line template and short field explanations.
- If the user gives some fields but not all, return the same template with known values filled in and missing ones left empty; a short natural lead-in is allowed, and keep the short explanations.
- If the user provides enough information, normalize it into the 4-line template and then proceed with the KAL workflow.
- Keep the intake step lightweight.
- Do not add unnecessary analysis before the intake is clear.
- If the user explicitly asks how to fill the fields, always include the explanation block.
- If the user explicitly asks for raw copy-paste format only, you may omit the explanation block.
## Filled-template behavior
@@ -86,3 +94,8 @@ seed: "..."
goal: "..."
scope: "..."
```
- The explanation block belongs below the 4 fields by default.
- For chat surfaces, short bullets are preferred over tables.
- Do not turn intake into a long questionnaire.
- Keep it to one short lead-in, the 4 fields, and brief field hints.