BF lawyer-litigation-workflow
【深度模拟律师办案逻辑】将真实律师的完整办案思维链编码为7步自动化管线。 不是简单的模板填充——从案由输入开始，系统像一位资深诉讼律师一样思考： IRAC法律推理→争议焦点提炼→类案检索比对→法条穷尽检索→红蓝对抗策略分析→ 法官中立审视→全案一致性审计。每份文书经过7项QC质量门控，绝不放过一个占位符残留。 核心亮点：(1)规格驱动文书生成管道——起诉状/答辩状/代理词/证据目录等11类文书， 从模板安全替换到叙事填充全自动；(2)对抗式诉讼策略——模拟对方反驳、法官倾向、 胜诉概率量化；(3)多层质量闭环——模板来源校验+字体一致性+占位符扫描+骨架完整性+ 当事人覆盖检查，任一不通过即硬阻断。让AI真正像律师一样办案，而不是像打字员一样填表。 触发词：起诉、应诉、答辩、代理词、证据目录、诉讼策略、类案检索、民事案件、 买卖合同纠纷、借贷纠纷、租赁纠纷、劳动争议。
【深度模拟律师办案逻辑】将真实律师的完整办案思维链编码为7步自动化管线。 不是简单的模板填充——从案由输入开始，系统像一位资深诉讼律师一样思考： IRAC法律推理→争议焦点提炼→类案检索比对→法条穷尽检索→红蓝对抗策略分析→ 法官中立审视→全案一致性审计。每份文书经过7项QC质量门控，绝不放过一个占位符残留。…
As a process F 35/100 · Will not run — References files that are not bundled: assets/workflow_specs/{文书}_spec.json
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Bash Write Glob Grep WebFetch WebSearch
Files scanned: 2. 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") - warning
missing-refreference to a missing file: assets/workflow_specs/{文书}_spec.json
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: assets/workflow_specs/{文书}_spec.json
- 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
- 100Steps. 81 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1658 tokens
- 100Running it twice. No mutating operations
- low 12 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
- -47 reference files, but SKILL.md never points to them: the model will not open them
- -35 of 10 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 389: enough signal without eating the budget
- +4Structure: 54 headings
- +3Step-by-step instructions: 81 items
- +4Has examples (13 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.