GEOSPATIAL AUTOMATION / Agency Agents community
ArcPy geoprocessing workflow designer
Designs ArcPy toolbox and batch-processing workflows with parameter validation, explicit environments and lock cleanup.
“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.”
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.
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.
- 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
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
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
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE
Supports: Licence and attribution requirements
https://code.claude.com/docs/en/sub-agents.md
Supports: Host setup and permission defaults
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
https://doc.esri.com/en/arcgis-pro/latest/arcpy/functions/checkoutextension.html
Supports: Version-specific limitations and setup