arcgis-portal-content
Manage portal content including saving WebMaps/WebScenes, bookmarks, slides, and portal items. Use for content persistence, WebMap/WebScene configuration, and navigation presets.
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-portal-content/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 does a good job listing specific capabilities in the portal/GIS content management domain and is highly distinctive. However, the 'when to use' clause essentially restates the capabilities in different words rather than providing explicit trigger conditions, and some terms are overly technical rather than matching natural user language.
Suggestions
Rewrite the 'Use for...' clause as explicit trigger guidance, e.g., 'Use when the user asks to save, update, or configure WebMaps, WebScenes, bookmarks, slides, or other portal items.'
Add more natural user-facing trigger terms such as 'save my map', 'update portal content', 'create a bookmark', or 'manage slides' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: saving WebMaps/WebScenes, bookmarks, slides, and portal items. Also mentions content persistence, configuration, and navigation presets. | 3 / 3 |
Completeness | The 'what' is well covered (manage portal content, saving WebMaps/WebScenes, bookmarks, slides, portal items). The 'when' is present but weak — 'Use for content persistence, WebMap/WebScene configuration, and navigation presets' restates capabilities rather than providing explicit trigger guidance like 'Use when the user wants to save or update portal content'. | 2 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'WebMaps', 'WebScenes', 'bookmarks', 'slides', 'portal items' which are relevant but fairly technical. Missing more natural user phrases like 'save my map', 'update portal', or file format references. Users may not naturally say 'content persistence' or 'navigation presets'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche — ArcGIS/portal content management with WebMaps, WebScenes, bookmarks, and slides. These are highly distinctive terms unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%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 API reference skill with excellent actionability — nearly every section has executable code examples covering WebMap/WebScene creation, saving, bookmarks, slides, and portal item management. Its main weakness is the lack of explicit workflow sequences with validation checkpoints for save operations, and some sections could be trimmed to improve conciseness. The progressive disclosure and cross-referencing to related skills is well done.
Suggestions
Add an explicit numbered workflow for the save process with validation checkpoints (e.g., 1. Authenticate, 2. Load map, 3. updateFrom(view), 4. Verify view state captured, 5. save/saveAs, 6. Confirm saved item ID).
Trim sections like Portal User Information and Portal Folders that read as generic API reference rather than task-specific guidance, or move them to a separate reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy (e.g., multiple similar save patterns, both ESM and CDN import patterns) and could be tightened. Some sections like Portal User Information and Portal Folders feel like padding for an API reference rather than targeted skill content. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — from creating WebMaps, saving them, managing bookmarks, querying portal items, to a complete HTML save example. Every section includes concrete, runnable JavaScript/HTML code with specific API calls. | 3 / 3 |
Workflow Clarity | The 'Common Pitfalls' section highlights the critical updateFrom-before-save sequence and authentication requirements, which serves as implicit workflow guidance. However, there are no explicit numbered workflow sequences with validation checkpoints for the save operations, which involve destructive/persistent changes to portal content. The save workflow should have explicit validation steps. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear section headers, a reference samples list at the bottom for deeper exploration, and cross-references to related skills (authentication, maps, layers). Content is appropriately organized with one-level-deep references and easy navigation. | 3 / 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.