SKILLEMALL.ai
GitHub ↗ RU Sign in

AC exhibitor-checklist-generator

Generate a phased exhibitor prep checklist with task owners and deadlines from your show details. "Create our trade show prep checklist" / "生成展会准备清单" / "Messe-Checkliste erstellen" / "出展チェックリストを作成" / "lista de preparación para feria". 展会清单/参展准备/任务分配 Messe-Checkliste Messeplanung 出展準備リスト lista de control ferial

ClawHub Agent Skills author: Ivan Xu v1.2.0 MIT-0 4 files body ≈ 1 600 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process C 62/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting

GeneratorInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
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: 4. 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 "homepage"

Process rating: all ten parameters 62/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Failures and branches. 4 branches
  • 100Steps. 53 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1600 tokens

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +3Description length 311: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 53 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: clean
This is a markdown-only trade show checklist skill; its lead-capture example touches personal data, but the behavior is disclosed, purpose-aligned, and not backed by code or hidden execution.
LLM: benign (high) · VirusTotal: · 29 May 2026