SKILLEMALL.ai
GitHub ↗ RU Sign in

CD legal-assistant-pro

(no description)

ClawHub Hermes author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 4 060 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

1. 识别用户需求属于NDA审查/版本对比/引文核验/会议简报/状态报告中的哪一类 2. 确认输入文档格式(支持 .docx/.pdf/.txt/.md)

As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationWordResearchtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
C
70/100
safety, quality, tests
Safety 60%
100
Quality 40%
24
Run on models
none yet
Process rating
D
44/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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

  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit keys need to be on a single line at line 2, column 1: name: legal-assistant-pro | ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 44/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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
  • 40Consistency. Frontmatter name (legal-assistant-pro) differs from the folder (legal-doc-reviewer)
  • 70Execution cost. Instruction body is 4060 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 56 steps
  • 100Running it twice. No mutating operations
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 18 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)
  • +3Description length 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 46 headings
  • +3Step-by-step instructions: 56 items
  • +4Has examples (12 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This legal document helper is mostly coherent, but it asks for broad command execution and writes or logs sensitive legal work without clear user-control boundaries.
LLM: suspicious (high) · VirusTotal: · 20 Aug 2026