SKILLEMALL.ai

AC process-data-monitor-claw

过程数据监控虾 — 实时监控业务运行中的全链路数据状态,像雷达一样扫描业务流程每个节点,第一时间发现异常并告警。 **当以下情况时使用此 Skill**: (1) 需要监控业务流程节点状态(订单履约、库存同步、支付链路、数据管道等) (2) 需要设置数据异常阈值告警(数值超限、状态卡顿、趋势恶化) (3) 需要配置多渠道告警推送(飞书群/私信、邮件、短信) (4) 需要生成监控报告(日报/周报,异常汇总、响应时效) (5) 用户提到"监控"、"实时监控"、"链路追踪"、"异常检测"、"告警"、"预警"、"数据状态"、"流程监控"、"业务监控"、"全链路"、"节点状态" **典型触发示例**: - "帮我监控订单履约流程,超过24小时未发货就告警" - "实时监控库存同步状态,发现差异立即通知" - "监控支付成功率,低于95%立即预警" - "设置数据管道监控,ETL任务失败立即告警"

ClawHub Agent Skills author: Ricky v1.0.0 MIT-0 7 files · 2 scripts body ≈ 382 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
99
Quality 40%
84
Run on models
none yet
Process rating
C
51/100
Has gaps
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
  • 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-background-process scripts/monitor-daemon.sh:31
    Starts a background / autostarted process
    nohup bash "$0" _run >> "$LOG_FILE" 2>&1 &

Files scanned: 7. 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 51/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
  • 30Running it twice. 2 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 15 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 382 tokens

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 400: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 15 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 2 scripts are documented

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

External checks

ClawHub: clean
This skill is a disclosed business monitoring and Feishu alerting helper, with expected operational risk that should be controlled through careful configuration.
LLM: benign (high) · VirusTotal: · 29 May 2026