SKILLEMALL.ai
GitHub ↗ RU Sign in

BC cue-litigation-lawyer-assistant

专为从事民商事及刑事诉讼的执业律师、法务打造的 AI 案头助手。将繁琐的“查、核、算、写”工作交由 AI 处理——支持秒级调用 MCP 检索现行法规原文；更支持深度研判：合同审查、疑难案件类案检索、复杂赔偿金/诉讼费自动理算、诉讼文书高质量起草与仿写、深度文书审校（自动核验法条效力与案号真伪）。直连北大法宝等权威法律数据库，产出结论均附原始链接，助力法律人大幅节省案头时间。

ClawHub Hermes author: panting09266-ai v1.7.0 MIT-0 2 files body ≈ 2 515 tokens Open the sourceclawhub.ai↗ analyzed 31 h ago

专为从事民商事及刑事诉讼的执业律师、法务打造的 AI 案头助手。将繁琐的“查、核、算、写”工作交由 AI 处理——支持秒级调用 MCP…

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureWordLegaltype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 189 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "display_name"
  • note frontmatter-key unknown frontmatter key "display_name_en"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "description_zh"
  • note frontmatter-key unknown frontmatter key "description_en"
  • note frontmatter-key unknown frontmatter key "trigger_words"

Process rating: all ten parameters 58/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. No external tools needed
  • 100Steps. 43 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2515 tokens
  • 100Running it twice. No mutating operations
  • low 10 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
  • -229 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 188: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 43 items
  • +4Has examples (8 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.

External checks

ClawHub: suspicious
This legal-assistant skill is coherent in purpose but asks the agent to handle credentials, upload confidential legal files, modify client configuration, and run unpinned remote code in ways users should review carefully before installing.
LLM: suspicious (high) · 15 Sept 2026