CtrlK
BlogDocsLog inGet started
Tessl Logo

arcgis-online

ArcGIS Online integration. Manage data, records, and automate workflows. Use when the user wants to interact with ArcGIS Online data.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/arcgis-online/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, executable reference with concrete Membrane CLI commands and a useful actions table, sequenced through connection setup with state polling. Its main gaps are an unnecessary product primer, and the absence of validation/confirmation checkpoints around the destructive delete actions it advertises.

Suggestions

Trim the opening paragraph that defines ArcGIS Online (Claude already knows this) and remove the 'Think of it as Google Maps' analogy.

Add an explicit validation/confirmation step before destructive actions (e.g., 'Before running delete-item or delete-group, confirm the target ID with the user and consider a get-* call first').

Provide one worked end-to-end example (e.g., connect → search-items → get-item → delete-item with confirmation) to turn the scattered commands into a single executable narrative.

DimensionReasoningScore

Conciseness

The bulk is efficient command examples, but the intro ('ArcGIS Online is a cloud-based mapping and analysis platform... Think of it as Google Maps but for professional use') over-explains what the product is, and the sparse Overview tree adds little, fitting 'mostly efficient but includes some unnecessary explanation' rather than 4.

3 / 5

Actionability

Concrete, copy-paste-ready commands with flags cover the common cases (install, login, connection ensure, action list/run, request proxy) plus a full popular-actions table, but placeholders like CONNECTION_ID and the lack of a worked end-to-end example leave minor gaps versus the 5 anchor.

4 / 5

Workflow Clarity

The connection workflow is well-sequenced with state polling (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the skill lists destructive actions (Delete Item, Delete Group) with no pre-run validation or confirmation checkpoint, so per the destructive-operation cap it cannot exceed 3.

3 / 5

Progressive Disclosure

The single SKILL.md is organized into clear, well-labeled sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no deep nesting; at ~150 lines it is over the simple-skill threshold, so it lands at 'good structure; minor organization gaps' rather than 5.

4 / 5

Total

14

/

20

Passed

Description

62%Weight 40%Scale 1-5

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 well-structured with both a capability statement and an explicit 'Use when' trigger, and the named product makes it distinct. Its weakness is generic verbs ('manage', 'automate') and missing natural synonyms like 'GIS', 'maps', and 'geospatial' that users would actually say.

Suggestions

Replace generic verbs with concrete ArcGIS actions, e.g. 'Create and share maps, search and manage items, groups, and users, and automate geospatial workflows.'

Expand the trigger to include natural synonyms: 'Use when the user wants to work with ArcGIS Online data, maps, GIS layers, or geospatial content.'

Mention the file/extension context if applicable (e.g., hosted feature layers, web maps) to sharpen distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('ArcGIS Online integration') plus a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete GIS operations like creating maps or analyzing layers, so it sits at the '1-2 concrete actions, not comprehensive' anchor rather than 4.

3 / 5

Completeness

It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with ArcGIS Online data' trigger, but the 'when' is generic rather than listing concrete trigger phrases, so it fits 'has both; when could be more specific' instead of 5.

4 / 5

Trigger Term Quality

The product name 'ArcGIS Online' and 'data' are natural terms, but it omits common synonyms a user would actually say ('GIS', 'maps', 'geospatial', 'layers'), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The named product 'ArcGIS Online' gives it a clear niche with low conflict risk, but the generic action verbs leave minor overlap risk with adjacent Esri/GIS skills, placing it at 'mostly distinct; minor overlap' rather than the 5 anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.