SKILLEMALL.ai

BF claude-handoff

Writes a structured handoff package when local agent determines cloud Claude Code is needed. This is the ONLY path from local pipeline to cloud — the agent never auto-invokes Claude. The user reviews the handoff, decides whether to run Claude Code, and retains full control over Max quota spend.

ClawHub Agent Skills author: Stephen Thorn v1.0.0 MIT-0 3 files body ≈ 3 658 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 45/100 · Will not run — References files that are not bundled: ref-link

GeneratorAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
F
45/100
Will not run
References files that are not bundled: ref-link
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. 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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ref-link
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "inputs"
  • note frontmatter-key unknown frontmatter key "outputs"

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: ref-link
  • 0Tools and files. 1 referenced file(s) missing: ref-link
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 100Steps. 11 steps
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3658 tokens
  • 100Progress reporting. Reports progress

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 295: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (7 code blocks)

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

External checks

ClawHub: suspicious
The skill performs its handoff purpose, but it can send task and project details to an environment-selected notification endpoint and keeps persistent local metadata logs.
LLM: suspicious (high) · VirusTotal: · 29 May 2026