From It's a Small World to the Haunted Mansion: A Blog Post Written in Claude Chat via BlackOps MCP

This is the post about the post.

Today is my wife's birthday. I took the day off. We were at Magic Kingdom.

Obsidian shipped official Claude Code skills. I saw the news, researched it, wrote a 9-tweet thread breaking down what it actually means for people already running custom skill ecosystems, and hit send.

From "It's a Small World."

That's not a flex. That's the proof of concept.

---

What kepano shipped

Steph Ango — CEO of Obsidian, known as kepano — published an official set of agent skills for Claude Code: github.com/kepano/obsidian-skills.

Four skills. Each one a SKILL.md file that Claude reads before touching your vault.

• obsidian-markdown — correct wikilink syntax, frontmatter, callouts, tags
• obsidian-bases — Obsidian's new database layer (think local Notion databases)
• json-canvas — spatial note maps that actually open in Obsidian
• defuddle — strips web pages to clean markdown before saving

This isn't a community plugin. kepano wrote it himself. That's a product decision about where Obsidian is going.

---

The problem it solves

Before this, Claude Code would write to your vault and silently break things.

Wrong wikilink syntax. Malformed frontmatter. Canvas files that wouldn't open in Obsidian at all.

Claude didn't know Obsidian's proprietary formats. It guessed. It was wrong. Every time.

These skills fix that at the source. Claude reads the format rules before it touches a single file.

---

What it means if you already have a skill ecosystem

I run 8 custom skills against my vault. Daily planner. Bug fixer. YouTube summarizer. Content pipeline. Brain compiler.

They worked. But they were compensating for format gaps, not solving them.

Official skills don't replace your custom ones. They compose.

Drop kepano's into your .claude folder alongside your own. Now both load. Claude knows Obsidian format rules before it touches your workflow logic.

Layered context. Not monolithic prompts. That's the architecture.

---

The one to watch: obsidian-bases

defuddle is the underrated pick for day-to-day use. Web pages are context window poison — nav bars, footers, ad copy, cookie banners. defuddle strips all of it before Claude saves the note. One step from URL to clean vault note.

But obsidian-bases is the signal.

Bases is Obsidian's database layer. Teaching Claude Code to read and write it means they're building toward AI-native knowledge management. Not AI-assisted. AI-native.

That's a different product entirely. And they just declared it officially.

---

Install

npx skills add git@github.com:kepano/obsidian-skills.git

Or clone and copy into your vault's .claude folder manually.

Skills don't auto-load. Invoke them per session:

• /obsidian-markdown
• /obsidian-bases
• /json-canvas

Run /defuddle before any web research session. Non-negotiable.

---

The part about the Disney ride

Here's what I actually want you to take from this.

It's my wife's birthday. I took the day off. We were at Magic Kingdom as a family.

I've been on It's a Small World a hundred times. I know every doll, every song, every inch of that ride. So when I pulled out my phone and saw the news about obsidian-skills, I had the bandwidth to do something with it.

I researched it in Claude chat. Claude drafted the thread in my voice. I sharpened it, sent it. Then posted a one-liner about where I was sitting when I did it.

By the time I walked off that ride and got in line for the Haunted Mansion, this blog post was written. Done. In the queue. While 999 happy haunts waited for me inside.

The whole thing happened in one conversation. No tool switching. No copy-paste between apps. No "now open Hypefury, now open Ghost, now open Buffer."

One conversation. Thought to published. Magic Kingdom to done.

This is not a hustle flex. This is the opposite. The whole point of building this system is that the work happens without friction. A thought becomes a published post without breaking the day.

It's my wife's birthday. I was present. The machine handled the rest.

That's what BlackOps is.

blackopscenter.com