SKILLEMALL.ai

BD summon_translator

Translate safety procedures, supplier documents, and Articulate Rise 360 eLearning content into 137+ languages using AI. Built for supply chain teams, HSE professionals, and L&D teams who can't afford mistranslated compliance content.

ClawHub Agent Skills author: nikirun2017-phache v1.0.0 MIT-0 2 files body ≈ 1 995 tokens Open the sourceclawhub.ai analyzed 5 d ago

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches

ProcedureWriting and documentsInfrastructureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
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 name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "pricing"
  • note frontmatter-key unknown frontmatter key "auth"

Process rating: all ten parameters 46/100

  • 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. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (summon_translator) differs from the folder (summon-translator-skill)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 24 steps
  • 100Execution cost. Instruction body is 1995 tokens
  • low 13 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 234: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 24 items
  • +4Has examples (8 code blocks)

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

External checks

ClawHub: clean
This is a straightforward translation skill that uploads user-selected files to a paid translation API, with no hidden code or automatic behavior found.
LLM: benign (high) · VirusTotal: · 29 May 2026