arcgis-feature-effects
Apply visual effects, filters, focus areas, and blend modes to map layers. Use for highlighting features, spatial filtering, display filters, and CSS-like visual emphasis.
76
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-feature-effects/SKILL.mdQuality
Discovery
77%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly states both capabilities and usage triggers. It names concrete actions (visual effects, filters, focus areas, blend modes) applied to a specific domain (map layers). The main weakness is that some trigger terms are somewhat technical ('spatial filtering', 'display filters') and could overlap with non-map-related styling or filtering skills.
Suggestions
Add more natural user-facing trigger terms like 'layer opacity', 'map styling', 'highlight regions', or specific mapping library names to improve discoverability.
Strengthen distinctiveness by specifying the mapping context more explicitly, e.g., mentioning GIS, web maps, or specific frameworks to reduce overlap with general CSS/visual styling skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'visual effects, filters, focus areas, and blend modes to map layers.' These are distinct, actionable capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Apply visual effects, filters, focus areas, and blend modes to map layers') and when ('Use for highlighting features, spatial filtering, display filters, and CSS-like visual emphasis'), with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'visual effects', 'filters', 'blend modes', 'map layers', and 'CSS-like visual emphasis', but misses common user terms like 'opacity', 'transparency', 'layer styling', 'map styling', or specific tool names (e.g., Leaflet, Mapbox). 'Spatial filtering' and 'display filters' are somewhat technical. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'map layers' with visual effects creates a somewhat specific niche, but terms like 'filters', 'visual effects', and 'CSS-like visual emphasis' could overlap with general CSS styling or image processing skills. The map-specific context helps but isn't strongly distinctive. | 2 / 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 comprehensive, highly actionable reference for ArcGIS feature effects with excellent code examples covering the full API surface. Its main weaknesses are verbosity from redundant individual effect examples that repeat a trivial pattern, and a monolithic structure that could benefit from splitting detailed reference content into separate files. The common pitfalls section is a strong addition that adds genuine value beyond what Claude would know.
Suggestions
Consolidate the individual effect examples (Opacity, Grayscale, Blur, Drop Shadow, Bloom, Brightness/Contrast) into 1-2 combined examples since they all follow the identical pattern and the reference table already documents syntax.
Move the detailed blend mode categories table, spatial relationships table, and FocusArea properties into a separate REFERENCE.md file, keeping only the most common patterns inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes redundant individual effect examples (opacity, grayscale, blur, drop-shadow, bloom, brightness/contrast) that all follow the same trivial pattern and could be consolidated into the reference table. The effect types reference table already covers syntax, making the individual examples largely redundant. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready JavaScript code with concrete property values, real filter expressions, and complete object structures. The import patterns, autocasting notes, and interactive examples (click, slider, histogram) are all directly usable. | 3 / 3 |
Workflow Clarity | The skill covers many independent patterns well but lacks explicit multi-step workflows with validation checkpoints. For example, the 'Combining Display Filter with Feature Effect' and interactive sections don't include verification steps (e.g., checking if the effect was applied, handling null results from hitTest). The common pitfalls section partially compensates but is reactive rather than integrated into workflows. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a reference samples section pointing to external examples. However, at ~350+ lines, significant content (individual effect examples, full blend mode tables, focus area details) could be split into separate reference files. The 'Related Skills' section provides good cross-references, but the main file is monolithic for its scope. | 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 (511 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.