time-zone-planner

Plan cross-time-zone meeting windows for distributed teams, providing region-by-region local time mappings and tradeoff analysis for scheduling decisions.

Quality

72%

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 ./scientific-skills/Other/time-zone-planner/SKILL.md

Quality

Content

67%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 well structured and actionable, with a clear workflow, concrete commands, parameter tables, and real one-level-deep references. Its main weaknesses are redundancy (the scope/refusal guidance is stated three times and two sections prescribe overlapping output structures) and a usage example that does not match the packaged script's actual behavior.

Suggestions

Consolidate the triplicated scope guidance: merge "Scope Boundaries" into "When to Use" and keep only the refusal script from "Input Validation".

Merge "Stress-Case Rules" and "Response Template" into one output-structure section, since both prescribe overlapping block lists (Assumptions, Tradeoffs, Risks appear in both).

Make the documented usage match the script: either update scripts/main.py to accept the JSON input shown (regions, duration, preferred_hours) or correct the Usage section to reflect that it runs with hardcoded defaults.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows and keeps sections short, but the same scope statement is repeated three times across "When to Use", "Scope Boundaries", and "Input Validation", and "Stress-Case Rules" duplicates the "Response Template" structure. Mostly efficient but could be tightened by merging these.	3 / 5
Actionability	Concrete elements throughout: runnable Quick Check commands, an exact usage example with input JSON, a parameters table, an alias mapping table, and a verbatim refusal response. Minor gap: the documented "Input: {...}" usage does not match scripts/main.py, which accepts no input and hardcodes its example regions.	4 / 5
Workflow Clarity	The 5-step workflow is clearly sequenced and includes an explicit checkpoint ("If timezone details or availability constraints are missing, stop and request the minimum missing fields") plus a Quick Check verification and script-failure fallback in Error Handling. It stops short of anchor 5's explicit validate-fix-retry feedback loops.	4 / 5
Progressive Disclosure	Sections are well organized and both references (guidelines.md, audit-reference.md) are real files, clearly signaled with one-line descriptions at one level of depth. Minor gaps: detail like the alias mapping table and response template lives inline in the overview rather than being split out.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly states what the skill does with several concrete actions and mostly natural trigger terms, but it entirely lacks a "when to use" clause, which caps completeness and weakens its trigger function. Adding an explicit use-when clause and a few more natural trigger phrases would raise it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when scheduling meetings or calls across time zones, comparing meeting times for distributed teams, or finding overlap windows for US/EU/Asia regions."

Add natural synonyms users would actually say ("find a time that works for everyone", "schedule a call across regions", "timezone overlap") to improve trigger term coverage.

Clarify the niche boundary in the description (recommendation only, not calendar booking) to reduce overlap risk with generic calendar/scheduling skills.

Dimension	Reasoning	Score
Specificity	"Plan cross-time-zone meeting windows", "region-by-region local time mappings", and "tradeoff analysis" name several concrete actions in a clearly stated domain, but coverage has minor gaps (no mention of DST handling or candidate-window comparison). This is above anchor 3 (only 1-2 actions) but short of anchor 5's comprehensiveness.	4 / 5
Completeness	The "what" is explicit (plan cross-time-zone meeting windows with local time mappings and tradeoff analysis), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural phrases like "time-zone", "meeting windows", and "scheduling decisions" are terms users would say, giving good keyword coverage. A few natural synonyms are missing (e.g. "find a time that works for everyone", "call scheduling"), so it falls short of anchor 5's comprehensive synonym coverage but is clearly above anchor 3.	4 / 5
Distinctiveness Conflict Risk	"cross-time-zone meeting windows for distributed teams" carves out a clear niche, but the description does not distinguish itself from generic calendar/scheduling skills, leaving minor overlap risk with closely related skills rather than the minimal risk of anchor 5.	4 / 5
	Total	15 / 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: aipoch/medical-research-skills
Path: scientific-skills/Other/time-zone-planner/SKILL.md
Commit: 686e09d

Reviewed: 13 hours 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.