BD team-tasks
在用户明确要求管理团队任务台账或调用 team-tasks 时使用。 提供本地 JSON 任务存储、更新、评论、归档、备份与受限恢复，以及批量和专项的风险提醒解析。 任务变更会原子写入可重试的提醒同步事件，供调度适配器维护规则关联并动态投递；调度、通知及身份权限检查仍由外部适配器负责。 不用于一般任务管理讨论、翻译或仅在引用材料中出现任务的场景。
在用户明确要求管理团队任务台账或调用 team-tasks 时使用。 提供本地 JSON 任务存储、更新、评论、归档、备份与受限恢复，以及批量和专项的风险提醒解析。 任务变更会原子写入可重试的提醒同步事件，供调度适配器维护规则关联并动态投递；调度、通知及身份权限检查仍由外部适配器负责。…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 78 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3192 tokens
- low 28 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 174: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 78 items
- +4Has examples (18 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.