arcgis-embeddable-maps
Embed lightweight, self-contained maps in web pages using the Embeddable Components package. Use for quick map embeds with minimal code and built-in UI controls.
78
72%
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-embeddable-maps/SKILL.mdQuality
Discovery
67%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 both a 'what' and 'when' clause, earning good marks on completeness. However, it lacks specificity in concrete actions (e.g., adding markers, popups, tile layers) and could include more natural trigger terms users would use when requesting map functionality. The distinctiveness is moderate—it could better differentiate itself from other mapping approaches.
Suggestions
Add specific concrete actions like 'add markers, popups, tile layers, and zoom controls' to improve specificity.
Include more natural trigger terms users might say, such as 'interactive map', 'map widget', 'embed a map', 'location map', or specific technology names if applicable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (maps in web pages) and mentions some actions ('embed lightweight, self-contained maps'), but doesn't list multiple specific concrete actions like adding markers, setting coordinates, configuring layers, etc. | 2 / 3 |
Completeness | It answers both 'what' (embed lightweight, self-contained maps in web pages using the Embeddable Components package) and 'when' ('Use for quick map embeds with minimal code and built-in UI controls'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'maps', 'web pages', 'map embeds', 'Embeddable Components', but misses common user variations like 'Leaflet', 'interactive map', 'Google Maps alternative', 'map widget', or specific file/framework references users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Embeddable Components package' adds some specificity, but 'maps in web pages' could overlap with other mapping skills (e.g., Leaflet, Mapbox, Google Maps). The description doesn't clearly distinguish what makes this approach unique beyond 'minimal code'. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
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 well-structured API reference skill with excellent actionability - all examples are concrete, executable, and cover the key use cases. The main weakness is verbosity: the document could be significantly shorter by condensing repetitive examples and moving detailed property tables or pitfalls to a reference file. The common pitfalls section, while useful, is overly detailed with anti-pattern/correct pairs that pad the token count.
Suggestions
Consolidate the 7 basic usage examples into 2-3 that demonstrate multiple features at once, rather than showing each attribute variation separately.
Consider moving the full property tables and common pitfalls to a separate reference file, keeping only the most critical pitfalls (missing script, missing size) inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy - the common pitfalls section repeats information already clear from the properties table and examples (e.g., item-id being required). The extensive list of usage examples with minor variations (dark theme, custom center, API key) could be condensed. The property tables are efficient, but overall the document is longer than necessary. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready HTML and JavaScript examples. Import patterns for both CDN and ESM are concrete, the full CDN example is a complete working page, and programmatic configuration examples are specific and executable. | 3 / 3 |
Workflow Clarity | For a simple, single-purpose skill (embedding a map component), the workflow is clear and unambiguous. The import patterns establish the setup sequence, examples show usage, and common pitfalls provide validation guidance for what can go wrong. No destructive or batch operations are involved, so explicit validation checkpoints aren't needed. | 3 / 3 |
Progressive Disclosure | The document has good section organization and references related skills at the bottom, but it's quite long with inline content that could be split out (e.g., the extensive common pitfalls section, the full property tables). The reference samples section is nearly empty. For a skill of this length (~200+ lines), more content could be offloaded to reference files. | 2 / 3 |
Total | 10 / 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.