SKILLEMALL.ai
GitHub ↗ RU Sign in

CB contract-review

律师助理与法律助手、项目管理专家在审核合同、排查条款风险时必备。自动执行基础、商业、法律三层审查，仅添加批注不改原文，一键生成带批注合同、审查摘要、综合意见及业务流程图，让合同风控与业务梳理更高效专业。

anbeime/skill Agent Skills author: anbeime 27 files · 18 scripts body ≈ 1 220 tokens Open the sourcegithub.com↗ analyzed 27 h ago

律师助理与法律助手、项目管理专家在审核合同、排查条款风险时必备。自动执行基础、商业、法律三层审查，仅添加批注不改原文，一键生成带批注合同、审查摘要、综合意见及业务流程图，让合同风控与业务梳理更高效专业。

As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting

AnalyzerWordWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
74
Run on models
none yet
Process rating
B
65/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
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.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-privilege scripts/mermaid_renderer.py:190
    Privilege escalation / world-writable permissions (string literal in code, not executed)
    "--disable-setuid-sandbox",
    code literal

Files scanned: 27. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 65/100

  • 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
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 100Steps. 58 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1220 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

  • +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 101: 120–800 characters recommended
  • -39 of 9 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 58 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (7 of 7)
  • +1License stated

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