AF lawyer-case-strategist
This skill should be used when a lawyer handling civil or commercial cases (民商事律师) needs to analyze a case, build litigation strategy, review pleadings, prepare for trial, or predict judicial outcomes. It is a six-phase lawyer's full-lifecycle workbench based on Zou Bihua's "Nine-Step Method of Elements Trial" (要件审判九步法), covering case intake (Phase 0), claim construction (Phase 1), offense-defense deduction (Phase 2), document audit with "eight consistencies" check (Phase 3), trial rehearsal (Phase 4), and strategy review with judgment prediction (Phase 5). Triggers include 案件分析、案件初筛、要不要接案、请求权基础、要件九步法、抗辩检索、争点整理、八个一致、庭审预演、裁判预判、案件复盘、起诉状核验、代理词核验.
This skill should be used when a lawyer handling civil or commercial cases (民商事律师) needs to analyze a case, build litigation strategy, review pleadings…
As a process F 35/100 · Will not run — References files that are not bundled: assets/avatar.png
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/avatar.png - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: assets/avatar.png
- 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. 104 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1505 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
- +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
- +5Description quotes 2 example trigger phrases
- +3Description length 651: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 104 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.