arcgis-coding-components
Embed an Arcade expression editor in applications using the Coding Components package. Use for building Arcade authoring, testing, and debugging interfaces.
76
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-coding-components/SKILL.mdQuality
Discovery
75%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 is reasonably well-structured with a clear 'what' and 'when' clause, and occupies a distinct niche that minimizes conflict risk. However, it could benefit from more specific concrete actions and broader trigger term coverage to help users who may phrase their requests differently.
Suggestions
Add more specific concrete actions, e.g., 'configure editor options, handle expression validation, integrate syntax highlighting' to improve specificity.
Include natural keyword variations users might search for, such as 'ArcGIS Arcade', 'expression builder', 'code editor component', or 'embed editor widget'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Arcade expression editor, Coding Components package) and some actions (embed, building authoring/testing/debugging interfaces), but doesn't list multiple concrete actions in detail—e.g., what specific embedding steps, configuration options, or API calls are involved. | 2 / 3 |
Completeness | Clearly answers both 'what' (embed an Arcade expression editor using the Coding Components package) and 'when' ('Use for building Arcade authoring, testing, and debugging interfaces'), with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Arcade expression editor', 'Coding Components', 'authoring', 'testing', 'debugging', but these are fairly niche/technical. Missing common variations a user might say, such as 'ArcGIS Arcade', 'expression builder', 'code editor component', or 'embed editor widget'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche—Arcade expression editor via Coding Components package—making it highly unlikely to conflict with other skills. The combination of 'Arcade' and 'Coding Components' is distinctive. | 3 / 3 |
Total | 10 / 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, actionable skill with excellent concrete code examples and a useful Common Pitfalls section that addresses real developer pain points. Its main weaknesses are moderate verbosity (the content is quite long with some redundancy) and lack of explicit workflow sequencing with validation steps. The progressive disclosure could be improved by moving the detailed API tables and full integration example to separate reference files.
Suggestions
Move the detailed property/method/event tables and the full map integration example to a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the most common patterns.
Add an explicit workflow sequence for integrating the editor (e.g., 1. Load components → 2. Verify with componentOnReady() → 3. Set profile → 4. Listen for diagnostics → 5. Apply expression), with validation checkpoints.
Replace the vague 'Reference Samples' section with specific sample names or links, or remove it entirely if no concrete references exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy—multiple similar examples (minimal editor appears twice) and the property/method/event tables, while useful, are quite extensive. Some descriptions in the tables explain things Claude could infer. However, it avoids explaining basic concepts like what Arcade or web components are. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples for every use case—CDN imports, ESM imports, event listeners, profile configuration, test data setup, snippets, and a complete map integration example. All code is concrete HTML/JavaScript, not pseudocode. | 3 / 3 |
Workflow Clarity | The skill presents clear individual examples but lacks an explicit sequenced workflow for building an editor integration from scratch. The Common Pitfalls section is excellent for error prevention, but there's no step-by-step process with validation checkpoints (e.g., verify component loaded before setting properties, check diagnostics before applying expressions). | 2 / 3 |
Progressive Disclosure | The Related Skills section provides good cross-references, and the content is organized with clear headers. However, the full example with map integration and the extensive property tables could be split into separate reference files. The 'Reference Samples' section is vague ('Search for Arcade-related samples') rather than providing clear links. | 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.