arcgis-knowledge-graphs
Work with ArcGIS Knowledge graphs for storing, querying, and visualizing connected data using KnowledgeGraphLayer, LinkChartView, and openCypher queries. Use for graph databases, relationship visualization, and entity exploration.
86
82%
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 concisely covers specific capabilities, relevant technologies, and clear trigger conditions. It uses third person voice appropriately and provides enough domain-specific terminology (ArcGIS, KnowledgeGraphLayer, LinkChartView, openCypher) to be highly distinguishable. The 'Use for...' clause effectively communicates when this skill should be selected.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions (storing, querying, visualizing connected data) and names specific technologies (KnowledgeGraphLayer, LinkChartView, openCypher queries). | 3 / 3 |
Completeness | Clearly answers 'what' (work with ArcGIS Knowledge graphs for storing, querying, and visualizing connected data using specific tools) and 'when' ('Use for graph databases, relationship visualization, and entity exploration'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Knowledge graphs', 'graph databases', 'relationship visualization', 'entity exploration', 'openCypher queries', and 'ArcGIS'. These cover both domain-specific and general terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with ArcGIS-specific terminology (KnowledgeGraphLayer, LinkChartView, openCypher) that clearly carves out a niche 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, highly actionable reference skill with excellent executable code examples covering the full ArcGIS Knowledge Graph API surface. Its main weaknesses are the lack of validation/error-handling workflows for destructive operations (apply edits) and the monolithic structure that could benefit from splitting detailed sections into separate files. The content is mostly concise but has minor verbosity in explanatory notes.
Suggestions
Add validation/error-handling steps around executeApplyEdits calls (e.g., try/catch with error inspection, verify edits with a follow-up query) to create proper feedback loops for destructive operations.
Split detailed sections like Link Chart Visualization and openCypher patterns into separate referenced files to improve progressive disclosure and reduce the main file length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with code-forward examples, but includes some unnecessary commentary (e.g., 'Knowledge graph services typically require authentication — configure credentials or OAuth' is vague filler). The import patterns section listing both ESM and CDN is useful but adds bulk. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for every major operation: fetching graphs, querying with openCypher, streaming results, spatial queries, apply edits, link chart creation, layout configuration. Code is concrete with specific API calls and realistic parameters. | 3 / 3 |
Workflow Clarity | The Apply Edits section performs destructive operations (add, update, delete entities) without any validation or error handling steps. There are no feedback loops for verifying edits succeeded. The Common Pitfalls section mentions 'load before querying' but doesn't integrate this into a clear workflow sequence. Per rubric, missing feedback loops for destructive changes caps this at 2. | 2 / 3 |
Progressive Disclosure | The file is quite long (~300 lines) with all content inline. The Reference Samples and Related Skills sections at the end provide good navigation, but the main body could benefit from splitting detailed sections (e.g., Link Chart Visualization, openCypher patterns) into separate files with clear pointers. Currently it's a semi-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.