obsidian-maps
Skill2 starsChanged 2 months agoMITView on GitHub
Embed interactive maps in Obsidian via the Map View plugin.
In this repository58 other files it gives its agents.
- ad-hoc-script-verificationSkill
- architecture-diagramSkill
- blocked-page-recoverySkill
- cadquery-enclosure-designSkill
- canonical-thumbnailSkill
- circuit-designSkill
- competitor-news-monitorSkill
- component-alternativesSkill
- debugging-hermes-tui-commandsSkill
- docker-container-update-checkSkill
- document-to-action-itemsSkill
- docxSkill
- email-inbox-triageSkill
- embedded-porting-patternsSkill
- ephemeral-file-sharingSkill
- excalidrawSkill
- flash-game-researchSkill
- flutter-android-buildSkill
- flutter-content-renderingSkill
- github-code-reviewSkill
- githubSkill
- goatcounter-analyticsSkill
- google-oauth-file-pollSkill
- grounded-citationsSkill
- hermes-agent-skill-authoringSkill
- hermes-gateway-slash-commandSkill
- hermes-gateway-supervisionSkill
- jellyseerr-watch-suggestionsSkill
- maintained-fork-publishingSkill
- meeting-action-itemsSkill
- native-mcpSkill
- pdf-flattenSkill
- pdfSkill
- pdf-surgical-editsSkill
- planSkill
- product-price-monitorSkill
- psp-developmentSkill
- psp-homebrew-testingSkill
- psp-prx-plugin-maintenanceSkill
- python-debugpySkill
- python-webapp-patternsSkill
- reddit-readingSkill
- retro-fansiteSkill
- reverse-proxy-websocket-debuggingSkill
- rss-feedsSkill
- simplify-codeSkill
- sketchSkill
- skit-thumbnailSkill
- spikeSkill
- subagent-driven-developmentSkill
- test-driven-developmentSkill
- usb-device-enumerationSkill
- weekly-review-planningSkill
- wiki-media-asset-pipelineSkill
- windows-c-build-toolchainSkill
- windows-crash-forensicsSkill
- writing-plansSkill
- yt-dlp-anti-botSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use Map View by esm7, NOT obsidian-maps (the official Bases plugin — requires Obsidian Bases feature, not standalone).
- Distinctive: line 68
Do NOT hand-write the JSON.
- Very specific: line 83
Create trip note with locations: tag in frontmatter
- Very specific: line 84
Add inline geo links: Place #trip-tag
- Distinctive: line 93
Don't hand-write code blocks: use Copy Block from Presets or the context menu embed command — the JSON structure is non-obvious and …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Obsidian Maps Integration
Plugin: Map View (esm7)
Use Map View by esm7, NOT obsidian-maps (the official Bases plugin — requires Obsidian Bases feature, not standalone).
- Community plugin:
obsidian-map-view - GitHub:
esm7/obsidian-map-view
Two Location Formats
1. Frontmatter (one location per note)
---
location: 50.0755, 14.4378
---Note shows as a single pin on the map.
2. Inline geo links (multiple locations per note)
Requires locations: tag (plural) in frontmatter:
---
tags:
- locations
---Then in the note body:
[Place Name](geo:50.0880,14.4044) #tag-nameEach [Name](geo:lat,lng) becomes a separate pin. Inline tags (#tag-name) enable custom icon rules.
Embedded Map Code Block
The code block uses JSON (not YAML). Format sourced from mapState.ts:
```mapview
{"name":"View Name","mapZoom":13,"centerLat":50.0755,"centerLng":14.4378,"query":"tag:#place-tag","chosenMapSource":0,"autoFit":true}
```JSON fields
| Field | Type | Description |
name | string | View name |
mapZoom | number | Zoom level (1-19) |
centerLat | number | Map center latitude |
centerLng | number | Map center longitude |
query | string | Filter query (e.g. tag:#prague-place) |
chosenMapSource | number | Map tile source index |
autoFit | boolean | Auto-zoom to fit all markers |
embeddedHeight | number | Optional: height in pixels |
lock | boolean | Optional: disable pan/zoom |
Generating code blocks
Do NOT hand-write the JSON. Instead:
- Open Map View sidebar → configure query/zoom/pan
- Presets pane → Copy Block
- Paste into note
Or: right-click in note editor → "embed a Map View" → enter search term.
Query Syntax
tag:#hiking— notes/markers with tagname:Prague— markers containing stringtag:#sleep*— wildcard tagslinkedfrom:"filename"— notes linking to filename- Boolean:
tag:#dogs AND tag:#food
Workflow: Trip Planning
- Create trip note with
locations:tag in frontmatter - Add inline geo links:
[Place](geo:lat,lng) #trip-tag - Embed map:
```mapview ```block with querytag:#trip-tag - Open Map View sidebar → focus note → see all pins
- Configure icon rules in Map View settings (Font Awesome icons)
Pitfalls
- obsidian-maps ≠ Map View:
obsidian-maps(obsidianmd) requires Bases feature. Useobsidian-map-view(esm7) for standalone embedding. - Code block is JSON, not YAML:
centerLat/centerLng(notcenter),mapZoom(notzoom),query(notfilter). YAML-like syntax causesSyntaxError: Unexpected token. - Inline links need
locations:tag: withoutlocations:(plural) in frontmatter, Map View skips scanning forgeo:links to save performance. - Don't hand-write code blocks: use Copy Block from Presets or the context menu embed command — the JSON structure is non-obvious and error-prone.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

