Data Table Manager
n8n-io/n8n
Load before calling data-tables or parse-file. An agent skill from n8n-io/n8n.
One Go binary for every Dutch location workflow — geocode, reverse-geocode, batch CSVs, full GeoJSON geometries,...
$ npx skills add mvanhorn/printing-press-library --skill pp-pdok-location -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-pdok-location --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/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-pdok-location .claude/skills/pp-pdok-location && 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 "pp-pdok-location" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-pdok-location into .claude/skills/pp-pdok-location/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-pdok-location", 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/mvanhorn/printing-press-library/tree/main/cli-skills/pp-pdok-locationType 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 mvanhorn/printing-press-library --skill pp-pdok-location -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-pdok-location --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-pdok-location .agents/skills/pp-pdok-location && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-pdok-location" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-pdok-location into .agents/skills/pp-pdok-location/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-pdok-location", 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 mvanhorn/printing-press-library --skill pp-pdok-location -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-pdok-location --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-pdok-location .cursor/skills/pp-pdok-location && 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 "pp-pdok-location" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-pdok-location into .cursor/skills/pp-pdok-location/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-pdok-location", 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/mvanhorn/printing-press-library.git --path cli-skills/pp-pdok-location--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 mvanhorn/printing-press-library --skill pp-pdok-location -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-pdok-location --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-pdok-location .gemini/skills/pp-pdok-location && 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 "pp-pdok-location" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-pdok-location into .gemini/skills/pp-pdok-location/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-pdok-location", 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 mvanhorn/printing-press-library pp-pdok-locationInstalls 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 mvanhorn/printing-press-library --skill pp-pdok-location -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-pdok-location .github/skills/pp-pdok-location && 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 "pp-pdok-location" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-pdok-location into .github/skills/pp-pdok-location/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-pdok-location", 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 mvanhorn/printing-press-library --skill pp-pdok-location -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-pdok-location --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-pdok-location .opencode/skills/pp-pdok-location && 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 "pp-pdok-location" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-pdok-location into .opencode/skills/pp-pdok-location/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-pdok-location", 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.
pp-pdok-locationOne Go binary for every Dutch location workflow — geocode, reverse-geocode, batch CSVs, full GeoJSON geometries,...
Pp Pdok Location is an agent skill from mvanhorn/printing-press-library. One Go binary for every Dutch location workflow — geocode, reverse-geocode, batch CSVs, full GeoJSON geometries,... Trigger phrases: geocode a Dutch address, find the gemeente for this lat/lon, convert RD coordinates to WGS84, look up a Dutch postcode, batch geocode a CSV of Dutch addresses, find the nearest address to this point in the Netherlands, use pdok-location, run pdok-location.
Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering CSV and tabular files. The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d9a1696. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
claudenpxgoFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Pdok Location loads about 4.6k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 1,963 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated 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.
The full file from mvanhorn/printing-press-library at commit d9a1696, republished under its Apache-2.0 licence (© mvanhorn). 1,963 words, ~4,577 tokens.
.claude/skills/pp-pdok-location/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/developer-tools/pdok-location/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the pdok-location-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install pdok-location --cli-onlypdok-location-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):
go install github.com/mvanhorn/printing-press-library/library/developer-tools/pdok-location/cmd/pdok-location-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
PDOK Location is the right CLI when an agent needs to work with Dutch addresses, parcels, roads, or administrative boundaries — including batch geocoding CSVs, looking up the gemeente containing a point, converting between RD and WGS84 coordinates, or pulling full GeoJSON features inside a bounding box. It is Netherlands-only (do not use for non-Dutch addresses) and free (no auth, no key).
This binary wraps two upstreams — Locatieserver (/bzk/locatieserver/search/v3_1) and Kadaster Location API (/kadaster/location-api/v1) — because they are complementary, not redundant.
A common Dutch geo workflow uses both: geocode text on Locatieserver, then pull full geometry on the Location API. Each is incomplete without the other (Locatieserver lacks bbox and full geometries; Location API lacks Solr ranking and reverse geocoding), so bundling them under one binary, one config, and one local cache turns that workflow into a single tool. Run pdok-location-pp-cli doctor --json to see which of the two upstreams is reachable right now — the sources.locatieserver and sources.kadaster_location_api keys each report status + which commands are affected if the source is down.
These capabilities aren't available in any other tool for this API.
batch geocode — Geocode an entire CSV of Dutch addresses in one command — outputs lat/lon, RD X/Y, match score, and an error column for failed rows.
When an agent needs to enrich a list of Dutch addresses, this is the one-shot command — no per-row scripting, with cached re-runs and a clear error column.
pdok-location-pp-cli batch geocode incidents.csv --address-col street --out incidents-geocoded.csvfeatures search — Search across multiple Location API OGC collections (adres, perceel, gebouw, ...) with an optional bounding-box filter, flattened to JSON or CSV.
When an agent needs a flat CSV of address+parcel matches inside a study area, this is the lightest path from a query to a multi-collection result set.
pdok-location-pp-cli features search --query damrak --collections adres,perceel --bbox 4.85,52.36,4.92,52.40 --csvresolve — Type a partial address, get the canonical match with full GeoJSON geometry — the suggest→lookup chain collapsed into a single command.
When an agent needs to turn imprecise user text into a canonical address with geometry, this is the cheapest path.
pdok-location-pp-cli resolve 'Damrak Amsterdam' --geojsonnearest — From any lat/lon or RD coordinate, return the nearest address, nearest parcel, nearest hectometer marker, and the gemeente/provincie containing the point — all in one call.
Reverse-geocoding usually needs four separate API calls; this one returns the full picture in one shot, ideal for field-data enrichment pipelines.
pdok-location-pp-cli nearest --lat 52.3731 --lon 4.8922 --jsontop — Return the single best match for a query if (and only if) the Solr score clears a threshold — exits non-zero when no match clears the bar.
When an agent needs a yes/no on whether an address is well-known, this is the predicate.
pdok-location-pp-cli top 'Hertog Aalbrechtweg 5 1823DL Alkmaar' --min-score 5.0 --require-type adres --jsonconvert rd-to-ll — Convert Dutch RD (EPSG:28992) coordinates to WGS84 lat/lon and back, with pure-math precision — no API call needed.
When an agent must reconcile Dutch RD coords with global WGS84, this is the local, deterministic path — no rate limit, no auth.
pdok-location-pp-cli convert rd-to-ll 121200 488000 --jsonconvert wkt-to-geojson — Take any WKT geometry (POINT, POLYGON, MULTIPOLYGON, MULTILINESTRING) and emit GeoJSON — or convert GeoJSON back to WKT.
When an agent needs to feed a PDOK response into mapping or analysis tooling expecting GeoJSON, this saves a parser.
pdok-location-pp-cli convert wkt-to-geojson 'POINT(4.76 52.64)'gemeente get — After a one-time sync, look up any of the 342 Dutch gemeenten or 12 provincies fully offline — name, centroid, codes, parent provincie.
For any agent workflow that asks 'which gemeente?' or 'list all gemeenten in this provincie', the answer is local and instant.
pdok-location-pp-cli gemeente get amsterdam --jsonsearch — Full-text search across every address, gemeente, and lookup you've previously fetched — finds matches locally before falling back to the API.
When an agent repeats lookups on the same dataset, this short-circuits the API entirely once the cache is warm.
pdok-location-pp-cli search 'amsterdam centraal' --jsongemeente of-point — Given any lat/lon or RD coordinate, return which gemeente and provincie contain it — using the offline gazetteer with an API fallback.
For 'which municipality is this incident in' questions an agent asks repeatedly, this is the cached, offline-first answer.
pdok-location-pp-cli gemeente of-point --lat 52.3731 --lon 4.8922 --jsonperceel lookup — Look up a Dutch cadastral parcel by its full kadastrale aanduiding (e.g. 'AMR03 N 1234') and get back the GeoJSON parcel feature.
For cadastral investigations, this is the only command-line path from aanduiding text to a GeoJSON parcel.
pdok-location-pp-cli perceel lookup --aanduiding 'ASD02 A 4332' --jsoncollections — Manage collections
pdok-location-pp-cli collections get — A list of all collections (geospatial data resources) in this dataset.pdok-location-pp-cli collections get-adres — adres collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-functioneel-gebied — functioneel_gebied collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-gebouw — gebouw collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-gemeentegebied — gemeentegebied collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-geografisch-gebied — geografisch_gebied collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-inrichtingselement — inrichtingselement collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-perceel — perceel collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-plaats — plaats collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-provinciegebied — provinciegebied collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-spoorbaandeel — spoorbaandeel collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-waterdeel — waterdeel collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-wegdeel — wegdeel collection (geospatial data resource) in this dataset.pdok-location-pp-cli collections get-woonplaats — woonplaats collection (geospatial data resource) in this dataset.conformance — Manage conformance
pdok-location-pp-cli conformance — A list of all conformance classes specified in a standard that the server conforms to.free — Manage free
pdok-location-pp-cli free — De Free API biedt de mogelijkheid om vrij te zoeken (klassiek geocoderen), waar zonder tussenkomst van suggesties de...lookup — Manage lookup
pdok-location-pp-cli lookup — Zodra er op basis van suggesties van de Suggest API een keuze is gemaakt, wordt de Lookup API aangeroepen, welke...pdok-location-api — Manage pdok location api
pdok-location-pp-cli pdok-location-api — This documentpdok-location-search — Manage pdok location search
pdok-location-pp-cli pdok-location-search — This endpoint allows one to implement autocomplete functionality for location search. The q parameter accepts a...reverse — Manage reverse
pdok-location-pp-cli reverse — De Reverse API biedt de mogelijkheid om een locatie (punt geometrie) op te geven om vervolgens verschillende...suggest — Manage suggest
pdok-location-pp-cli suggest — De Suggest API biedt de mogelijkheid om een (gedeelte van een) zoekopdracht op te voeren, waarnaar er suggesties...When you know what you want to do but not which command does it, ask the CLI directly:
pdok-location-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
pdok-location-pp-cli batch geocode customers.csv --address-col street --out customers-geocoded.csvGeocode every row, write a new CSV with lat/lon, RD x/y, score, and an error column. Re-runs are free because successful matches are cached.
pdok-location-pp-cli resolve 'Damrak Amsterdam' --geojsonOne command that does the suggest→lookup chain and returns GeoJSON ready to drop into a map.
pdok-location-pp-cli nearest --lat 52.3731 --lon 4.8922 --agent --select adres.weergavenaam,adres.id,perceel.weergavenaam,gemeente.gemeentenaam,gemeente.provincienaamPair --agent with --select dotted paths so the agent gets only the address line, parcel description, and admin context — not the full per-source response.
pdok-location-pp-cli features search --query amsterdam --collections perceel --bbox 4.85,52.36,4.92,52.40 --csvPulls every parcel matching 'amsterdam' inside the bbox from the Location API and emits a flat CSV; swap --collections to adres, gebouw, or any other OGC collection.
pdok-location-pp-cli convert rd-to-ll 121200 488000 --jsonPure-math transform, runs offline, deterministic — useful for normalizing legacy datasets stored in RD.
No authentication required.
Run pdok-location-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
pdok-location-pp-cli collections get --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.
When you (or the agent) notice something off about this CLI, record it:
pdok-location-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
pdok-location-pp-cli feedback --stdin < notes.txt
pdok-location-pp-cli feedback list --json --limit 10Entries are stored locally at ~/.pdok-location-pp-cli/feedback.jsonl. They are never POSTed unless PDOK_LOCATION_FEEDBACK_ENDPOINT is set AND either --send is passed or PDOK_LOCATION_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
pdok-location-pp-cli profile save briefing --json
pdok-location-pp-cli --profile briefing collections get
pdok-location-pp-cli profile list --json
pdok-location-pp-cli profile show briefing
pdok-location-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show pdok-location-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:
claude mcp add pdok-location-pp-mcp -- pdok-location-pp-mcpVerify: claude mcp list
which pdok-location-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:pdok-location-pp-cli <command> [subcommand] [args] --agentpdok-location-pp-cli <command> --help.© mvanhorn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cli-skills/pp-pdok-location of mvanhorn/printing-press-library.
Open the folder on GitHubat commit d9a1696
Pp Pdok Location 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 |
|---|---|---|---|---|---|---|
| Pp Pdok Location this skillmvanhorn/printing-press-library | 2.1k | — | ~4.6k | Automated safety check: Notes | Apache-2.0 | |
| Data Table Managern8n-io/n8n | 207k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Instrument Data To Allotropeaws-samples/amazon-bedrock-agents-healthcare-lifesciences | 274 | 2 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Abuse Hunternexu-io/harness-engineering-guide | 664 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Intelligence Requirements BuilderTracecatHQ/tracecat | 3.8k | — | ~6k | Automated safety check: Pass | MIT | |
| Markitshift-labs-ai/markit | 1.3k | — | ~299 | Automated safety check: Pass | MIT |
n8n-io/n8n
Load before calling data-tables or parse-file. An agent skill from n8n-io/n8n.
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
nexu-io/harness-engineering-guide
Detect and investigate bulk registration abuse on SaaS platforms.
TracecatHQ/tracecat
Turns a vague, high-level stakeholder ask into a structured set of intelligence requirements for a CTI team, complete with Essential Elements of Information, collection guidance, success criteria…
shift-labs-ai/markit
Convert files and URLs to Markdown. An agent skill from shift-labs-ai/markit.
tradermonty/claude-trading-skills
This skill should be used when analyzing sector rotation patterns and market cycle positioning.
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Categories
One Go binary for every Dutch location workflow — geocode, reverse-geocode, batch CSVs, full GeoJSON geometries,... Pp Pdok Location is an agent skill from mvanhorn/printing-press-library. One Go binary for every Dutch location workflow — geocode, reverse-geocode, batch CSVs, full GeoJSON geometries,...
Pp Pdok Location fits situations like: phrases: geocode a Dutch address; find the gemeente for this lat/lon; convert RD coordinates to WGS84; look up a Dutch postcode.
Run `npx skills add mvanhorn/printing-press-library --skill pp-pdok-location -a claude-code`. Or copy the skill folder (cli-skills/pp-pdok-location in mvanhorn/printing-press-library) into .claude/skills/pp-pdok-location in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-pdok-location -a codex`. Or copy the skill folder (cli-skills/pp-pdok-location in mvanhorn/printing-press-library) into .agents/skills/pp-pdok-location in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvanhorn/printing-press-library --skill pp-pdok-location -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-pdok-location, .gemini/skills/pp-pdok-location, .github/skills/pp-pdok-location and .opencode/skills/pp-pdok-location in your project.
Going by SKILL.md and its folder, Pp Pdok Location needs the command-line tools its instructions call (claude, npx and go). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Pdok Location is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Pdok Location: Data Table Manager (n8n-io/n8n, 207k stars), Instrument Data To Allotrope (aws-samples/amazon-bedrock-agents-healthcare-lifesciences, 274 stars), Abuse Hunter (nexu-io/harness-engineering-guide, 664 stars) and Intelligence Requirements Builder (TracecatHQ/tracecat, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.