Content
50%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The core technical content (usage triggers, dependencies, executable example, CRS/join/overlay implementation notes) is solid and actionable. However, the second half of the file is generic boilerplate padding, and the reference bundle, while real, is poorly signaled, dragging down efficiency and navigation.
Suggestions
Delete or collapse the generic template sections (When Not to Use, Required Inputs, Recommended Workflow, Deterministic Output Rules, Output Contract, Validation and Safety Rules, Failure Handling, Completion Checklist, Quick Validation, Scope Reminder) — they add ~60% of the body without geopandas-specific content.
Replace the parenthetical reference list with per-topic pointers in the relevant sections, e.g., under CRS rules: 'See references/crs-management.md for EPSG selection guidance', so each reference is clearly signaled where it is needed.
Add a concrete validation checkpoint to the example, such as 'if gdf.crs is None: gdf = gdf.set_crs("EPSG:4326")' before to_crs, to give the workflow a real feedback step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The technical half (When to Use, Key Features, Dependencies, Example Usage, Implementation Details) is lean, but roughly ten trailing sections (When Not to Use, Required Inputs, Recommended Workflow, Deterministic Output Rules, Output Contract, Validation and Safety Rules, Failure Handling, Completion Checklist, Quick Validation, Scope Reminder) are generic template padding that add no geopandas-specific value, and 'Scope Reminder' repeats the description verbatim. | 2 / 5 |
Actionability | The example is complete, runnable code covering read, CRS inspection, reprojection, buffer, plot, and write, and Implementation Details gives real API signatures (sjoin predicate=, sjoin_nearest max_distance=, overlay how=). Minor gaps: pipe-syntax signatures are illustrative rather than literal, no install command, and the boilerplate sections give only vague direction. | 4 / 5 |
Workflow Clarity | The commented 6-step example sequences clearly and reprojecting before metric calculations is a real checkpoint, but there are no validation or feedback loops (e.g., guarding against a missing CRS before to_crs) and 'Recommended Workflow' is abstract boilerplate rather than geopandas-specific steps. | 3 / 5 |
Progressive Disclosure | Six real one-level-deep reference files exist and are named in the body, but they are buried in a single parenthetical list at the end of Key Features with no per-topic signaling or links, and Implementation Details partially duplicates content that belongs in those references. | 3 / 5 |
Total | 12 / 20 Passed |