agentleFS
abduznikabduznik/abduznik-skills/skills/obsidian-maps/SKILL.md

obsidian-maps

Skill2 starsChanged 2 months agoMITView on GitHub

Embed interactive maps in Obsidian via the Map View plugin.

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
  1. Distinctive:

    Use Map View by esm7, NOT obsidian-maps (the official Bases plugin — requires Obsidian Bases feature, not standalone).

    line 17
  2. Distinctive:

    Do NOT hand-write the JSON.

    line 68
  3. Very specific:

    Create trip note with locations: tag in frontmatter

    line 83
  4. Very specific:

    Add inline geo links: Place #trip-tag

    line 84
  5. Distinctive:

    Don't hand-write code blocks: use Copy Block from Presets or the context menu embed command — the JSON structure is non-obvious and …

    line 93

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-name

Each [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

FieldTypeDescription
namestringView name
mapZoomnumberZoom level (1-19)
centerLatnumberMap center latitude
centerLngnumberMap center longitude
querystringFilter query (e.g. tag:#prague-place)
chosenMapSourcenumberMap tile source index
autoFitbooleanAuto-zoom to fit all markers
embeddedHeightnumberOptional: height in pixels
lockbooleanOptional: disable pan/zoom

Generating code blocks

Do NOT hand-write the JSON. Instead:

  1. Open Map View sidebar → configure query/zoom/pan
  2. Presets pane → Copy Block
  3. Paste into note

Or: right-click in note editor → "embed a Map View" → enter search term.

Query Syntax

  • tag:#hiking — notes/markers with tag
  • name:Prague — markers containing string
  • tag:#sleep* — wildcard tags
  • linkedfrom:"filename" — notes linking to filename
  • Boolean: tag:#dogs AND tag:#food

Workflow: Trip Planning

  1. Create trip note with locations: tag in frontmatter
  2. Add inline geo links: [Place](geo:lat,lng) #trip-tag
  3. Embed map: ```mapview ``` block with query tag:#trip-tag
  4. Open Map View sidebar → focus note → see all pins
  5. Configure icon rules in Map View settings (Font Awesome icons)

Pitfalls

  • obsidian-maps ≠ Map View: obsidian-maps (obsidianmd) requires Bases feature. Use obsidian-map-view (esm7) for standalone embedding.
  • Code block is JSON, not YAML: centerLat/centerLng (not center), mapZoom (not zoom), query (not filter). YAML-like syntax causes SyntaxError: Unexpected token.
  • Inline links need locations: tag: without locations: (plural) in frontmatter, Map View skips scanning for geo: 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.