CtrlK
BlogDocsLog inGet started
Tessl Logo

arcgis-time-animation

Work with temporal data using TimeSlider, TimeExtent, TimeInterval, and time-aware layers. Use for animating data over time, filtering by date ranges, and visualizing temporal patterns.

80

Quality

75%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-time-animation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies both what the skill does and when to use it, with specific API component names (TimeSlider, TimeExtent, TimeInterval) that create strong distinctiveness. The main weakness is that trigger terms could be broader to capture more natural user language variations like 'timeline', 'time series', or 'date animation'.

Suggestions

Add more natural user-facing trigger terms such as 'timeline', 'time series', 'date animation', 'playback', or 'chronological' to improve discoverability.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'animating data over time', 'filtering by date ranges', 'visualizing temporal patterns', and names specific components (TimeSlider, TimeExtent, TimeInterval, time-aware layers).

3 / 3

Completeness

Clearly answers both what ('Work with temporal data using TimeSlider, TimeExtent, TimeInterval, and time-aware layers') and when ('Use for animating data over time, filtering by date ranges, and visualizing temporal patterns') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes some relevant keywords like 'temporal data', 'date ranges', 'animating data over time', and specific API names (TimeSlider, TimeExtent), but misses common user terms like 'timeline', 'time series', 'date filter', 'playback', or 'time animation'.

2 / 3

Distinctiveness Conflict Risk

The specific mention of TimeSlider, TimeExtent, TimeInterval, and time-aware layers creates a clear niche around temporal/time-based GIS functionality that is unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid API reference skill with excellent actionability — nearly every concept is backed by executable code examples covering multiple usage patterns. The main weaknesses are its length (could benefit from splitting detailed reference content into separate files) and the lack of integrated validation steps in multi-step workflows. The common pitfalls section is valuable but would be more effective if woven into the relevant workflow sections.

Suggestions

Move detailed property tables, custom labels, and advanced animation patterns into a separate reference file (e.g., TIME_REFERENCE.md) to reduce the main skill's token footprint.

Integrate validation checkpoints directly into multi-step workflows (e.g., after layer.load(), explicitly check timeInfo before proceeding, with error handling guidance inline rather than only in pitfalls).

Remove one-line descriptions that state the obvious (e.g., 'Represents a time range with start and end dates', 'Represents a duration of time') to improve conciseness.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good code examples, but includes some unnecessary explanations (e.g., 'Represents a time range with start and end dates' for TimeExtent, 'Represents a duration of time' for TimeInterval) that Claude already knows. The content is quite long and could be tightened in places, though most of the length comes from genuinely useful code examples.

2 / 3

Actionability

Excellent actionability throughout — every section provides fully executable, copy-paste ready code examples covering both ESM and CDN imports, widget configuration, querying, filtering, animation patterns, and event handling. The code is concrete and complete with real property values and realistic patterns.

3 / 3

Workflow Clarity

The 'Initializing TimeSlider from Layer' section shows a reasonable workflow with layer loading and timeInfo checking, and the 'Common Pitfalls' section provides useful validation guidance. However, multi-step processes like setting up time animation lack explicit validation checkpoints or error recovery steps — the pitfalls are listed separately rather than integrated into workflows.

2 / 3

Progressive Disclosure

The content is well-organized with clear section headers and a logical progression from basics to advanced patterns. However, at ~300 lines, much of the reference material (property tables, all animation patterns, custom labels) could be split into separate files. The 'Related Skills' and 'Reference Samples' sections provide good navigation, but the main file is monolithic.

2 / 3

Total

9

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
SaschaBrunnerCH/arcgis-maps-sdk-js-ai-context
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.