BF adjudicator-trial-guide
This skill should be used when a judge, arbitrator, judicial assistant, or law student needs to apply Zou Bihua's "Nine-Step Method of Elements Trial" (要件审判九步法) in adjudicating or arbitrating civil and commercial cases. It is a five-phase adjudicator's workbench covering pre-trial preparation (Phase A: fixing claims, locating legal basis, analyzing elements), trial management (Phase B: claim retrieval, issue consolidation, evidence guidance), fact-finding (Phase C: fact determination and element subsumption), judgment writing (Phase D: eight consistencies audit), and judicial interpretation and values (Phase E: exercising the interpretation right correctly with value judgments). Triggers include 法官办案、仲裁员办案、庭审驾驭、仲裁庭审、要件九步法（裁判者视角）、心证形成、释明权、裁判文书说理、举证指导、争点整理（裁判者）、八个一致（裁判文书）、合议庭评议、仲裁庭评议.
This skill should be used when a judge, arbitrator, judicial assistant, or law student needs to apply Zou Bihua's "Nine-Step Method of Elements Trial"…
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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: This skill should be used when a judge, arbitrator, judicial assis… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - 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. 114 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1346 tokens
- 100Running it twice. No mutating operations
- low 11 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
- +1No license
- +2Single-language instructions
- +3Description length 793: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 114 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.