date-formatter

Converts dates between formats and handles timezone differences

Quality

66%

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 ./samples/agentserver/travel-agent-optimization-di/.agent_configs/baseline/skills/date-formatter/SKILL.md

Quality

Content

78%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 lean and well-targeted, avoiding any over-explanation while giving concrete expected outputs for both tasks. Its main weakness is actionability: it tells Claude what to produce but not how to parse natural-language dates, leaving the implementation method unspecified.

Suggestions

Add a brief concrete method or library for parsing natural-language dates (e.g. a one-line Python example using dateutil.parser) to move actionability from guidance to executable.

For the timezone case, include a short example of obtaining city local times (e.g. via zoneinfo) so the side-by-side output is reproducible rather than implied.

Optionally split the two capabilities under short headers ('## Parse natural-language dates' and '## Compare times across cities') to make the two tasks scannable.

Dimension	Reasoning	Score
Conciseness	The body is two lean sentences with no padding and no over-explanation of concepts Claude already knows; every token earns its place. This matches the 'lean and efficient; assumes Claude's competence' anchor exactly.	5 / 5
Actionability	The guidance is concrete and specific (target output 'YYYY-MM-DD', side-by-side local-time display, real example phrases) but provides no implementation method, library, or command for parsing natural-language dates. This fits the 'some concrete guidance but incomplete; missing key details' anchor rather than the 'mostly executable with code' level above.	3 / 5
Workflow Clarity	Each of the two single actions is stated unambiguously with a clear expected output, and neither involves destructive or batch operations so no validation cap applies. It falls just below 5 because the timezone scenario states the display format but gives no sequenced steps for obtaining/comparing the city times.	4 / 5
Progressive Disclosure	This is a sub-50-line simple skill with no need for external references, and the content is appropriately minimal and self-contained with nothing that should be split out. Per the rubric's simple-skill exception, well-organized minimal content scores 5 here.	5 / 5
	Total	17 / 20 Passed

Description

53%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 and uses correct third-person voice to state two concrete capabilities, but it entirely lacks a 'Use when...' trigger clause and offers only generic keyword coverage. This makes it a moderately strong but incomplete description capped at the midpoint on completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to format dates, parse natural-language dates, or compare times across time zones.'

Replace generic phrasing with concrete output formats and synonyms to boost specificity and trigger coverage, e.g. 'Converts dates between formats (YYYY-MM-DD, ISO, natural language) and resolves timezone differences across cities.'

Include common user phrasings like 'date conversion', 'time zones', and 'parse dates' to improve natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (dates, timezones) and two concrete actions ('Converts dates between formats', 'handles timezone differences'), but does not enumerate a comprehensive set of specific actions. It sits at the 'names domain and 1-2 concrete actions' anchor rather than the 'several specific actions' level above, since 'between formats' is generic and no output formats are named.	3 / 5
Completeness	It gives a clear 'what' (convert date formats, handle timezones) but includes no 'Use when...' clause or equivalent trigger guidance for 'when'. Per the rubric, a missing explicit trigger clause caps completeness at 3, which is the best fit.	3 / 5
Trigger Term Quality	It surfaces relevant keywords ('dates', 'timezone differences') but omits common natural variations users would say ('format dates', 'date conversion', 'time zones'). This matches the 'some relevant keywords but missing common variations or synonyms' anchor, below the 'good keyword coverage' level.	3 / 5
Distinctiveness Conflict Risk	Date formatting and timezone handling is a clear, fairly distinct niche with minimal overlap risk against other skills. It is not generic enough to sit at the 'somewhat specific but could still overlap' level below, though it lacks the explicit trigger phrases that would warrant a 5.	4 / 5
	Total	13 / 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: Azure/azure-sdk-for-net
Path: samples/agentserver/travel-agent-optimization-di/.agent_configs/baseline/skills/date-formatter/SKILL.md
Commit: bc946a1

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.