Build Teaql App
teaql/teaql-agent-kit
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries.
Geohash encoding/decoding in TypeScript or Rust — bit interleaving, the base32 alphabet, precision and cell geometry, neighbour/adjacency computation, proximity and bounding-box queries, and…
Install Geohash Spatial Code Maps
$ npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills geohash-spatial-code-maps --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/geohash-spatial-code-maps .claude/skills/geohash-spatial-code-maps && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "geohash-spatial-code-maps" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/geohash-spatial-code-maps into .claude/skills/geohash-spatial-code-maps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geohash-spatial-code-maps", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/geohash-spatial-code-mapsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills geohash-spatial-code-maps --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/geohash-spatial-code-maps .agents/skills/geohash-spatial-code-maps && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "geohash-spatial-code-maps" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/geohash-spatial-code-maps into .agents/skills/geohash-spatial-code-maps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geohash-spatial-code-maps", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills geohash-spatial-code-maps --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/geohash-spatial-code-maps .cursor/skills/geohash-spatial-code-maps && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "geohash-spatial-code-maps" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/geohash-spatial-code-maps into .cursor/skills/geohash-spatial-code-maps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geohash-spatial-code-maps", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/geohash-spatial-code-maps--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills geohash-spatial-code-maps --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/geohash-spatial-code-maps .gemini/skills/geohash-spatial-code-maps && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "geohash-spatial-code-maps" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/geohash-spatial-code-maps into .gemini/skills/geohash-spatial-code-maps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geohash-spatial-code-maps", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills geohash-spatial-code-mapsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/geohash-spatial-code-maps .github/skills/geohash-spatial-code-maps && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "geohash-spatial-code-maps" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/geohash-spatial-code-maps into .github/skills/geohash-spatial-code-maps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geohash-spatial-code-maps", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills geohash-spatial-code-maps --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/geohash-spatial-code-maps .opencode/skills/geohash-spatial-code-maps && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "geohash-spatial-code-maps" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/geohash-spatial-code-maps into .opencode/skills/geohash-spatial-code-maps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geohash-spatial-code-maps", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
geohash-spatial-code-maps- GitHub stars
- 214
- Token cost
- ~2.5k tokens
- SKILL.md length
- 789 words
- Files
- 47 (incl. references, assets)
- Skills in repo
- 182
- Repo updated
- First seen
- Licence
- MIT
At a glance
Geohash encoding/decoding in TypeScript or Rust — bit interleaving, the base32 alphabet, precision and cell geometry, neighbour/adjacency computation, proximity and bounding-box queries, and…
- Works in 8 steps: Encoding & Bit Interleaving (CRITICAL) → Precision & Cell Geometry (CRITICAL) → Neighbours & Adjacency (HIGH) → …
- Debugging geohash work — even when the user does not say geohash but the work involves spatial hashing
- SKILL.md covers When to Apply, A note on scope, Rule Categories by Priority and Quick Reference, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Geohash Spatial Code Maps is an agent skill from pproenca/dot-skills. Geohash encoding/decoding in TypeScript or Rust — bit interleaving, the base32 alphabet, precision and cell geometry, neighbour/adjacency computation, proximity and bounding-box queries, and geohash-backed spatial indexing. Also covers the "codebase as a navigable 2D map" pattern — projecting a codebase into a coordinate plane, geohashing it so prefixes become business-domain regions, and navigating it like Google Maps (zoom, tiles, level-of-detail, clustering, deep links). Trigger when implementing, reviewing…
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 49 other files, including reference files and assets (for example `AGENTS.md`, `assets/templates/_template.md` and `metadata.json`).
It sits in Mobile. It works with Rust, TypeScript and Google Maps Platform. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- Debugging geohash work — even when the user does not say geohash but the work involves spatial hashing
- Morton/Z-order codes
- Proximity search on lat/lon
- Mapping and visualising code structure spatially
Example prompts
- “codebase as a navigable 2D map”
- “geohash”
- “/geohash-spatial-code-maps”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Geohash Spatial Code Maps loads about 2.5k tokens when it runs, and up to ~24k if it reads all its reference files. Until then it costs about 206 tokens; SKILL.md has 789 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 789 words, ~2,494 tokens.
Download SKILL.mdSave it as
.claude/skills/geohash-spatial-code-maps/SKILL.md (or your agent's skills folder). This skill also uses 46 other files; get the full folder from GitHub.- name
- geohash-spatial-code-maps
- description
- Geohash encoding/decoding in TypeScript or Rust — bit interleaving, the base32 alphabet, precision and cell geometry, neighbour/adjacency computation, proximity and bounding-box queries, and geohash-backed spatial indexing. Also covers the "codebase as a navigable 2D map" pattern — projecting a codebase into a coordinate plane, geohashing it so prefixes become business-domain regions, and navigating it like Google Maps (zoom, tiles, level-of-detail, clustering, deep links). Trigger when implementing, reviewing, or debugging geohash work — even when the user does not say "geohash" but the work involves spatial hashing, Morton/Z-order codes, proximity search on lat/lon, or mapping and visualising code structure spatially. Contains 42 impact-ordered rules with TypeScript and Rust examples.
Geohash & Spatial Code Maps Best Practices
How to implement geohashes correctly in TypeScript and Rust, how to query and index them at scale, and how to apply them to the "codebase as a navigable 2D map" pattern — projecting code into a plane so geohash prefixes become domain regions you can fly through like Google Maps. Contains 42 rules across 8 categories, prioritised by impact.
When to Apply
Reference these guidelines when:
- Implementing or reviewing a geohash encoder/decoder in TypeScript or Rust (bit interleaving, base32, precision, neighbours)
- Building proximity / radius / bounding-box search on lat/lon data, or storing geohashes as index keys (SQL B-tree, Redis sorted sets)
- Debugging the classic geohash bugs — swapped axes, wrong alphabet, border false negatives, off-by-one cells at high precision
- Projecting a codebase (or any abstract graph) into a 2D plane and geohashing it so prefixes name business domains or features
- Navigating a geohashed dataset like a slippy map: zoom-to-precision, viewport tile loading, level-of-detail aggregation, prefix clustering, deep links
A note on scope
Categories 1–4, 6, and 7 are textbook geohashing, drawn from authoritative sources (the geohash spec, the davetroy/geohash-js neighbour tables, Redis, Elasticsearch). Categories 5 (map-) and 8 (nav-) are a novel synthesis — there is no canonical "geohash your codebase" library, so those rules derive design principles from established techniques (deterministic graph layout, Morton/Z-order keys, slippy-map tiling, software cartography). They are honest about when the pattern is overkill.
Rule Categories by Priority
| Priority | Category | Impact | Prefix | Rules |
|---|---|---|---|---|
| 1 | Encoding & Bit Interleaving | CRITICAL | enc- | 6 |
| 2 | Precision & Cell Geometry | CRITICAL | prec- | 5 |
| 3 | Neighbours & Adjacency | HIGH | nbr- | 5 |
| 4 | Proximity & Range Queries | HIGH | qry- | 5 |
| 5 | Codebase-as-Map Spatial Layout | HIGH | map- | 7 |
| 6 | Decoding & Bounding Boxes | MEDIUM-HIGH | dec- | 4 |
| 7 | Spatial Indexing & Storage | MEDIUM-HIGH | idx- | 5 |
| 8 | Navigation & Rendering | MEDIUM | nav- | 5 |
Quick Reference
1. Encoding & Bit Interleaving (CRITICAL)
enc-interleave-longitude-first— Interleave longitude on even bits, latitude on oddenc-base32-alphabet— Use the geohash base32 alphabet, not RFC 4648enc-integer-morton-encode— Encode to an interleaved 64-bit integer for speed and sortable keysenc-binary-chop-no-float-drift— Recompute interval midpoints; never accumulate a float stepenc-normalize-input-domain— Clamp latitude, wrap longitude, reject non-finite inputenc-five-bit-char-boundary— Accumulate exactly five bits per character
2. Precision & Cell Geometry (CRITICAL)
prec-choose-from-error-radius— Choose geohash length from the required error radiusprec-cells-are-not-square— Treat cells as rectangles whose aspect flips with lengthprec-error-is-half-cell— Report decoded accuracy as half the cell, not the full cellprec-cells-shrink-toward-poles— Scale longitude metres by cos(latitude)prec-avoid-mixed-precision— Normalise to one precision before comparing or storing
3. Neighbours & Adjacency (HIGH)
nbr-canonical-lookup-tables— Compute neighbours with the canonical border/neighbour tablesnbr-antimeridian-wrap— Wrap east/west neighbours across the antimeridiannbr-pole-handling— Return no neighbour past the polesnbr-integer-level-neighbors— Compute neighbours on the de-interleaved integernbr-eight-neighbor-set— Build the full eight-neighbour set for proximity
Show full SKILL.md (342 more words)Show less
4. Proximity & Range Queries (HIGH)
qry-search-cell-plus-neighbors— Query the cell plus its eight neighbours, never the prefix aloneqry-precision-from-radius— Match query precision to the search radiusqry-bbox-range-decomposition— Decompose a bounding box into covering geohash rangesqry-refine-with-haversine— Refine geohash candidates with true distanceqry-expand-precision-when-sparse— Widen the search by dropping a prefix character on sparse cells
5. Codebase-as-Map Spatial Layout (HIGH)
map-deterministic-projection— Project code into 2D from a structural signal, not arbitrary layoutmap-stable-coordinates— Make coordinates reproducible and incremental-stablemap-normalize-to-geohash-domain— Normalise the code plane into the geohash lat/lon domainmap-coupling-implies-proximity— Validate that coupled code lands in the same regionmap-prefix-as-domain-region— Treat a geohash prefix as a named domain regionmap-precision-as-architectural-level— Map prefix length to architectural levelmap-persist-coordinate-sidecar— Persist the file-to-geohash assignment as a committed sidecar
6. Decoding & Bounding Boxes (MEDIUM-HIGH)
dec-decode-to-bbox— Decode to a bounding box, then derive the centredec-symmetric-interval-reconstruction— Decode by mirroring the encoder's interval halvingdec-avoid-roundtrip-reencode— Keep the original hash; don't decode-then-re-encodedec-precompute-reverse-alphabet— Decode with a precomputed reverse-alphabet table
7. Spatial Indexing & Storage (MEDIUM-HIGH)
idx-sorted-string-range-scan— Store geohashes as sorted strings for prefix range scansidx-integer-sortable-key— Use the interleaved integer as a compact sortable keyidx-db-prefix-index— Make prefix queries sargable in Postgres and Redisidx-range-query-from-covering-set— Execute a box query as range scans over the covering setidx-trie-hierarchical-bucketing— Aggregate by region with a geohash trie
8. Navigation & Rendering (MEDIUM)
nav-precision-to-zoom-levels— Map geohash precision to zoom levelsnav-level-of-detail-aggregation— Render aggregated prefix buckets when zoomed outnav-tile-lazy-loading— Load only the geohash cells in the viewportnav-cluster-by-prefix— Cluster overlapping markers by shared prefixnav-breadcrumb-prefix-path— Use the geohash prefix as navigation state and deep link
How to Use
Read individual reference files for detailed explanations, code examples, and "when NOT to apply" guidance:
- Section definitions — Category structure and impact levels
- Rule template — Template for adding new rules
Rules cross-link via [[other-rule-slug]]; follow them when a related pattern is referenced. To build a code map end to end, the spine is: map-deterministic-projection → map-normalize-to-geohash-domain → encode (category 1) → map-prefix-as-domain-region → navigate (category 8).
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 46 other files (references, assets) in skills/.experimental/geohash-spatial-code-maps of pproenca/dot-skills.
- SKILL.md
- AGENTS.md
- assets/templates/_template.md
- metadata.json
- references/_sections.md
- references/dec-avoid-roundtrip-reencode.md
- references/dec-decode-to-bbox.md
- references/dec-precompute-reverse-alphabet.md
- references/dec-symmetric-interval-reconstruction.md
- references/enc-base32-alphabet.md
- references/enc-binary-chop-no-float-drift.md
- references/enc-five-bit-char-boundary.md
- references/enc-integer-morton-encode.md
- references/enc-interleave-longitude-first.md
- references/enc-normalize-input-domain.md
- references/idx-db-prefix-index.md
- references/idx-integer-sortable-key.md
- references/idx-range-query-from-covering-set.md
- … and 29 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
Geohash Spatial Code Maps next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Geohash Spatial Code Maps this skillpproenca/dot-skills | 214 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Build Teaql Appteaql/teaql-agent-kit | 2.8k | — | ~4.6k | Automated safety check: Pass | MIT | |
| jscpd Code Migration Trackerkucherenko/jscpd | 6.3k | — | ~5k | Automated safety check: Pass | MIT | |
| Dbgtheodo-group/debug-that | 158 | — | ~1.9k | Automated safety check: Pass | MIT | |
| MCP SDK Tier Auditmodelcontextprotocol/conformance | 129 | — | ~4.4k | Automated safety check: Pass | Custom licence | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence |
Similar skills
jscpd Code Migration Tracker
kucherenko/jscpd
Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.
Dbg
theodo-group/debug-that
Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.
- Official
MCP SDK Tier Audit
modelcontextprotocol/conformance
Comprehensive tier assessment for an MCP SDK repository against SEP-1730.
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
Testing Changes
pnpm/pnpm
Run the tests that cover a change in the pnpm repository, in the Rust workspace (pnpm/, pnpr/) or the TypeScript CLI (pnpm11/), and recognize the cases where a scoped run passes without testing…
More from pproenca/dot-skills
All 182 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Works with
Categories
Questions about Geohash Spatial Code Maps
What does Geohash Spatial Code Maps do?
Geohash encoding/decoding in TypeScript or Rust — bit interleaving, the base32 alphabet, precision and cell geometry, neighbour/adjacency computation, proximity and bounding-box queries, and…. Geohash Spatial Code Maps is an agent skill from pproenca/dot-skills. Geohash encoding/decoding in TypeScript or Rust — bit interleaving, the base32 alphabet, precision and cell geometry, neighbour/adjacency computation, proximity and bounding-box queries, and geohash-backed spatial indexing.
When should I use Geohash Spatial Code Maps?
Geohash Spatial Code Maps fits situations like: debugging geohash work — even when the user does not say geohash but the work involves spatial hashing; morton/Z-order codes; proximity search on lat/lon; mapping and visualising code structure spatially.
How do I install Geohash Spatial Code Maps in Claude Code?
Run `npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a claude-code`. Or copy the skill folder (skills/.experimental/geohash-spatial-code-maps in pproenca/dot-skills) into .claude/skills/geohash-spatial-code-maps in your project. Claude Code loads it when a task matches its description.
How do I install Geohash Spatial Code Maps in Codex?
Run `npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a codex`. Or copy the skill folder (skills/.experimental/geohash-spatial-code-maps in pproenca/dot-skills) into .agents/skills/geohash-spatial-code-maps in your project. Codex loads it when a task matches its description.
Can I use Geohash Spatial Code Maps in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill geohash-spatial-code-maps -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/geohash-spatial-code-maps, .gemini/skills/geohash-spatial-code-maps, .github/skills/geohash-spatial-code-maps and .opencode/skills/geohash-spatial-code-maps in your project.
What does Geohash Spatial Code Maps need to run?
SKILL.md names no scripts, command-line tools or credentials: Geohash Spatial Code Maps is instructions for the agent only.
Does Geohash Spatial Code Maps access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Geohash Spatial Code Maps safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Geohash Spatial Code Maps use?
Geohash Spatial Code Maps is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Geohash Spatial Code Maps use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 22k tokens, read only when the agent opens those files.
What are the alternatives to Geohash Spatial Code Maps?
Skills that share tags, products or a category with Geohash Spatial Code Maps: Build Teaql App (teaql/teaql-agent-kit, 2.8k stars), jscpd Code Migration Tracker (kucherenko/jscpd, 6.3k stars), Dbg (theodo-group/debug-that, 158 stars) and MCP SDK Tier Audit (modelcontextprotocol/conformance, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Geohash Spatial Code Maps?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.