SKILLEMALL.ai
GitHub ↗ RU Sign in

BF compliance-sentinel-claw

合规哨兵监控虾。监控合作方（供应商/客户）的工商异动、法律诉讼、失信记录等合规风险，7×24 小时守望预警。 触发场景： - 合作方准入审查（签约前查询工商、诉讼、失信记录） - 持续监控预警（对已签约合作方定期监控，异动时推送飞书通知） - 批量风险扫描（对供应商库/客户库批量合规检查） - 风险等级评估（给合作方打分，识别高风险对象） 触发关键词：合规监控、合作方风险、工商异动、诉讼监控、失信名单、经营异常、股权冻结、风险预警、尽职调查、供应商审查

ClawHub Agent Skills author: Ricky v1.0.0 MIT-0 6 files body ≈ 342 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process F 35/100 · Will not run — References files that are not bundled: scripts/compliance-monitor.sh

ProcedureInfrastructureSecuritytype 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
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: scripts/compliance-monitor.sh
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: 6. 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: scripts/compliance-monitor.sh

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: scripts/compliance-monitor.sh
  • 0Tools and files. 1 referenced file(s) missing: scripts/compliance-monitor.sh
  • 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. 31 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 342 tokens
  • 100Running it twice. No mutating operations

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
  • +4No input/output examples
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 228: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 31 items
  • +4Reference files are cited in the instructions (3 of 3)

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

External checks

ClawHub: clean
This skill is a coherent partner compliance monitoring helper that uses disclosed Feishu storage and alerts, but users should manage sensitive partner data carefully.
LLM: benign (high) · VirusTotal: · 29 May 2026