arcgis-charts
Render interactive charts from ArcGIS layer data using the Charts Components package. Use for bar, line, pie, histogram, scatter, box plot, gauge, radar, and heat charts.
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-charts/SKILL.mdQuality
Discovery
82%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 strong description that clearly identifies the specific technology (ArcGIS Charts Components), the core action (rendering interactive charts), and enumerates the supported chart types. Its main weakness is the lack of an explicit 'Use when...' clause that describes triggering scenarios from the user's perspective, which slightly limits completeness.
Suggestions
Add an explicit 'Use when...' clause describing trigger scenarios, e.g., 'Use when the user wants to visualize ArcGIS layer data, create charts from map service layers, or asks about the ArcGIS Charts Components package.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and chart types: 'Render interactive charts from ArcGIS layer data using the Charts Components package' followed by an enumeration of nine specific chart types (bar, line, pie, histogram, scatter, box plot, gauge, radar, heat). | 3 / 3 |
Completeness | Clearly answers 'what' (render interactive charts from ArcGIS layer data) and partially addresses 'when' with 'Use for bar, line, pie...' but lacks an explicit 'Use when...' clause describing the triggering context (e.g., 'Use when the user asks to visualize ArcGIS data or create charts from map layers'). The 'Use for' lists chart types rather than trigger scenarios. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'charts', 'ArcGIS', 'bar', 'line', 'pie', 'histogram', 'scatter', 'box plot', 'gauge', 'radar', 'heat charts', and 'Charts Components package'. These cover the natural terms a user working with ArcGIS charting would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'ArcGIS layer data' and 'Charts Components package', which clearly carves out a niche that is unlikely to conflict with generic charting or data visualization 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 comprehensive and highly actionable skill with excellent executable examples, a useful pitfalls section, and good cross-references to related skills. Its main weakness is that it's overly long due to inline API reference tables that would be better placed in a separate file, and it lacks explicit validation/verification steps in its workflows. The content would benefit from splitting the reference material out and keeping the SKILL.md focused on quick-start patterns and common use cases.
Suggestions
Move the detailed property/method/event tables to a separate REFERENCE.md file and link to it from the SKILL.md, keeping only the most essential properties inline.
Add a brief validation step after chart setup (e.g., listening for `arcgisUpdateComplete` or `arcgisDataFetchComplete` to confirm the chart rendered with data) to improve workflow clarity.
Remove self-evident table descriptions like 'Hide loading animation' for `hideLoaderAnimation` to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long with extensive API reference tables (properties, methods, events) that could be split into a separate reference file. The description column in many table rows is self-evident (e.g., 'Hide loading animation' for `hideLoaderAnimation`). However, the code examples and pitfalls sections are well-targeted and not padded with unnecessary explanation. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples including a complete CDN HTML page, multiple chart type instantiations, selection/filtering setup, custom formatters, and export calls. The common pitfalls section includes concrete anti-patterns with correct alternatives. | 3 / 3 |
Workflow Clarity | The basic usage example shows a clear sequence (load map → get layer → create model → assign to chart), but there are no explicit validation checkpoints or error handling steps. For a component setup workflow, there's no guidance on verifying the chart rendered correctly or handling common async timing issues beyond the pitfalls section. | 2 / 3 |
Progressive Disclosure | The skill has good cross-references to related skills at the bottom and references sample names, but the massive inline API reference tables (properties, methods, events, formatter callbacks) should be in a separate reference file. The SKILL.md tries to be both a quick-start guide and a complete API reference, making it a near-monolithic document. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
d84407b
- 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.