arcgis-pro-automation
Automate controlled local ArcGIS Pro and ArcPy workflows through arcgis-mcp-bridge: inspect .aprx projects and file geodatabases, run geoprocessing, projection, raster, network, spatial-statistics, editing, symbology, and layout export with path and mutation guards. Use when the user explicitly names ArcGIS Pro, ArcPy, .aprx, .gdb, Esri geoprocessing, muend/arcgis-mcp-bridge, its health_check, PathGuard, or confirmation gates, or sketch-to-GIS extraction. Do not trigger for ArcGIS Online or Enterprise administration, QGIS or PyQGIS, generic open-source GIS, or live GUI control of an already-open ArcGIS Pro session.
Install
With your agent
Install OMGSkills skill "muend/geoai-skills:skills/arcgis-pro-automation" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/muend/geoai-skills /tmp/geoai-skills && ln -s /tmp/geoai-skills/skills/arcgis-pro-automation ~/.claude/skills/arcgis-pro-automationFrom README
ArcGIS Pro Automation Operate saved ArcGIS Pro projects and local GIS datasets through the guarded arcgis-mcp-bridge tool surface. Treat the bridge as an execution backend, not as permission to mutate data or claim a result that was never observed. Establish the boundary Require Windows, a licensed ArcGIS Pro , and a bridge worker interpreter that can import ArcPy for real geoprocessing. Use the bridge for local, headless, repeatable ArcPy work. It does not drive the visible ArcGIS Pro UI and does not administer ArcGIS Online or Enterprise. If the bridge tools are not callable, provide or a dry execution plan. Never simulate tool output or imply that an .aprx or .gdb changed. Use the schemas exposed by the connected MCP server. Tool names may be host- namespaced; match the semantic catalog name and never invent parameters. Keep every read and write inside the configured allowed roots. Use absolute paths and a dedicated scratch geodatabase for intermediate outputs.
More from this repo
cartography-geoviz
Always invoke before answering any request to create, compare, design, or review a user-facing map, even if the request...
change-detection
Change analysis, once the observations are comparable.
geo-data-engineering
Always invoke when geospatial data must be acquired, prepared, repaired, scaled, or moved through a repeatable pipeline.