Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Impertio-Studio/QGIS-Claude-Skill-Package --skill qgis-agents-analysis-orchestratorgit clone --depth 1 https://github.com/Impertio-Studio/QGIS-Claude-Skill-PackageWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/impertio-studio/qgis-claude-skill-package/qgis-agents-analysis-orchestrator)<a href="https://agentmods.dev/skills/impertio-studio/qgis-claude-skill-package/qgis-agents-analysis-orchestrator"><img src="https://agentmods.dev/badge/skills/impertio-studio/qgis-claude-skill-package/qgis-agents-analysis-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/impertio-studio/qgis-claude-skill-package/qgis-agents-analysis-orchestrator"><img src="https://agentmods.dev/badge/skills/impertio-studio/qgis-claude-skill-package/qgis-agents-analysis-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00100 | $0.04219 |
| Opus 5 | $0.00050 | $0.02109 |
| Sonnet 5 | $0.00020 | $0.00844 |
| Haiku 4.5 | $0.00010 | $0.00422 |
Grade A, and why
qgis-agents-analysis-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qgis-agents-analysis-orchestrator
Quick Reference
This skill is an orchestrator — it guides analysis method selection and workflow ordering. It does NOT contain implementation details. For implementation, refer to the specific skill indicated by the decision trees.
When to Use This Skill
| Trigger | Action |
|---|---|
| "Analyze spatial data" | Start at Decision Tree 1: Analysis Type |
| "Which algorithm should I use?" | Go to Algorithm Selection Guide |
| "Chain multiple operations" | Go to Workflow Patterns |
| "What format should I use?" | Go to Format Selection |
| "Which CRS for my analysis?" | Go to CRS Selection |
| "Connect Claude to QGIS" | Go to MCP Integration |
Critical Warnings
NEVER start coding before completing the workflow plan. ALWAYS determine: (1) analysis type, (2) CRS, (3) input format, (4) algorithm chain, (5) output format.
NEVER mix vector and raster operations without explicit conversion steps. ALWAYS include rasterize/vectorize as a named step.
NEVER chain algorithms with mismatched CRS. ALWAYS reproject to a common CRS as the FIRST step.
NEVER use geographic CRS (EPSG:4326) for distance or area calculations. ALWAYS reproject to a projected CRS first.
NEVER assume third-party provider algorithms (GRASS, SAGA) are available. ALWAYS check availability with QgsApplication.processingRegistry().algorithmById() and fall back to native: algorithms.
NEVER hardcode file paths. ALWAYS use QgsProcessing.TEMPORARY_OUTPUT or 'memory:' for intermediate results.
ALWAYS wrap processing.run() in try/except for QgsProcessingException.
ALWAYS check layer.isValid() after loading any layer.
ALWAYS create spatial indexes (native:createspatialindex) before spatial queries on large datasets.
Decision Tree 1: Analysis Type Selection
What is your primary question?
│
├─ "How are features distributed spatially?"
│ └─ VECTOR ANALYSIS → Decision Tree 2
│
├─ "What is the value at this location?" / "How does a surface vary?"
│ └─ RASTER ANALYSIS → Decision Tree 3
│
├─ "What is the shortest/fastest route?" / "What areas are reachable?"
│ └─ NETWORK ANALYSIS → Decision Tree 4
│
├─ "How do two datasets relate spatially?"
│ ├─ Both datasets are vector → VECTOR OVERLAY → Decision Tree 2
│ ├─ Both datasets are raster → RASTER CELL STATISTICS → Decision Tree 3
│ └─ One vector + one raster → HYBRID ANALYSIS:
│ ├─ Extract raster values at vector locations → `native:rastersampling`
│ ├─ Summarize raster within vector zones → `native:zonalstatisticsfb`
│ └─ Convert vector to raster first → `gdal:rasterize` then Decision Tree 3
│
├─ "Create a continuous surface from point samples?"
│ └─ INTERPOLATION:
│ ├─ Sparse, irregular points → `native:tininterpolation`
│ ├─ Dense, regular points → `native:idwinterpolation`
│ └─ Event density visualization → `native:heatmapkerneldensityestimation`
│
└─ "Classify or cluster features?"
└─ CLUSTERING:
├─ Known number of groups → `native:kmeansclustering`
├─ Unknown groups, density-based → `native:dbscanclustering`
└─ Spatiotemporal data → `native:stdbscanclustering`
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 414 lines · 100 tokens per session scan A fd0aa3fb7f09
qgis-agents-analysis-orchestrator is a skill published in the GitHub repository Impertio-Studio/QGIS-Claude-Skill-Package (33 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 4,219 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
opengis-all
Use when navigating end-to-end GIS workflows — discover the full toolchain from GDAL data processing through GeoServer publishing to CesiumJS/OpenLayers visualization. One-stop index covering the complete open-source GIS data pipeline.
open-map-stack
Use textual agent instructions for GIS and geospatial work: source discovery and provenance, vector/raster/point-cloud pipelines, CRS and metric analysis, spatial SQL, routing and isochrones, QGIS projects, tile generation, and web maps. Use advanced tools and formats such as OSM, Overture, STAC, Sentinel/Landsat…
opengis-daf
Use when building plan-driven GIS data analysis or data quality-check pipelines with OpenGisDAF (.NET 10 / C# 14): define buffer, clip, intersect/containment checks, coordinate transform, field calculator, attribute/geometry QC rules purely in JSON plans, run the daf CLI, chain operators via DAG upstream bindings…
gdal
Use when processing geospatial raster/vector data via command line — format conversion (Shapefile to GeoJSON), reprojection, DEM analysis, NDVI calculation, mosaicking. GDAL/OGR CLI: the industry standard for batch geospatial data processing with 50+ command-line tools (ogr2ogr, gdalwarp, gdaltranslate, gdalcalc).
gis-skills
Use when processing geospatial data, publishing map services, querying spatial databases, performing geometry operations, or building web map applications. Index of 24 skills: GDAL, GeoServer, QGIS, PostGIS, JTS, GeoPandas, Shapely, CesiumJS, OpenLayers, NetTopologySuite, OpenGisDAF and more.
swmm-end-to-end
Top-level orchestration skill for agentic SWMM modelling. Use when an agent needs one entrypoint that decides which module tools to run, in what order, and when to stop, for example to build, run, QA, and optionally calibrate a SWMM case from prepared or partially prepared inputs.