BF kontour-travel-planner
Transform any AI agent into a world-class travel planner using Kontour AI's 9-dimension progressive planning model with structured conversation flow.
As a process F 52/100 · Will not run — References files that are not bundled: {APPROVED_PUBLIC_URL}
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
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: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6308 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: {APPROVED_PUBLIC_URL}
Process rating: all ten parameters 52/100
Will not run. References files that are not bundled: {APPROVED_PUBLIC_URL}
- 0Tools and files. 1 referenced file(s) missing: {APPROVED_PUBLIC_URL}
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 26 mutating operations with no state check
- 40Consistency. Frontmatter name (kontour-travel-planner) differs from the folder (travel-planner-notion-ai-obsidian-kontour-integration)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6308 tokens
- 100Steps. 74 steps
- 100Failures and branches. 2 branches, has a failure section
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- -32 of 5 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 149: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 74 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: suspicious
The skill is mostly an offline travel planner, but it needs review because it hardcodes an unapproved third-party Kontour link into generated output and has secondary installation and audit-script hygiene risks.
LLM: suspicious (medium) · 10 Sept 2026