How do I install the Arcpy Vs Arcgis API skill?

Run npx skillmds@latest add buildmoonshot/arcpy-vs-arcgis-api in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Arcpy Vs Arcgis API safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Arcpy Vs Arcgis API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Arcpy Vs Arcgis API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Arcpy Vs Arcgis API?

buildmoonshot (@buildmoonshot) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Arcpy Vs Arcgis API by buildmoonshot

Name: Arcpy Vs Arcgis API
Author: buildmoonshot

Arcpy Vs Arcgis API

Use when starting an Esri/ArcGIS automation task and choosing how to connect — deciding between ArcPy and the ArcGIS API for Python. Makes the agent pick the right library for the environment (local Pro/desktop geoprocessing vs web/Enterprise/Online feature services) instead of forcing the wrong one.

buildmoonshot 48b8264 2 files · 3.6 KB Updated Sep 17, 2026

File contents

ArcPy vs. ArcGIS API for Python

Esri has two Python doors, and picking the wrong one means a missing license, an impossible deploy, or a 10x-harder script. Choose deliberately before writing code.

ArcPy — local Pro/Desktop + geoprocessing

Runs inside the ArcGIS Pro/Desktop Python environment; needs a Pro license and install.
Best for: heavy geoprocessing tools, editing local file geodatabases and enterprise (SDE) data, raster analysis, script/model tools, anything that leans on the desktop toolbox.
Auth/context comes from the Pro install.

ArcGIS API for Python (`arcgis`) — web GIS over REST

Talks to ArcGIS Online / Enterprise / Portal over REST; no Pro install required.
Best for: querying and editing hosted feature layers/services, portal/content/user administration, web maps, publishing, and running in a server, notebook, or CI without a desktop license.
Auth is explicit: GIS(url, user, pwd) / tokens.

The decision

Local/SDE geodatabase + geoprocessing tools? → ArcPy.
Hosted feature service / portal content / web layer, or running license-free on a server? → ArcGIS API for Python.
Both are legitimate in one pipeline (e.g., ArcPy to process locally, the API to publish the result) — just don't force one into the other's job.

Don't do this

Don't reach for ArcPy in a license-less server/CI context — it won't import.
Don't try to push heavy local geoprocessing through the web API, or hand-roll REST calls when arcgis already wraps them.

Why this matters

This choice is made before any code, and it's expensive to reverse: discover it late and you've written a script that can't run where it needs to. Naming the environment (desktop vs web, licensed vs not) and the data (local gdb vs hosted service) up front picks the right tool the first time.

---name: arcpy-vs-arcgis-apidescription: Use when starting an Esri/ArcGIS automation task and choosing how to connect — deciding between ArcPy and the ArcGIS API for Python. Makes the agent pick the right library for the environment (local Pro/desktop geoprocessing vs web/Enterprise/Online feature services) instead of forcing the wrong one.---# ArcPy vs. ArcGIS API for PythonEsri has two Python doors, and picking the wrong one means a missing license, an impossible deploy, or a 10x-harder script. Choose deliberately before writing code.## ArcPy — local Pro/Desktop + geoprocessing- Runs inside the **ArcGIS Pro/Desktop** Python environment; needs a Pro license and install.- Best for: heavy **geoprocessing** tools, editing **local file geodatabases and enterprise (SDE)** data, raster analysis, script/model tools, anything that leans on the desktop toolbox.- Auth/context comes from the Pro install.## ArcGIS API for Python (`arcgis`) — web GIS over REST- Talks to **ArcGIS Online / Enterprise / Portal** over REST; **no Pro install required.**- Best for: querying and editing **hosted feature layers/services**, portal/content/user administration, web maps, publishing, and running in a **server, notebook, or CI** without a desktop license.- Auth is explicit: `GIS(url, user, pwd)` / tokens.## The decision- Local/SDE geodatabase + geoprocessing tools? → **ArcPy.**- Hosted feature service / portal content / web layer, or running license-free on a server? → **ArcGIS API for Python.**- Both are legitimate in one pipeline (e.g., ArcPy to process locally, the API to publish the result) — just don't force one into the other's job.## Don't do this- Don't reach for ArcPy in a license-less server/CI context — it won't import.- Don't try to push heavy local geoprocessing through the web API, or hand-roll REST calls when `arcgis` already wraps them.## Why this mattersThis choice is made *before* any code, and it's expensive to reverse: discover it late and you've written a script that can't run where it needs to. Naming the environment (desktop vs web, licensed vs not) and the data (local gdb vs hosted service) up front picks the right tool the first time.

Frequently asked questions