Convert Obsidian vault content, wikilinks, and attachments into portable Markdown trees before publishing, indexing, or migrating notes.
Scanned 6/8/2026
Install via CLI
openskills install agentskillexchange/skills---
name: "Export Obsidian vaults into clean Markdown trees for publishing or downstream processing"
slug: "export-obsidian-vaults-into-clean-markdown-trees-for-publishing-or-downstream-processing"
description: "Convert Obsidian vault content, wikilinks, and attachments into portable Markdown trees before publishing, indexing, or migrating notes."
github_stars: 1300
verification: "security_reviewed"
source: "https://github.com/zoni/obsidian-export"
author: "zoni"
publisher_type: "user"
category: "Data Extraction & Transformation"
framework: "Multi-Framework"
tool_ecosystem:
github_repo: "zoni/obsidian-export"
github_stars: 1300
---
# Export Obsidian vaults into clean Markdown trees for publishing or downstream processing
Convert Obsidian vault content, wikilinks, and attachments into portable Markdown trees before publishing, indexing, or migrating notes.
## Prerequisites
obsidian-export CLI and access to the source vault directory
## Installation
Requirements and caveats from upstream:
- As a text interface, this must be run from a terminal or Windows PowerShell.
- Note that the destination directory must exist, so you may need to create a new, empty directory first.
- Some static site generators are picky about frontmatter and require it to be present.
Basic usage or getting-started notes:
- docs directory and run generate.sh.
- ## Pre-built binaries
- Pre-compiled binaries for all major platforms are available at <https://github.com/zoni/obsidian-export/releases>
- Source: https://github.com/zoni/obsidian-export
- Extracted from upstream docs: https://raw.githubusercontent.com/zoni/obsidian-export/HEAD/README.md
## Documentation
- https://github.com/zoni/obsidian-export
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/export-obsidian-vaults-into-clean-markdown-trees-for-publishing-or-downstream-processing/)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.