arcgis-visualization
Style and render geographic data with renderers, symbols, and visual variables. Use for creating thematic maps, heatmaps, class breaks, unique values, labels, and 3D visualization.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 skill description that clearly communicates both what the skill does and when to use it. It uses specific, domain-appropriate terminology that GIS users would naturally employ, and the 'Use for' clause provides explicit trigger guidance. The description is concise yet comprehensive, covering the key capabilities without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'style and render geographic data', 'renderers, symbols, visual variables', 'thematic maps, heatmaps, class breaks, unique values, labels, 3D visualization'. These are concrete, domain-specific capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Style and render geographic data with renderers, symbols, and visual variables') and when ('Use for creating thematic maps, heatmaps, class breaks, unique values, labels, and 3D visualization') with an explicit 'Use for' trigger clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'heatmaps', 'thematic maps', 'class breaks', 'unique values', 'labels', '3D visualization', 'renderers', 'symbols'. These cover a good range of terms a GIS user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in geographic data visualization and cartographic styling. Terms like 'renderers', 'class breaks', 'unique values', 'heatmaps', and '3D visualization' in a geographic context are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong reference skill with excellent actionability—every concept is backed by executable, copy-paste-ready code examples. The common pitfalls section with anti-patterns and correct patterns adds significant value. The main weakness is that the skill is quite long and monolithic; splitting detailed symbol catalogs and visual variable references into separate files would improve progressive disclosure and conciseness.
Suggestions
Extract the detailed 2D/3D symbol type catalog and visual variables sections into separate reference files (e.g., SYMBOLS.md, VISUAL-VARIABLES.md) and link to them from the main skill, keeping SKILL.md as a concise overview with the most common patterns.
Remove or condense the autocasting section—the JS example alone suffices; the TypeScript variants and the tip about when to use explicit classes add length without proportional value for most use cases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is largely efficient with code examples doing the heavy lifting, but it's quite long and could benefit from splitting detailed symbol type references and visual variable examples into separate files. Some sections like the color formats note and autocasting explanation add minor verbosity. | 2 / 3 |
Actionability | Every renderer type, symbol type, and visual variable includes fully executable JavaScript/TypeScript code examples with concrete property values. The common pitfalls section provides both anti-patterns and correct patterns with clear explanations of impact. | 3 / 3 |
Workflow Clarity | This is primarily a reference/configuration skill rather than a multi-step workflow, so the single action of assigning renderers to layers is unambiguous. The content is well-sequenced from simple to complex renderers, and the common pitfalls section serves as validation guidance for the most frequent errors. | 3 / 3 |
Progressive Disclosure | The skill does reference related skills (arcgis-feature-effects, arcgis-smart-mapping, arcgis-core-maps) with clear one-level-deep links, and lists reference samples. However, the body itself is very long (~400+ lines) with detailed symbol type catalogs and visual variable examples that could be split into separate reference files, keeping SKILL.md as a leaner overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (584 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.