---
title: "ArcPy geoprocessing workflow designer: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/agency-gis-geoprocessing-specialist/
description: "Designs ArcPy toolbox and batch-processing workflows with parameter validation, explicit environments and lock cleanup."
---

# ArcPy geoprocessing workflow designer: review, role & definition · Undominated.ai

> Designs ArcPy toolbox and batch-processing workflows with parameter validation, explicit environments and lock cleanup.

[← Explore all agents](/agents/)

GEOSPATIAL AUTOMATION / Agency Agents community

# ArcPy geoprocessing workflow designer

Designs ArcPy toolbox and batch-processing workflows with parameter validation, explicit environments and lock cleanup.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/gis/gis-geoprocessing-specialist.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 5 linked sources
 Publisher Agency Agents community
 Licence [MIT ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE)
 Revision bd956db032d9
 [Read what was—and wasn’t—checked ↓](#review)

“ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.”

 [Agency Agents community · upstream description ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/gis/gis-geoprocessing-specialist.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The definition calls for dependent-parameter validation and user-facing error/progress reporting before long-running processing.
- It names workspace, extent and output coordinate system as explicit settings and requires cursor/lock cleanup.
- It specifies Python toolboxes with validation before execution, explicit arcpy environments, and da cursors rather than a one-off map.
- The when-not section sends a single Pro analysis to the GIS analyst profile and a full pipeline to a spatial data engineer.

### A good fit for

 - Provide the manual spatial workflow, ArcGIS Pro version/licence, input schemas and target outputs.
- Receive a .pyt/model/script design with validation, logging, intermediate-data cleanup and realistic-data test cases.
- Designing a reusable .pyt tool with parameter validation and progress reporting.
- Catching ArcMap-era licence and map-series wording before treating it as current ArcGIS Pro practice.

### Weigh up before choosing

 - The source mixes legacy Data Driven Pages terminology into Pro guidance; current Esri documentation calls this Map Series and says it is not a geoprocessing toolset.
- The source mandates extension checkout/checkin, but Esri documents CheckOutExtension as a no-op from Pro 3.7; adapt licence handling to the installed version.
- ArcPy, licensed extensions and GIS datasets are not included; this is source-only guidance requiring version-specific adaptation.
- For Claude Code, adapt the display name to lowercase hyphenated form and use a supported named color in a working copy; original download bytes remain unchanged.
- Source-only listing: inspect the upstream context and referenced dependencies before adapting this definition.
- The pattern table lists Data Driven Pages as the Model Builder side of a map series. Esri's FAQ says ArcGIS Pro uses the term Map Series and that Map Series is not a geoprocessing toolset.
- The rules say to check extensions out and back in. Esri's ArcGIS Pro 3.7 CheckOutExtension page says that function no longer performs any action and is not required for extension tools.
- No tools field is set. The profile does not launch ArcGIS Pro or check a licence.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - gis/gis-geoprocessing-specialist.md (complete definition)
- LICENSE (applicable redistribution terms)
- Host custom-agent documentation; repository installation guidance where applicable

### Our findings

 - The definition calls for dependent-parameter validation and user-facing error/progress reporting before long-running processing.
- It names workspace, extent and output coordinate system as explicit settings and requires cursor/lock cleanup.
- Toolbox rules require invalid inputs to fail before execution and require SetProgressor for work over five seconds.
- The automation table pairs arcpy.mp layout export with Data Driven Pages. Esri's published FAQ uses Map Series for that Pro capability and says it is not a geoprocessing toolset.
- Check-out instructions in the profile are not qualified by version. The current CheckOutExtension document says that starting with ArcGIS Pro 3.7 the function has no effect.
- Frontmatter does not declare tools, and the Markdown does not register a host subagent by itself.

### Not established by this review

 - No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
- The resource was not executed and its tools were not called.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://code.claude.com/docs/en/sub-agents.md)
 - Read the pinned definition and MIT licence; review the host permissions before use.
- Use the original as a role reference; for .claude/agents/ create a host-valid working copy, supply the project inputs and constrain tools to the agreed files/environment.
- Provide the manual spatial workflow, ArcGIS Pro version/licence, input schemas and target outputs.

### Before you start

 - A host supporting adapted Markdown agent definitions
- The selected GIS/game toolchain and authorized project assets

### Compatibility

Claude Code

### Implementation

Markdown

### Host-mediated repository and tool access

 - No tool allowlist is declared; the orchestrating host must explicitly bound file, shell and network permissions.

### Cost model

The definition is reusable under its stated licence. Host/model usage, execution environments and connected services can incur separate charges.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Complete upstream definition at reviewed commit ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/gis/gis-geoprocessing-specialist.md) Checked 2026-10-14 https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/gis/gis-geoprocessing-specialist.md Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations
- [Applicable upstream redistribution licence ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE) Checked 2026-10-14 https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE Supports: Licence and attribution requirements
- [Host custom-agent configuration ↗](https://code.claude.com/docs/en/sub-agents.md) Checked 2026-10-14 https://code.claude.com/docs/en/sub-agents.md Supports: Host setup and permission defaults
- [Esri Map Series terminology ↗](https://support.esri.com/en-us/knowledge-base/faq-does-arcgis-pro-have-the-data-driven-pages-function-000015711) Checked 2026-10-14 https://support.esri.com/en-us/knowledge-base/faq-does-arcgis-pro-have-the-data-driven-pages-function-000015711 Supports: Version-specific limitations and setup
- [Esri version-dependent extension licensing ↗](https://doc.esri.com/en/arcgis-pro/latest/arcpy/functions/checkoutextension.html) Checked 2026-10-14 https://doc.esri.com/en/arcgis-pro/latest/arcpy/functions/checkoutextension.html Supports: Version-specific limitations and setup

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
