arcgis-editing

Edit features with the Editor component/widget, configure forms, manage subtypes, handle attachments, and work with branch versioning.

Quality

60%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./contexts/5.0/skills/arcgis-editing/SKILL.md

Quality

Content

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 comprehensive, highly actionable skill with excellent executable code examples covering the full editing lifecycle from basic Editor setup through branch versioning. Its main weakness is length — at ~400+ lines with inline reference tables and numerous examples, it could benefit from splitting reference material into separate files. The workflow clarity is strong, particularly the version management workflow with proper error handling and cleanup.

Suggestions

Move the Editor component property/event/method tables to a separate reference file (e.g., EDITOR_REFERENCE.md) and link to it from the main skill to reduce token usage.

Consider splitting the complete HTML example and some of the more detailed form examples into an EXAMPLES.md file, keeping only the most essential patterns inline.

Dimension	Reasoning	Score
Conciseness	The skill is quite long with extensive property/event/method tables that could be referenced externally. Some sections like the 'Branch Versioning Overview' include explanatory text Claude doesn't need. However, most content is code-focused and avoids excessive explanation of basic concepts.	2 / 3
Actionability	The skill provides fully executable code examples throughout — from basic Editor component HTML to complete version management workflows. Code is copy-paste ready with concrete imports, API calls, and result handling. The Common Pitfalls section includes both anti-patterns and correct patterns.	3 / 3
Workflow Clarity	Multi-step workflows like version editing include clear sequencing with validation checkpoints (check for conflicts after reconcile, try/finally for cleanup). The 'Complete Version Workflow' function demonstrates proper error handling and resource cleanup. The Common Pitfalls section explicitly addresses validation gaps like checking edit capabilities and inspecting applyEdits results.	3 / 3
Progressive Disclosure	The skill has clear section headers and references related skills at the bottom, but the body is monolithic — property tables, multiple form examples, versioning workflows, and attachments are all inline. The extensive property/event/method tables for the Editor component could be split into a reference file, and the complete HTML example could be in a separate examples file.	2 / 3
	Total	10 / 12 Passed

Description

42%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description lists specific capabilities well but suffers from a complete lack of 'when to use' guidance, which is critical for skill selection. The domain context (likely ArcGIS or a specific GIS framework) is never explicitly stated, making it harder for Claude to distinguish this skill from other editing or form-related skills. Adding explicit trigger conditions and naming the technology platform would significantly improve selection accuracy.

Suggestions

Add a 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user asks about the ArcGIS Editor widget, feature editing, form configuration, or branch versioning in geodatabase workflows.'

Explicitly name the platform or framework (e.g., ArcGIS Maps SDK, ArcGIS Experience Builder) to improve distinctiveness and help Claude match the right context.

Include natural user terms and file/object types users might mention, such as 'geodatabase', 'feature layer', 'ArcGIS', or 'GIS editing'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: edit features, configure forms, manage subtypes, handle attachments, and work with branch versioning. These are distinct, actionable capabilities.	3 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores at 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'Editor component/widget', 'forms', 'subtypes', 'attachments', 'branch versioning', but these are somewhat domain-specific (likely ArcGIS/GIS) without mentioning the broader context. Missing common user phrases like 'editing geodata', 'feature editing', or the platform name.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Editor component/widget', 'subtypes', and 'branch versioning' narrows the domain somewhat (likely GIS/ArcGIS), but without naming the specific platform or technology, it could overlap with other editing or form-related skills. 'Configure forms' and 'handle attachments' are quite generic terms.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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 (747 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: SaschaBrunnerCH/arcgis-maps-sdk-js-ai-context
Commit: d84407b

Reviewed: 3 months ago

Table of Contents

Discovery Implementation Validation

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.