create-spatial-visualization

create-spatial-visualization is a skill for Claude Code from pjt222/agent-almanac. It costs 111 tokens per session (2,943 once invoked), scanned A, original, MIT.

A workflow for turning route data such as GPX files, latitude and longitude points, or GeoJSON into maps and elevation profiles. It can produce interactive maps, static images, and web-based visualizations.

In plain words
What is it for?
Mapping hiking or cycling routes, showing elevation changes, placing points of interest on a map, and creating spatial trip dashboards or report graphics.
Why use it?
It removes the need to manually plot routes and combine them with markers, boundaries, or terrain information. It also addresses coordinate-system handling and map export.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the agent-almanac plugin — 122 skills, 76 agents shipped together

Good fit Mapping hiking or cycling routes, showing elevation changes, placing points of interest on a map, and creating spatial trip dashboards or report graphics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pjt222/agent-almanac/create-spatial-visualization
Install

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.

Any agent
npx skills add pjt222/agent-almanac --skill create-spatial-visualization
Clone the repo
git clone --depth 1 https://github.com/pjt222/agent-almanac

Made for: Claude Code.

Or install agent-almanac, the plugin that ships this one along with the rest of its 122 skills, 76 agents.

Wrote 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.

agentmods badge for create-spatial-visualization

README.md
[![agentmods](https://agentmods.dev/badge/skills/pjt222/agent-almanac/create-spatial-visualization.svg)](https://agentmods.dev/skills/pjt222/agent-almanac/create-spatial-visualization)
Your own site
<a href="https://agentmods.dev/skills/pjt222/agent-almanac/create-spatial-visualization"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/create-spatial-visualization.svg" alt="Measured on agentmods" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,943 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00111 $0.02943
Opus 5 $0.00056 $0.01471
Sonnet 5 $0.00022 $0.00589
Haiku 4.5 $0.00011 $0.00294

Measured 4d ago against content hash 0be8ddcff7f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

create-spatial-visualization 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 4d 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.

i18n/caveman-lite/skills/create-spatial-visualization/SKILL.md · 270 lines

How it starts

The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Spatial Visualization

Create interactive maps, elevation profiles, and spatial visualizations from GPX tracks, waypoints, or route data.

When to Use

  • Visualizing a planned or completed tour route on an interactive map
  • Creating elevation profiles for hiking or cycling routes
  • Overlaying waypoints, POIs, and route corridors on a basemap
  • Generating static map images for print reports
  • Building a web-based trip dashboard with spatial data

Inputs

  • Required: Spatial data source (GPX file, CSV with lat/lon, GeoJSON, or waypoint list)
  • Required: Visualization type (interactive map, static map, elevation profile, heatmap)
  • Optional: Basemap preference (OpenStreetMap, satellite, terrain, topo)
  • Optional: Styling parameters (colors, line width, marker icons)
  • Optional: Output format (HTML widget, PNG, SVG, embedded in Quarto)
  • Optional: Additional layers (POI markers, area boundaries, distance markers)

Procedure

Step 1: Import Spatial Data

Load and parse the spatial data into a usable format.

R approach (sf package):

# GPX file
track <- sf::st_read("route.gpx", layer = "tracks")
waypoints <- sf::st_read("route.gpx", layer = "waypoints")

# CSV with coordinates
points <- readr::read_csv("stops.csv") |>
  sf::st_as_sf(coords = c("lon", "lat"), crs = 4326)

# GeoJSON
route <- sf::st_read("route.geojson")

JavaScript approach (for Observable/D3):

// GPX parsing
const gpxText = await FileAttachment("route.gpx").text();
const parser = new DOMParser();
const gpxDoc = parser.parseFromString(gpxText, "text/xml");

// Extract track points
const trkpts = gpxDoc.querySelectorAll("trkpt");
const coordinates = Array.from(trkpts).map(pt => ({
  lat: +pt.getAttribute("lat"),
  lon: +pt.getAttribute("lon"),
  ele: +pt.querySelector("ele")?.textContent || 0
}));

Verify the coordinate reference system (CRS) is WGS 84 (EPSG:4326) for web maps.

Got: Spatial data loaded as an sf object (R) or coordinate array (JS) with valid geometries. Point counts match expected input (e.g., a GPX track has hundreds to thousands of points).

Read the full file on GitHub · 270 lines

Changes

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.

  1. 4d ago First seen · 270 lines · 111 tokens per session scan A 0be8ddcff7f5

Subscribe to this mod's changes

create-spatial-visualization is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed today), licensed MIT. It adds 111 tokens to every session and 2,943 once invoked, about $0.0006 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-09-03.

Related

Other skills, from other repositories

analytics

Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…

yonatangross/orchestkit · 62 tokens

audit-pr

Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".

gtrabanco/agentic-workflow · 71 tokens

design-feature

Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".

gtrabanco/agentic-workflow · 51 tokens

plan-feature

Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".

gtrabanco/agentic-workflow · 66 tokens

product-audit

Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".

gtrabanco/agentic-workflow · 69 tokens

audit-docs

Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…

gtrabanco/agentic-workflow · 188 tokens