CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

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-organized, actionable, and workflow-oriented with concrete commands and a runnable script, but it carries moderate redundancy across scope/validation sections and ships a stub script plus a thin reference file. Navigation and sequencing are solid with only minor validation-loop gaps.

Suggestions

Consolidate When to Use, Scope Boundaries, and Input Validation into a single scope section to remove the redundant restatement of the same boundaries.

Replace or expand the stub scripts/main.py so it performs genuine multi-region local-time computation (including IANA timezone handling) rather than returning hardcoded '09:00' values.

Either flesh out references/guidelines.md with substantive planning notes or drop it, since its current two-bullet form adds little over the main body.

DimensionReasoningScore

Conciseness

Mostly efficient and well-sectioned, but the Input Validation section restates When to Use and Scope Boundaries, and Stress-Case Rules overlaps the Response Template — clear tightening opportunities without losing information.

3 / 5

Actionability

Provides executable Quick Check and Usage commands plus a runnable script and a concrete Parameters table; the main gap is that scripts/main.py is a stub with hardcoded times rather than copy-paste-ready for real multi-region computation.

4 / 5

Workflow Clarity

A clear 5-step sequence with a stop-and-request-missing-fields checkpoint and an Error Handling block with manual fallback; the only gap is the absence of an explicit validate-fix-retry loop on script output.

4 / 5

Progressive Disclosure

Good structure with a clearly signaled, one-level-deep References section linking guidelines.md and audit-reference.md; minor gaps are the near-empty guidelines.md and some inline redundancy across scope sections.

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 concrete, domain-specific actions, but omits any explicit 'Use when...' trigger guidance, which caps completeness and leaves distinctiveness slightly short of ideal. Trigger term coverage is good though not comprehensive.

Suggestions

Add an explicit trigger clause, e.g. 'Use when planning meetings across time zones for distributed teams, or when the user mentions time zone overlap, global scheduling, or region-by-region local times.'

Include natural synonyms users might say (e.g., 'timezones', 'global team meeting', 'meeting scheduler') to broaden trigger coverage.

Name a distinguishing capability (e.g., DST-aware local-time mapping) to sharpen distinctiveness against generic calendar tools.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Plan cross-time-zone meeting windows', 'region-by-region local time mappings', and 'tradeoff analysis' — with only minor coverage gaps (e.g., DST handling, alias resolution not named).

4 / 5

Completeness

The 'what' is clear, 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

Includes natural phrases users would say ('meeting windows', 'distributed teams', 'scheduling decisions') but misses common synonyms like 'timezones', 'global team', or 'meeting scheduler'.

4 / 5

Distinctiveness Conflict Risk

The cross-time-zone / distributed-team niche is mostly distinct with minor overlap risk against generic calendar or scheduling skills; not a fully isolated trigger set.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
aipoch/medical-research-skills
Reviewed

Table of Contents

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.