arcgis-utility-networks
Work with ArcGIS Utility Networks for modeling and analyzing connected infrastructure including network tracing, associations visualization, and topology validation. Use for electric, gas, water, and telecom network analysis.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 identifies a specific domain (ArcGIS Utility Networks), lists concrete capabilities (tracing, visualization, validation), and provides explicit trigger guidance for when to use it (electric, gas, water, telecom analysis). The description is concise, uses third-person voice, and includes natural keywords that users in this domain would use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'network tracing', 'associations visualization', and 'topology validation', all within the clearly defined domain of ArcGIS Utility Networks for connected infrastructure modeling. | 3 / 3 |
Completeness | Clearly answers both 'what' (modeling and analyzing connected infrastructure including network tracing, associations visualization, topology validation) and 'when' ('Use for electric, gas, water, and telecom network analysis'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'ArcGIS', 'Utility Networks', 'network tracing', 'topology validation', 'electric', 'gas', 'water', 'telecom', and 'associations'. These cover the main terms a user working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche — ArcGIS Utility Networks is a very specific domain. The combination of 'ArcGIS', 'Utility Networks', and infrastructure-specific terms like 'network tracing' and 'topology validation' make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 strong actionability — concrete code examples, clear import patterns, and useful property tables. Its main weaknesses are the lack of an explicit multi-step workflow with validation checkpoints (especially important for topology validation and tracing operations) and the somewhat monolithic structure that could benefit from splitting detailed API tables into separate reference files. Some minor verbosity in explaining domain concepts Claude already knows.
Suggestions
Add an explicit numbered workflow for the common use case (e.g., 1. Configure auth → 2. Load WebMap → 3. Load UtilityNetwork → 4. Validate topology → 5. Create widgets/run trace) with validation checkpoints at each step.
Move the detailed property/method tables to a separate REFERENCE.md file and link to it, keeping only the most essential properties inline.
Remove or minimize the Key Concepts section — Claude already understands what network tracing, associations, and topology are; focus on ArcGIS-specific implementation details only.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy — the Map Components approach and Core API approach overlap, and the property/method tables could be more selective. The key concepts section explains things Claude likely already knows (e.g., what associations and subnetworks are). However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides fully executable code examples for both web components and JavaScript API approaches, with concrete import patterns, widget configuration, and a complete HTML example. Property tables and method references give specific, copy-paste ready guidance. | 3 / 3 |
Workflow Clarity | The Common Pitfalls section implicitly describes a workflow (load WebMap → load UtilityNetwork → create widgets), and load order is mentioned, but there's no explicit numbered workflow with validation checkpoints. For operations like topology validation and tracing, explicit validation/feedback loops are missing. | 2 / 3 |
Progressive Disclosure | The skill references related skills and samples at the bottom, which is good. However, the content itself is quite long (~200+ lines) with detailed property tables and multiple approaches that could be split into separate reference files. The inline API reference tables make the main skill heavier than necessary. | 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.