CD 诉讼文书起草
专为诉讼律师、法务设计的 AI 文书起草助手。告别“对着空白文档发呆”和“满世界找模板”的痛苦。只需输入案件事实与己方立场（或直接丢入对方起诉状/证据目录），AI 将为你定制起草结构严谨的起诉状、答辩状、质证意见或律师函初稿。每一项诉讼主张和答辩理由，AI 都会自动为你匹配现行有效的法条及类案参考。直接输出可编辑的 Markdown/Word 格式，律师稍作修改即可定稿，大幅节省案头撰写时间。 Triggers: 起草答辩状、起草质证意见、起草律师函、起草起诉状、起草上诉状、draft litigation document
专为诉讼律师、法务设计的 AI 文书起草助手。告别“对着空白文档发呆”和“满世界找模板”的痛苦。只需输入案件事实与己方立场（或直接丢入对方起诉状/证据目录），AI 将为你定制起草结构严谨的起诉状、答辩状、质证意见或律师函初稿。每一项诉讼主张和答辩理由，AI 都会自动为你匹配现行有效的法条及类案参考。直接输出可编辑的…
As a process D 41/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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName"
Process rating: all ten parameters 41/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
- 40Consistency. Frontmatter name (诉讼文书起草) differs from the folder (cue-litigation-drafting)
- 60Tools and files. Uses tools (web, git) that frontmatter does not declare
- 100Steps. 9 steps
- 100Execution cost. Instruction body is 1234 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 265: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.