SKILLEMALL.ai
GitHub ↗ RU Sign in

BF jf-garbage-inspection

杰峰垃圾溢出巡检技能。通过杰峰监控设备抓图，Agent 直接看图分析垃圾桶是否溢出，输出结构化巡检报告。支持单设备/批量巡检和定时任务。

ClawHub Agent Skills author: jftech v1.0.0 MIT-0 5 files body ≈ 1 642 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

杰峰垃圾溢出巡检技能。通过杰峰监控设备抓图，Agent 直接看图分析垃圾桶是否溢出，输出结构化巡检报告。支持单设备/批量巡检和定时任务。

As a process F 31/100 · Will not run — References files that are not bundled: scripts/capture_and_download.py, scripts/crypto.py

ProcedureSoftware developmentAI and agentstype 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%
60
Run on models
none yet
Process rating
F
31/100
Will not run
References files that are not bundled: scripts/capture_and_download.py, scripts/crypto.py
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: 0. 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/capture_and_download.py
  • warning missing-ref reference to a missing file: scripts/crypto.py

Process rating: all ten parameters 31/100

Will not run. References files that are not bundled: scripts/capture_and_download.py, scripts/crypto.py
  • 0Tools and files. 2 referenced file(s) missing: scripts/capture_and_download.py, scripts/crypto.py
  • 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
  • 40Consistency. Frontmatter name (jf-garbage-inspection) differs from the folder (jf-open-pro-garbage-inspection)
  • 100Steps. 45 steps
  • 100Execution cost. Instruction body is 1642 tokens
  • 100Running it twice. No mutating operations
  • low 10 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 68: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 45 items
  • +4Has examples (10 code blocks)

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

External checks

ClawHub: suspicious
This camera-inspection skill is not clearly malicious, but it needs Review because it handles sensitive camera credentials, surveillance images, and scheduled reporting with weak scoping and secret-handling guidance.
LLM: suspicious (high) · 30 Jul 2026