SKILLEMALL.ai

BD lexseek

法索 AI 法律助手,提供法律条文检索功能。当用户询问法律问题、查询法规条文、查找司法解释、了解法律条款内容时自动触发。包括:查询特定法律(如劳动法、合同法、民法典)、根据案件情况检索相关法律依据、了解某个法律概念的具体规定等。

ClawHub Agent Skills author: daixin877889 v1.0.0 MIT-0 6 files body ≈ 831 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
72
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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.
For the model run — optional
  • 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 Obfuscation obf-hex-escape-chain scripts/lexseek.js:1
    Escaped/char-code string obfuscation (detector / deny-list definition; security demo / example)
    const fs=require('fs'),path=require('path'),readline=require('readline'),APIConstants={'BASE_URL':'https://api.lexseek.cn','ENDPOINTS':{'LOGIN':'/api/v1/auth/login/password','SEARCH_LAW':'/api/v1/skil
    detectordemo

Files scanned: 5. 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 46/100

  • 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
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 100Steps. 81 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 831 tokens
  • 100Running it twice. No mutating operations
  • medium 11 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

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 114: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 81 items
  • +4Reference files are cited in the instructions (2 of 2)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This legal-search skill appears tied to a real external service, but it asks users for account passwords through chat/CLI and stores an API key locally in plaintext.
LLM: suspicious (high) · VirusTotal: malicious · 28 May 2026