Content
64%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, actionable reference for ArcGIS Knowledge Graphs with strong executable code examples covering querying, visualization, editing, and search. Its main weaknesses are its length (could benefit from progressive disclosure into sub-files) and the lack of validation/error-handling workflows for destructive operations like entity edits and deletes. Some sections like layout settings add minimal value by deferring to API docs rather than providing concrete guidance.
Suggestions
Add validation/error-handling steps for applyEdits operations (check results for errors, handle failures) to improve workflow safety for destructive operations.
Split the document into a concise overview SKILL.md with links to separate files for detailed topics like LINK_CHARTS.md, CYPHER_PATTERNS.md, and APPLY_EDITS.md.
Remove or consolidate the OrganicLayoutSettings and ChronologicalLayoutSettings sections that mostly just say 'refer to API documentation' — either provide concrete property examples or omit them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with code-forward examples and minimal prose, but it's quite long with some sections that could be consolidated (e.g., multiple layout settings sections that add little value, and the OrganicLayoutSettings/ChronologicalLayoutSettings sections that just say 'refer to API documentation'). | 2 / 3 |
Actionability | Nearly all guidance is provided as executable JavaScript code with proper imports, concrete API calls, and realistic examples. The openCypher patterns, apply edits, search, and query examples are all copy-paste ready with clear context. | 3 / 3 |
Workflow Clarity | The skill presents individual operations clearly but lacks explicit multi-step workflows with validation checkpoints. For destructive operations like applyEdits (entity deletes), there are no validation or error-handling steps. The 'updateLinkChart from query results' function shows a workflow but without error handling or validation. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a reference samples section at the end, but it's a monolithic document (~300 lines) that could benefit from splitting detailed sections (link chart visualization, openCypher patterns, apply edits) into separate reference files with brief summaries in the main skill. | 2 / 3 |
Total | 9 / 12 Passed |