meta-travel-planner

Use this meta-skill instead of answering directly when the user needs a trip plan, travel itinerary, business-trip schedule, or day-by-day travel brief that benefits from multi-skill orchestration across preference inference, weather, place search, constraint extraction, itinerary drafting, variants, and optional artifact guidance.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/opensquilla/skills/exp/meta-travel-planner/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is exceptionally concise and adequately organized, but it delegates the actual orchestration workflow to the frontmatter composition, leaving the markdown body itself with only a high-level fallback. Actionability and workflow clarity are therefore moderate rather than strong when judged on the body alone.

Suggestions

Add a brief 'How it works' line in the body pointing to the composition steps so readers understand where the primary workflow lives.

Expand the fallback with a concrete validation checkpoint (e.g. verify weather/POI evidence before drafting the itinerary) to raise workflow clarity.

Optionally inline a one-line example of the expected final output structure so the body is actionable without the composition.

Dimension	Reasoning	Score
Conciseness	The body is lean (roughly a dozen lines): one orienting summary line plus a compact fallback, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	The fallback names concrete skills to call ('weather, multi-search-engine, summarize') and a specific file/action ('write a styled travel-itinerary.html and publish_artifact it'), but offers no executable commands and leaves the main orchestration path unstated in the body, so it is only partially concrete.	3 / 5
Workflow Clarity	A rough fallback sequence is present (call three skills, then optionally export HTML), but there are no validation checkpoints or error-recovery steps; the primary multi-step workflow lives in the frontmatter composition rather than the body.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the short body is well-organized into an overview and a Fallback section; not a 5 because the body does not explicitly orient the reader to the composition block that holds the real workflow.	4 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both the skill's purpose and its trigger conditions with concrete, natural language. Minor gaps in synonym coverage keep trigger term quality and specificity just below the top anchor.

Suggestions

Add common synonyms such as 'vacation', 'holiday itinerary', or 'tourist plan' to broaden natural trigger coverage.

Consider naming the concrete output artifact (e.g. 'day-by-day itinerary brief') earlier to sharpen the 'what' beyond process-stage labels.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete orchestration actions ('preference inference, weather, place search, constraint extraction, itinerary drafting, variants, and optional artifact guidance'); not a 5 because the actions are process-stage labels rather than fully enumerated concrete capabilities.	4 / 5
Completeness	Explicitly answers both what ('multi-skill orchestration across...') and when ('Use this meta-skill instead of answering directly when the user needs a trip plan, travel itinerary...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural trigger coverage ('trip plan, travel itinerary, business-trip schedule, day-by-day travel brief'); a few common synonyms like 'vacation', 'holiday', or 'tourist itinerary' are missing, so not a 5.	4 / 5
Distinctiveness Conflict Risk	Clear travel-planning orchestration niche with distinct, specific triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/exp/meta-travel-planner/SKILL.md
Commit: 94ac35e

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.