A "Meta Tool" Is Born
Imagine you're taking notes in Obsidian — bidirectional links, graph view, Canvas, Bases (database views). Now you want an AI agent to help manage your vault. The problem: when Claude Code opens your vault, it has no idea what a .canvas file looks like, and it can't distinguish a [[wikilink]] from a plain Markdown link.
kepano/obsidian-skills fills this gap. Its author is none other than Obsidian's CEO, Steph Ango (aka kepano). This isn't a third-party plugin from an enthusiast — it's Obsidian officially writing an "operations manual" for AI agents.
What Does It Provide?
Five skills, each covering one Obsidian-specific data format or tool:
| Skill | Purpose |
|-------|---------|
| obsidian-markdown | Handle Obsidian-flavored Markdown — wikilinks, embeds, callouts, properties |
| obsidian-bases | Work with .base files — Obsidian's database views, with filters, formulas, summaries |
| json-canvas | Work with .canvas files — visual canvases in the JSON Canvas format |
| obsidian-cli | Use the Obsidian CLI — plugin and theme development |
| defuddle | Extract clean Markdown from web pages — removes clutter, saves tokens |
If these formats seem obscure, think of it this way: plain Markdown is the "Mandarin" AI already speaks, while Obsidian's wikilinks, Canvas, and Bases are "dialects." Without learning the dialect, an AI treats [[Note A]] as plain text rather than a link, and a .canvas file as meaningless JSON.
The Agent Skills Specification: A Notable Trend
The most noteworthy thing about this project isn't any individual skill — it's that it follows the Agent Skills specification. The README states:
> These skills follow the Agent Skills specification so they can be used by any skills-compatible agent, including Claude Code, Codex, and Open Code.
In other words: these skills aren't tied to Claude Code. Codex, OpenCode — any spec-compliant agent can use the same skill files. Installation paths differ (Claude Code uses .claude/, Codex uses ~/.codex/skills/, OpenCode uses ~/.opencode/skills/), but the skill content itself is universal.
An analogy: skill files are to AI agents what drivers are to operating systems. Every OS once wrote its own drivers; later came universal driver frameworks. The Agent Skills spec is doing something similar — making "AI capability packages" portable across agents.
Why Is the Obsidian CEO Writing This Personally?
That signal matters more than the project itself.
Obsidian's business model has always been selling Sync and Publish services while keeping the client free and local. Now the CEO is personally writing Agent Skills, which suggests Obsidian treats "AI operability" as infrastructure-level investment.
The reason is easy to guess: if AI agents can't correctly read and write Obsidian's file formats, users will migrate to more AI-friendly tools. Rather than waiting for third parties, the vendor defines the standard itself. It's the same logic as database vendors writing their own ORM drivers — whoever controls the interface controls the ecosystem.
Defuddle: An Underrated Skill
Of the five skills, defuddle is easiest to overlook but possibly the most valuable. What it does sounds simple: extract clean Markdown from web pages, stripping navigation, ads, and scripts.
The keyword is "saving tokens."
When an agent needs to read a web page, feeding raw HTML can burn 20K+ tokens on navbars and scripts alone. Defuddle extracts the meaningful content down to maybe 2K tokens. For agents billed per token with limited context windows, this isn't a nice-to-have — it's real cost savings.
It's similar to a web-reader skill, but Defuddle is native to the Obsidian ecosystem and integrates seamlessly with Markdown notes.
Relationship to Anthropic Skills
Also trending the same day: anthropics/skills, Anthropic's official skills repository. Both trending at once is no coincidence — the Agent Skills ecosystem is forming fast.
The difference:
- anthropics/skills is Anthropic's official general-purpose skill collection
- kepano/obsidian-skills is a vendor-maintained (Obsidian) skill set for a specific application
- Repository: kepano/obsidian-skills
- +411 stars today
- Author: Steph Ango (Obsidian CEO)
- Specification: agentskills.io/specification
- License: not stated (not specified in README)
Their relationship resembles "standard libraries shipped with an OS" versus "SDKs provided by application vendors." You need the former for an agent to function; you need the latter for an agent to operate specific tools.
Lessons for Developers
If you're building a tool product, obsidian-skills offers a clear template:
1. If your data format isn't a standard format, it needs a skill — otherwise AI treats it as unrecognized text 2. Follow the Agent Skills specification — don't lock into a single agent; give users choice 3. An official effort beats third-party work — users trust the vendor's understanding of its own formats
Data
*The emergence of the Agent Skills specification means the AI agent ecosystem is moving from "every agent for itself" toward portable capabilities. Obsidian's CEO personally writing skills is an early signal of application vendors proactively adapting to the agent ecosystem.*