travel-planner

Use for concise business travel plans that combine policy constraints, local route facts, and traveler priorities.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/agent_task_experiments/skills/travel-planner/SKILL.md

Quality

Content

72%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 exemplary in conciseness and clean organization for a simple single-purpose skill. Its weakness is actionability and workflow clarity: requirements are listed as unnumbered directives with no example output or verification step to make the process fully executable.

Suggestions

Add a short example plan or output template so Claude knows the expected format and granularity.

Number the requirements into an explicit sequence and add a final verify/review checkpoint (e.g., confirm the plan stays within policy and separates fixed vs. recommended items).

Specify how to source and cite the MCP route/city facts concretely so the 'use as evidence' step is executable.

Dimension	Reasoning	Score
Conciseness	The body is six tight bullets with no padding, no explanation of concepts Claude already knows, and every line carrying a distinct instruction, matching the lean-and-efficient anchor that assumes Claude's competence.	5 / 5
Actionability	The bullets give concrete instructional guidance ("Separate fixed commitments from recommended choices", "Include a contingency for weather, transport delay, or fatigue") but provide no example plan, output format, or specific commands, leaving the guidance incomplete per the some-concrete-but-incomplete anchor.	3 / 5
Workflow Clarity	The bullets imply a loose sequence (start from objective, gather evidence, separate, add contingency) but are presented as unnumbered requirements with no explicit checkpoints or validation step, matching the anchor for steps present but checkpoints missing/implicit.	3 / 5
Progressive Disclosure	The skill is well under 50 lines with no external references needed and is organized under a clear '# Travel Planner' / '## Requirements' structure, qualifying for the simple-skill exception that scores 5 on well-organized sections alone.	5 / 5
	Total	16 / 20 Passed

Description

62%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.

The description is concise, uses a third-person "Use for..." trigger, and clearly scopes a business-travel niche with low conflict risk. It is held back from a top score by limited trigger-term variety and abstract rather than concrete action verbs.

Suggestions

Add concrete action verbs (e.g., 'Drafts and sequences') so the 'what' reads as specific actions rather than an abstract 'combine'.

Broaden trigger terms with natural synonyms such as 'itinerary', 'trip', or 'booking' so users' varied phrasing matches.

Consider naming the output artifact more concretely (e.g., 'day-by-day itinerary') to sharpen the 'when'.

Dimension	Reasoning	Score
Specificity	The description names the domain ("business travel plans") and concrete components ("policy constraints, local route facts, traveler priorities") but uses the abstract verb "combine" rather than listing specific actions like draft, schedule, or book, matching the anchor that names the domain with minimal/generic actions.	3 / 5
Completeness	It answers both what ("concise business travel plans that combine...") and when ("Use for...") with an explicit trigger clause, but the trigger phrasing is narrower than the comprehensive multi-phrase example at score 5.	4 / 5
Trigger Term Quality	"business travel plans" is a natural phrase a user might say, but common synonyms like "itinerary", "trip", or "booking" are absent, fitting the anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The combination of policy constraints, route facts, and traveler priorities carves a fairly distinct business-travel niche with minor overlap risk against generic planning skills, just above the somewhat-specific anchor at 3.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: AgentEra/Agently
Path: examples/agent_task_experiments/skills/travel-planner/SKILL.md
Commit: 5ecfa97

Reviewed: 1 day 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.