SKILLEMALL.ai

BF agent-caller

Call 179 professional agents on-demand from database

ClawHub Agent Skills author: 杨兴隆 v1.0.3 MIT-0 16 files body ≈ 1 977 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 40/100 · Will not run — References files that are not bundled: scripts/agent_usage_demo.py

ReferenceAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
F
40/100
Will not run
References files that are not bundled: scripts/agent_usage_demo.py
Tools and files w 18
0
Result and completion w 14
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.
  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: 16. 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/agent_usage_demo.py
  • note frontmatter-key unknown frontmatter key "keywords"
  • note frontmatter-key unknown frontmatter key "requires"
  • note frontmatter-key unknown frontmatter key "install"

Process rating: all ten parameters 40/100

Will not run. References files that are not bundled: scripts/agent_usage_demo.py
  • 0Tools and files. 1 referenced file(s) missing: scripts/agent_usage_demo.py
  • 0Result and completion. Does not say what the result is
  • 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
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 71 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1977 tokens
  • low 19 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 52: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -228 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +4Structure: 42 headings
  • +3Step-by-step instructions: 71 items
  • +4Has examples (12 code blocks)
  • +3All 4 scripts are documented
  • +1License stated

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

External checks

ClawHub: suspicious
The core code is a local agent-prompt catalog, but the package includes unsafe credential-sharing guidance and high-impact agent prompts without enough user control warnings.
LLM: suspicious (high) · VirusTotal: · 29 May 2026