arcgis-cim-symbols
Create advanced cartographic symbols using CIM (Cartographic Information Model). Use for complex multi-layer symbols, animated markers, custom line patterns, and data-driven symbology.
79
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/4.34/skills/arcgis-cim-symbols/SKILL.mdQuality
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 well-structured description that clearly communicates both what the skill does and when to use it, with a distinct niche in CIM-based cartographic symbology. Its main weakness is that trigger terms could be broader to capture more natural user language variations, particularly common platform names (ArcGIS, Esri) and file extensions that users might reference.
Suggestions
Add platform-specific trigger terms users might naturally say, such as 'ArcGIS', 'Esri', 'map symbology', '.lyrx files', or 'renderer' to improve discoverability.
Consider adding common synonyms like 'map symbols', 'GIS styling', or 'symbol layers' that users unfamiliar with CIM terminology might use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'multi-layer symbols, animated markers, custom line patterns, and data-driven symbology.' These are distinct, concrete capabilities within the CIM domain. | 3 / 3 |
Completeness | Clearly answers both what ('Create advanced cartographic symbols using CIM') and when ('Use for complex multi-layer symbols, animated markers, custom line patterns, and data-driven symbology'), with explicit trigger guidance via the 'Use for...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'CIM', 'cartographic symbols', 'animated markers', 'line patterns', 'data-driven symbology', but misses common user variations like 'ArcGIS', 'map symbols', 'symbol renderer', '.lyrx', or 'Esri' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | CIM (Cartographic Information Model) is a very specific niche domain. The combination of 'cartographic', 'CIM', and the specific symbol types makes this highly 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 reference skill with excellent actionability — nearly every section provides complete, executable code examples for CIM symbol creation. The main weaknesses are its length (could benefit from splitting into overview + detailed reference files) and the lack of any workflow guidance around testing/validating symbols. The content is well-organized but could be more token-efficient by consolidating some repetitive structural patterns.
Suggestions
Split detailed examples (line symbols, polygon symbols, animations) into separate reference files and keep SKILL.md as a concise overview with one basic example and clear links to each detailed file.
Add a brief workflow section explaining how to test/validate CIM symbols (e.g., 'Apply symbol to a test graphic, verify rendering in MapView, check console for CIM parsing errors').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is largely code examples which are useful, but the initial 'CIM Symbol Basics' bullet list is somewhat redundant given the description and the examples that follow. The file is quite long (~350 lines) and some examples could be consolidated. However, it avoids explaining basic concepts Claude would know. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready JavaScript/TypeScript code for every symbol type discussed. Examples are concrete with specific property values, color arrays, and complete object structures. The numbered marker, arrow line, hatched fill, and data-driven examples are all directly usable. | 3 / 3 |
Workflow Clarity | This is primarily a reference/recipe skill rather than a multi-step workflow, so explicit sequencing is less critical. However, there's no guidance on the process of creating and validating CIM symbols (e.g., how to test them, debug rendering issues, or verify correctness). The 'Common Pitfalls' section hints at validation concerns but doesn't provide verification steps. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and progresses from basic to advanced (point → line → polygon → animation → data-driven). However, at ~350 lines this is quite long and could benefit from splitting detailed examples into separate reference files. The 'Reference Samples' section at the end provides some navigation but the main content is monolithic. | 2 / 3 |
Total | 9 / 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 (509 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.