SKILLEMALL.ai

DC openclaw-orchestration

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: frank-bot07 v1.0.0 18 files · 2 scripts body ≈ 206 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
57/100
safety, quality, tests
Safety 60%
95
Quality 40%
0
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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 · 5

✓ No critical or high findings

Medium and low: 5
  • low Secrets in code secret-high-entropy-token package-lock.json:65
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…FSj+bWLt…2sH/Kn8E…h6w==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:178
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…wHD+vkj3…wBQ/hCAQ…tUp/3Qh6…OOw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:184
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…CpK+FtMRQVdIMN6/Df5j…tIC+7KYK…qaA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:237
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…RFW+TK4J…oUr/txX3…6Ns/A==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:261
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…JgI+2Q5U…e1E+Nyvgdz/aIyN…n58/GELp3+w==",
    detector

Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 56/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. No external tools needed
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 206 tokens
  • 100Running it twice. No mutating operations

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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 3 headings
  • +3Step-by-step instructions: 5 items
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: clean
This appears to be a legitimate local task-queue skill, with ordinary shared-state and logging cautions but no evidence of hidden malicious behavior.
LLM: benign (high) · VirusTotal: suspicious · 28 May 2026