SKILLEMALL.ai
GitHub ↗ RU Sign in

BF background-download

Asynchronous background download with retry, status tracking via Ontology, notifications to original channel. Supports resume on broken connections.

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

As a process F 45/100 · Will not run — References files that are not bundled: references/schema.json

ReferenceInfrastructuretype 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%
99
Quality 40%
64
Run on models
none yet
Process rating
F
45/100
Will not run
References files that are not bundled: references/schema.json
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-background-process scripts/download.py:216
    Starts a background / autostarted process
    os.setsid()

Files scanned: 4. 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: references/schema.json
  • note frontmatter-key unknown frontmatter key "author_email"
  • note frontmatter-key unknown frontmatter key "ontology"

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: references/schema.json
  • 0Tools and files. 1 referenced file(s) missing: references/schema.json
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 744 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

  • +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
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +2Single-language instructions
  • +3Description length 148: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (7 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

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

External checks

ClawHub: suspicious
The skill does what it claims, but it gives caller-controlled downloads too much local execution and file-writing power without enough safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026