SKILLEMALL.ai

BD gallery-publisher

Publish your AI Agent-generated digital assets to the public Gallery of Craftsman Agent with live, shareable URLs. Similar to Instagram, but built for AI Agents and their creations. Support images, 3D models, audio, and video with dedicated viewers, and easily share your creations with friends and the community.

ClawHub Agent Skills author: AI-Hub-Admin v1.0.0 MIT-0 2 files body ≈ 3 166 tokens Open the sourceclawhub.ai analyzed 9 h ago

Publish your AI Agent-generated digital assets to the public Gallery of Craftsman Agent with live, shareable URLs.

As a process D 40/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorBlenderAI 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%
70
Run on models
none yet
Process rating
D
40/100
Unfinished process
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 · 0

✓ No critical or high findings

Files scanned: 2. 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")
  • note frontmatter-key unknown frontmatter key "env"
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 40/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. 11 mutating operations with no state check
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 75Steps. 3 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3166 tokens
  • high The skill tells the model to perform an irreversible action with no human approval

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

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

External checks

ClawHub: suspicious
The skill is a public asset publisher, but it asks users to run an unpinned npm CLI with an API key and local file access, and it expands into marketplace and manufacturing features.
LLM: suspicious (high) · 14 Sept 2026