arcgis-scene-environment
Configure SceneView environment settings including shadows, lighting, backgrounds, underground navigation, and elevation modes. Use for realistic 3D visualizations.
77
66%
Does it follow best practices?
Impact
97%
1.59xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/4.34/skills/arcgis-scene-environment/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 well at listing specific capabilities within a clearly defined niche (SceneView environment configuration), making it distinctive and specific. However, the 'when' clause is weak—it states a broad goal ('realistic 3D visualizations') rather than providing explicit trigger conditions with natural user language. Adding more natural trigger terms and a proper 'Use when...' clause would significantly improve skill selection accuracy.
Suggestions
Expand the 'Use when...' clause with explicit trigger conditions, e.g., 'Use when the user asks about SceneView environment settings, 3D scene lighting, shadow configuration, or underground navigation.'
Add natural keyword variations users might say, such as '3D scene', 'scene view', 'ArcGIS SceneView', 'WebScene', 'atmosphere settings', or 'ground transparency'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring shadows, lighting, backgrounds, underground navigation, and elevation modes. These are distinct, identifiable capabilities within the SceneView environment domain. | 3 / 3 |
Completeness | The 'what' is well-covered (configure environment settings including specific features), but the 'when' clause ('Use for realistic 3D visualizations') is vague and doesn't provide explicit trigger guidance like 'Use when the user asks about...' with natural language triggers. It describes a goal rather than trigger conditions. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'SceneView', 'shadows', 'lighting', 'backgrounds', '3D visualizations', but misses common user variations such as '3D scene', 'scene view settings', 'ArcGIS', 'WebScene', or 'environment settings'. The 'Use for realistic 3D visualizations' is somewhat generic as a trigger. | 2 / 3 |
Distinctiveness Conflict Risk | SceneView environment settings is a very specific niche. The combination of 'SceneView', 'shadows', 'lighting', 'underground navigation', and 'elevation modes' creates a clear, distinct identity that is unlikely to conflict with other skills. | 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 reference skill with highly actionable, executable code examples covering a wide range of SceneView environment configurations. Its main weaknesses are length/redundancy (environment settings repeated across sections) and a monolithic structure that would benefit from splitting advanced topics like screenshots and focus areas into separate files. The Common Pitfalls section adds good value but could be integrated as inline warnings within relevant sections.
Suggestions
Reduce redundancy by consolidating repeated environment configuration patterns (atmosphere, stars, lighting appear in multiple sections) into a single reference section
Split advanced topics like Screenshot Capture and Focus Area into separate referenced files to improve progressive disclosure and reduce the main file's length
Add brief validation notes inline where configuration requires multiple coordinated settings (e.g., transparent background needs both alphaCompositingEnabled AND background color with 0 alpha)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy—environment configuration patterns are repeated across multiple sections (e.g., atmosphere/stars settings appear in basic config, atmosphere section, and complete example). Some sections like the complete HTML example largely duplicate earlier snippets. However, it avoids explaining basic concepts Claude would know. | 2 / 3 |
Actionability | All code examples are concrete, executable JavaScript/HTML snippets with specific property names, values, and patterns. The examples are copy-paste ready and cover both the Map Components API and Core API approaches with real configuration objects. | 3 / 3 |
Workflow Clarity | The skill is organized by feature area rather than workflows, which is appropriate for a configuration-focused skill. However, for operations like transparent backgrounds (requiring alphaCompositingEnabled) and underground navigation (requiring multiple settings), the steps could be more explicitly sequenced with validation. The Common Pitfalls section helps but validation checkpoints are absent. | 2 / 3 |
Progressive Disclosure | The content is quite long (~300 lines) and could benefit from splitting detailed sections (screenshots, focus areas) into separate files. There is one cross-reference to the arcgis-core-maps skill and a reference samples section, but the main file is monolithic with all content inline rather than appropriately split. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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 (521 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.