crs-discipline — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited crs-discipline (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Coordinate reference systems are the #1 source of silent, serious GIS errors. Before any spatial operation, know the CRS of every dataset, and make them match.
.prj for a shapefile, the SRID in PostGIS, the spatial reference of a feature class, gdf.crs in GeoPandas. Never start a spatial operation on data whose CRS you haven't confirmed..prj, an SRID of 0 or "unknown" — is the classic trap: it lines up perfectly on the author's machine but is meaningless anywhere else. Do not assume it's WGS84. Infer the likely CRS from the coordinate ranges (values in −180..180 → geographic degrees; large numbers in meters or feet → projected) and confirm with the source before proceeding.Define Projection vs Project in ArcPy, ST_SetSRID vs ST_Transform in PostGIS, .set_crs() vs .to_crs() in GeoPandas. Know which one the situation calls for.A CRS mismatch rarely throws an error — it returns confident, wrong answers: features that don't intersect when they should, distances off by orders of magnitude, layers stacked in the wrong hemisphere. These bugs look like valid output, so they pass review and reach the map, where someone in the field catches them. Thirty seconds of CRS checking prevents an entire class of them.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.