SKILLEMALL.ai

BD travel-itinerary-planner

智能旅行行程规划系统 - 一键生成完整旅行计划。 收集旅行信息,创建详细行程,提供预算估算、餐厅推荐、交通建议、实用贴士。 支持家庭旅行、情侣旅行、单人旅行等多种场景。 预算控制精准,误差控制在20%以内。 包含实时天气、预订链接、儿童友好活动、紧急联系等扩展功能。

ClawHub Hermes author: Chace v1.0.0 MIT-0 10 files body ≈ 1 572 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
D
49/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.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 10. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 134 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "framework"

Process rating: all ten parameters 49/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
  • 40Consistency. Frontmatter name (travel-itinerary-planner) differs from the folder (chaceclaw-travel-itinerary)
  • 100Tools and files. No external tools needed
  • 100Steps. 116 steps
  • 100Execution cost. Instruction body is 1572 tokens
  • 100Running it twice. No mutating operations
  • low 14 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
  • -266 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 133: enough signal without eating the budget
  • +4Structure: 41 headings
  • +3Step-by-step instructions: 116 items
  • +4Has examples (19 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This looks like a real travel-planning skill, but it overstates live/safety features and saves sensitive trip and expense details locally without clear privacy controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026