AC world-clock
Answers time and timezone questions with live data from the worldclock.pro MCP server. Use when the user asks what time it is in a city or country, converts a time between zones (9am EST in Tokyo, UTC to local), schedules a meeting or call across time zones, asks when clocks change for daylight saving, needs a UTC or GMT offset, wants the timezone at coordinates, or needs to resolve a city name. Covers DST rules, half hour offsets, and 224,000+ cities.
Answers time and timezone questions with live data from the worldclock.pro MCP server. Use when the user asks what time it is in a city or country, converts a…
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, consistency, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (world-clock) differs from the folder (world-clock-pro)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 13 steps
- 100Execution cost. Instruction body is 856 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +3Description length 456: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 13 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.