SKILLEMALL.ai
GitHub ↗ RU Sign in

BF shuzhi-open

数秦开放平台统一接口封装，支持区块链API服务、自动化取证、保管单组件、电子签章

ClawHub Agent Skills author: alex098929 v1.0.3 MIT-0 32 files body ≈ 3 714 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 35/100 · Will not run — References files that are not bundled: {preview_url}, {sign_url}

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: {preview_url}, {sign_url}
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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. The text references files that are not there: add them or drop the references.
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: 32. 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")
  • warning missing-ref reference to a missing file: {preview_url}
  • warning missing-ref reference to a missing file: {sign_url}
  • note frontmatter-key unknown frontmatter key "keywords"

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: {preview_url}, {sign_url}
  • 0Tools and files. 2 referenced file(s) missing: {preview_url}, {sign_url}
  • 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. 63 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3714 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)
  • +3Description length 40: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -232 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 64 headings
  • +3Step-by-step instructions: 63 items
  • +4Has examples (46 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

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

External checks

ClawHub: suspicious
This skill matches its stated legal evidence and e-signature purpose, but it handles sensitive identity and contract data with under-scoped privacy controls that warrant Review before installation.
LLM: suspicious (high) · VirusTotal: · 29 May 2026