SKILLEMALL.ai

BB local-image-gen-aipc

>

ClawHub Agent Skills author: juan-OY v1.0.3 MIT-0 5 files body ≈ 4 384 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process B 75/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
51
Run on models
none yet
Process rating
B
75/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
30
Inputs and preconditions w 11
30
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: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit keys need to be on a single line at line 6, column 1: description: > generate an image, create a picture, draw something, make an image of, text to … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "os"
  • note frontmatter-key unknown frontmatter key "setup"
  • note frontmatter-key unknown frontmatter key "inference"

Process rating: all ten parameters 75/100

  • 0Progress reporting. Says nothing while it works
  • 30When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 4384 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 19 steps
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (11 tags): a typed call is more reliable

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 1: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 19 items
  • +3Output format is stated explicitly
  • +4Has examples (23 code blocks)

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

External checks

ClawHub: suspicious
The skill’s image-generation purpose is coherent, but it tells the agent to automatically install software, packages, and a large model without clear user confirmation.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026