3po-3d.github.io/

obsidian_to_jekyll

community[skill]

Convert Obsidian markdown to Jekyll-compatible markdown. Strips wikilinks, converts callout blocks, resolves vault-relative image paths, and replaces Obsidian frontmatter with Jekyll frontmatter.

$/plugin install 3po-3d.github.io

details

Skill: obsidian_to_jekyll

Purpose

Transform Obsidian vault markdown into Jekyll-ready markdown that builds cleanly with kramdown + GFM.

Transformations

1. Wikilinks → Markdown links or plain text

[[page_name]]              → page_name (plain text, or link if target exists)
[[page_name|Display Text]] → Display Text
[[#heading]]               → [heading](#heading)

2. Callout blocks → HTML or blockquote

> [!info] Title
> Content here

→ becomes:

> **Title** — Content here

Or for styled callouts:

<div class="callout callout-info">
  <strong>Title</strong>
  <p>Content here</p>
</div>

3. Frontmatter replacement

Strip Obsidian frontmatter (title, tags, last_updated) and replace with Jekyll:

---
layout: chronos
title: "Page Title"
permalink: /chronos/page-slug/
nav_order: N
---

4. Image paths

![[image.png]]                    → ![image](/assets/img/image.png)
![alt](vault/path/image.png)     → ![alt](/assets/img/image.png)

5. Dataview/Templater blocks → Remove

```dataview
...
```
→ remove entirely (these only work in Obsidian)

```templater
...
```
→ remove entirely

6. Tags

#tag/name → remove (Obsidian-specific)

7. Kanban blocks → Remove or convert


## Procedure

1. Read the vault source file
2. Apply transformations 1-7 in order
3. Add Jekyll frontmatter
4. Verify the result is valid kramdown + GFM markdown
5. Write to the site target path

## Notes
- Preserve all heading hierarchy (h1-h6)
- Preserve all code blocks (``` ... ```)
- Preserve all tables
- Preserve all HTML that's already in the source
- Do NOT add Obsidian-specific styling
- The result must build cleanly with `bundle exec jekyll build`

technical

github: 3PO-3D/3po-3d.github.io
stars: 0
license: unspecified
contributors: 1
last commit: 2026-04-22T16:44:45Z
file: .claude/skills/obsidian_to_jekyll.md

obsidian-skills/obsidian-markdown— Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
medical_evaluation_system/obsidian— Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
obsidian-skills/obsidian-cli— Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
Obsidian-CLI-skill/obsidian-cli— Use this skill whenever the user wants Claude to directly interact with their Obsidian vault — reading a note or daily note, writing or appending content, searching vault contents, counting or listing notes, managing tasks, moving or renaming files, finding orphaned notes or broken links. Without this skill, Claude has no way to access vault data or execute vault operations. Treat any request that implies "go into my vault and do X" as a trigger — the user is asking Claude to act, not to explain. Also trigger for vault automation, CLI scripting, or cron-based workflows involving Obsidian, managing sync history, querying Bases, restoring file versions via history, managing bookmarks, or running JavaScript against the Obsidian API. Skip for pure conceptual questions: how Obsidian's GUI works, navigating settings menus, theme or plugin installation via the UI, iCloud/third-party sync conflicts, general Dataview query syntax, keyboard shortcuts, or parsing vault files with external scripts — anything where the user needs an explanation rather than Claude performing a vault operation.
obsidian-cli/obsidian-cli— Use this skill whenever the user wants Claude to directly interact with their Obsidian vault — reading a note or daily note, writing or appending content, searching vault contents, counting or listing notes, managing tasks, moving or renaming files, finding orphaned notes or broken links. Without this skill, Claude has no way to access vault data or execute vault operations. Treat any request that implies "go into my vault and do X" as a trigger — the user is asking Claude to act, not to explain. Also trigger for vault automation, CLI scripting, or cron-based workflows involving Obsidian. Skip for pure conceptual questions: how Obsidian's GUI works, navigating settings menus, theme or plugin installation via the UI, or general Dataview query syntax — anything where the user needs an explanation rather than Claude performing a vault operation.