AC litigation-intake-assessment
生成中国大陆争议解决与诉讼管理场景下的《案件初步评估报告》，适用于接案评估阶段对案件基本事实、初步证据材料、我方诉求和管辖法院信息进行结构化梳理、法律关系识别、风险标注、司法裁判检索，并量化估算胜诉概率、诉讼周期、资金与时间成本。当用户提到接案评估、案件初评、是否接案、胜诉率预估、诉讼周期预估、办案成本测算、争议焦点梳理、证据短板识别或补证建议时使用本 Skill。
As a process C 51/100 · Has gaps — 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.
For the model run — optional
- 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 51/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. 4 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 72 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1174 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 184: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 72 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.
External checks
ClawHub: suspicious
This legal intake skill is mostly purpose-aligned, but it sends sensitive legal queries and an API key to a third-party service while disabling normal HTTPS verification.
LLM: suspicious (high) · VirusTotal: · 29 May 2026