obsidian-wiki

A knowledge mgmt system inspired by gist published by Andrej Karpathy about maintaining a personal knowledge base with LLMs : the "LLM Wiki" pattern.

Instead of asking an LLM the same questions over over (or doing RAG every time), you compile knowledge once into interconnected markdown files and keep them current. In this case Obsidian is the viewer and the LLM is the maintainer.

We took that and built a framework around it. The whole thing is a set of markdown skill files that any AI coding agent (Claude Code, Cursor, Windsurf, whatever you use) can read and execute. You point it at your Obsidian vault and tell it what to do.

Quick Start

Install via Skills CLI (recommended)

npx skills add Ar9av/obsidian-wiki

This installs all wiki skills into your current agent (Claude Code, Cursor, Codex, etc.). Then open your agent and say "set up my wiki".

Browse the full skill list at skills.sh/ar9av/obsidian-wiki.

Install via git clone

git clone https://github.com/Ar9av/obsidian-wiki.git
cd obsidian-wiki
bash setup.sh

setup.sh asks for your vault path, writes the config to ~/.obsidian-wiki/config, symlinks skills into all your agents, and installs wiki-update globally so you can use it from any project.

OBSIDIAN_VAULT_PATH is just any directory where you want your wiki documents to live. It can be a new empty folder or an existing Obsidian vault. Obsidian will read from it directly.

Open the project in your agent and say "set up my wiki". That's it.

Agent Compatibility

This framework works with any AI coding agent that can read files. The setup.sh script automatically configures skill discovery for each one:

Agent	Bootstrap Files	Skills Directory	Slash Commands
Claude Code	CLAUDE.md	.claude/skills/ + ~/.claude/skills/ (portable)	✅ /wiki-ingest, /wiki-status, etc.
Cursor	.cursor/rules/obsidian-wiki.mdc	.cursor/skills/	✅ /wiki-ingest, /wiki-status, etc.
Windsurf	.windsurf/rules/obsidian-wiki.md	.windsurf/skills/	✅ via Cascade
Codex (OpenAI)	AGENTS.md	~/.codex/skills/	$wiki-ingest (Codex uses $)
Gemini CLI	GEMINI.md	~/.gemini/skills/	✅ /wiki-ingest, /wiki-query, etc.
Google Antigravity	.agent/rules/obsidian-wiki.md + .agent/workflows/obsidian-wiki.md	.agents/skills/ + ~/.gemini/antigravity/skills/ (legacy)	✅ slash commands via workflows registry
Kiro IDE/CLI	.kiro/steering/obsidian-wiki.md (inclusion: always)	.kiro/skills/ + ~/.kiro/skills/	✅ /wiki-ingest, /wiki-status, etc.
Hermes (NousResearch)	.hermes.md (→ AGENTS.md)	~/.hermes/skills/	✅ /wiki-history-ingest hermes, etc.
OpenClaw	AGENTS.md	~/.openclaw/skills/ + ~/.agents/skills/	✅ /wiki-ingest, /wiki-history-ingest openclaw, etc.
OpenCode	AGENTS.md	~/.agents/skills/	✅ /wiki-ingest, /wiki-query, etc.
Aider	AGENTS.md	~/.agents/skills/	Describe intent in chat — Aider reads the skill it needs
Factory Droid	AGENTS.md	~/.agents/skills/	✅ /wiki-ingest, /wiki-query, etc.
Trae	AGENTS.md	~/.trae/skills/	✅ via Agent tool
Trae CN	AGENTS.md	~/.trae-cn/skills/	✅ via Agent tool
GitHub Copilot (VS Code Chat)	.github/copilot-instructions.md	—	Describe intent in chat
GitHub Copilot (CLI)	—	~/.copilot/skills/	✅ /wiki-ingest, /wiki-query, etc.
Kilocode	AGENTS.md (primary) or CLAUDE.md (compatibility)	.agents/skills/ + .claude/skills/	✅ /wiki-ingest, /wiki-status, etc.

How it works: Each agent has its own convention for discovering skills. setup.sh symlinks the canonical .skills/ directory into each agent's expected location, and creates the bootstrap file that tells the agent about the project. You write skills once, every agent can use them.

Manual setup (if you prefer)

If you don't want to run setup.sh, you can configure your agent manually:

Claude Code

Skills are auto-discovered from .claude/skills/. Either:

• Run setup.sh to create symlinks, OR
• Copy .skills/* to .claude/skills/

The CLAUDE.md file at the repo root is automatically loaded as project context.

cd /path/to/obsidian-wiki && claude "set up my wiki"

Cursor

Skills are auto-discovered from .cursor/skills/. The .cursor/rules/obsidian-wiki.mdc file provides always-on context. Either:

• Run setup.sh to create symlinks, OR
• Copy .skills/* to .cursor/skills/

Open the project in Cursor and type /wiki-setup in the chat.

Windsurf

Cascade reads rules from .windsurf/rules/ and skills from .windsurf/skills/. Either:

• Run setup.sh to create symlinks, OR
• Copy .skills/* to .windsurf/skills/

Open in Windsurf and tell Cascade: "set up my wiki".

Codex (OpenAI)

Codex reads the AGENTS.md file at the repo root for project context. setup.sh installs skills globally to ~/.codex/skills/, making them available from any project. Either:

• Run setup.sh to create symlinks globally, OR
• Manually symlink .skills/* to ~/.codex/skills/

cd /path/to/obsidian-wiki && codex "set up my wiki"

Gemini CLI

Gemini CLI reads GEMINI.md at the repo root and discovers global skills from ~/.gemini/skills/. Either:

• Run setup.sh to create symlinks globally, OR
• Manually symlink .skills/* to ~/.gemini/skills/

cd /path/to/obsidian-wiki && gemini "set up my wiki"

Google Antigravity

Antigravity's always-on mechanism is .agent/rules/ + .agent/workflows/. setup.sh ships both files committed at the repo root and symlinks skills into .agents/skills/. The legacy ~/.gemini/antigravity/skills/ path is also wired for backwards-compat.

• Run setup.sh, OR
• Manually copy .agent/rules/obsidian-wiki.md and .agent/workflows/obsidian-wiki.md into your project and symlink .skills/* to .agents/skills/

Open in Antigravity and say "set up my wiki".

Kiro IDE/CLI

Kiro's always-on mechanism is .kiro/steering/*.md with inclusion: always. setup.sh ships .kiro/steering/obsidian-wiki.md committed and symlinks .skills/* into both .kiro/skills/ (project) and ~/.kiro/skills/ (global).

• Run setup.sh, OR
• Manually symlink .skills/* to .kiro/skills/ and ~/.kiro/skills/

Invoke with /wiki-ingest, /wiki-query, etc.

OpenCode

OpenCode reads AGENTS.md at the repo root natively. setup.sh symlinks skills into ~/.agents/skills/ (OpenCode's shared discovery path alongside AGENTS.md-aware agents).

cd /path/to/obsidian-wiki && opencode "set up my wiki"

Aider

Aider reads AGENTS.md at the repo root. Skills are referenced by path — Aider follows the instructions in AGENTS.md to read the relevant SKILL.md files. Skills are also mirrored to ~/.agents/skills/ by setup.sh for cross-project use.

cd /path/to/obsidian-wiki && aider

Then say "set up my wiki" in the chat.

Factory Droid

Droid reads AGENTS.md at the repo root and discovers skills from ~/.agents/skills/. setup.sh wires both.

cd /path/to/obsidian-wiki && droid "set up my wiki"

Trae / Trae CN

Trae reads AGENTS.md as its always-on mechanism (no hook support — rules file is the discovery path). setup.sh symlinks skills into ~/.trae/skills/ and ~/.trae-cn/skills/ respectively.

• Run setup.sh, OR
• Manually symlink .skills/* to ~/.trae/skills/ (or ~/.trae-cn/skills/)

Open the project in Trae and say "set up my wiki".

GitHub Copilot (CLI)

The Copilot CLI discovers skills from ~/.copilot/skills/. setup.sh symlinks .skills/* there automatically.

• Run setup.sh, OR
• Manually symlink .skills/* to ~/.copilot/skills/

Invoke with /wiki-ingest, /wiki-query, etc. from any project.

Note: the CLI and the VS Code Chat extension are configured separately — VS Code Chat uses .github/copilot-instructions.md (see section above).

Hermes

Hermes reads .hermes.md first (if present), then falls back to AGENTS.md. Skills are discovered globally from ~/.hermes/skills/. Either:

• Run setup.sh to create global symlinks, OR
• Manually symlink .skills/* to ~/.hermes/skills/

cd /path/to/obsidian-wiki && hermes "set up my wiki"

To mine your Hermes history into the wiki:

/wiki-history-ingest hermes

This reads ~/.hermes/memories/ and (if enabled) ~/.hermes/sessions/.

OpenClaw

OpenClaw is a local agent daemon that exposes itself through chat channels (Telegram, Slack, Discord, etc.). It reads AGENTS.md first (priority 10 in its bootstrap chain), then discovers skills from two paths: ~/.openclaw/skills/ (managed) and ~/.agents/skills/ (shared). Both are wired by setup.sh.

Skills are auto-registered as slash commands — /wiki-ingest, /wiki-query, /wiki-history-ingest, etc. all work natively.

• Run setup.sh to create symlinks in both paths, OR
• Manually symlink .skills/* into ~/.openclaw/skills/ and ~/.agents/skills/

cd /path/to/obsidian-wiki && openclaw "set up my wiki"

To mine your OpenClaw history into the wiki:

/wiki-history-ingest openclaw

This reads ~/.openclaw/workspace/MEMORY.md, daily notes in ~/.openclaw/workspace/memory/, and (if enabled) session transcripts in ~/.openclaw/agents/*/sessions/.

GitHub Copilot

Copilot reads .github/copilot-instructions.md for project context. Skills are referenced by path — Copilot will follow the instructions to read the relevant SKILL.md files.

Use Copilot Chat in VS Code and say "set up my wiki".

How it works

Every ingest runs through four stages:

1. Ingest — The agent reads your source material directly. It handles whatever you throw at it: markdown files, PDFs (with page ranges), JSONL conversation exports, plain text logs, chat exports, meeting transcripts, and images (screenshots, whiteboard photos, diagrams — vision-capable model required). No preprocessing step, no pipeline to run. The agent reads the file the same way it reads code.

2. Extract — From the raw source, the agent pulls out concepts, entities, claims, relationships, and open questions. A conversation about debugging a React hook yields a "stale closure" pattern. A research paper yields the key idea and its caveats. A work log yields decisions and their rationale. Noise gets dropped, signal gets kept. Each page also gets a 1–2 sentence summary: in its frontmatter at write time — later queries use this to preview pages without opening them.

3. Resolve — New knowledge gets merged against what's already in the wiki. If a concept page exists, the agent updates it — merging new information, noting contradictions, strengthening cross-references. If it's genuinely new, a page gets created. Nothing is duplicated. Sources are tracked in frontmatter so every claim stays attributable.

4. Schema — The wiki schema isn't fixed upfront. It emerges from your sources and evolves as you add more. The agent maintains coherence: categories stay consistent, wikilinks point to real pages, the index reflects what's actually there. When you add a new domain (a new project, a new field of study), the schema expands to accommodate it without breaking what exists.

A .manifest.json tracks every source that's been ingested — path, timestamps, which wiki pages it produced. On the next ingest, the agent computes the delta and only processes what's new or changed.

What we added on top of Karpathy's pattern

• Delta tracking. A manifest tracks every source file that's been ingested: path, timestamps, which wiki pages it produced. When you come back later, it computes the delta and only processes what's new or changed. You're not re-ingesting your entire document library every time.

• Project-based organization. Knowledge gets filed under projects when it's project-specific, globally when it's not. Both are cross-referenced with wikilinks. If you're working on 10 different codebases, each one gets its own space in the vault.

• Archive and rebuild. When the wiki drifts too far from your sources, you can archive the whole thing (timestamped snapshot, nothing lost) and rebuild from scratch. Or restore any previous archive.

• Multi-agent ingest. Documents, PDFs, Claude Code history (~/.claude), Codex sessions (~/.codex/), Hermes memories and sessions (~/.hermes/), OpenClaw MEMORY.md and sessions (~/.openclaw/), Windsurf data (~/.windsurf), ChatGPT exports, Slack logs, meeting transcripts, raw text. There are dedicated skills for Claude, Codex, Hermes, and OpenClaw history, plus a catch-all ingest skill for arbitrary text exports.

• Audit and lint. Find orphaned pages, broken wikilinks, stale content, contradictions, missing frontmatter. See a dashboard of what's been ingested vs what's pending.

• Automated cross-linking. After ingesting new pages, the cross-linker scans the vault for unlinked mentions and weaves them into the knowledge graph with [[wikilinks]]. No more orphan pages.

• Tag taxonomy. A controlled vocabulary of canonical tags stored in _meta/taxonomy.md, with a skill that audits and normalizes tags across your entire vault.

• Provenance tracking. Every claim on a wiki page is tagged: extracted (default), ^[inferred] (LLM synthesis), or ^[ambiguous] (sources disagree). A provenance: block in the frontmatter summarizes the mix per page, and wiki-lint flags pages that drift into mostly speculation. You can always tell what your wiki actually knows from what it guessed.

• Multimodal sources. Screenshots, whiteboard photos, slide captures, and diagrams ingest the same way as text — the agent transcribes any visible text verbatim and tags interpreted content as inferred. Requires a vision-capable model.

• Wiki insights. Beyond delta tracking, wiki-status can analyze the shape of your vault itself: top hubs, bridge pages (nodes whose removal would partition the graph), tag cluster cohesion scores, scored surprising connections, a graph delta since last run, and suggested questions the wiki structure is uniquely positioned to answer. Output goes to _insights.md.

• Graph export. wiki-export turns the vault's wikilink graph into graph.json (queryable), graph.graphml (Gephi/yEd), cypher.txt (Neo4j), and a self-contained graph.html interactive browser visualization — no server required.

• Tiered retrieval. wiki-query reads titles, tags, and page summaries first and only opens page bodies when the cheap pass can't answer. Say "quick answer" or "just scan" to force index-only mode. Keeps query cost roughly flat as your vault grows from 20 pages to 2000.

• QMD semantic search (optional). QMD is a local MCP server that indexes your wiki and source documents for fast semantic search. When QMD_WIKI_COLLECTION is set in .env, wiki-query runs a lex+vec pass against the collection before falling back to Grep — enabling concept-level matches that exact-string search misses. When QMD_PAPERS_COLLECTION is set, wiki-ingest queries your indexed sources before writing a new page, surfacing related work, detecting contradictions, and deciding whether to create or merge. Without QMD, both skills fall back to Grep/Glob and remain fully functional.

• _raw/ staging directory. Drop rough notes, clipboard pastes, or quick captures into _raw/ inside your vault. The next wiki-ingest run promotes them to proper wiki pages and removes the originals. Configured via OBSIDIAN_RAW_DIR in .env (defaults to _raw).

Optional: QMD Semantic Search

By default, wiki-ingest and wiki-query use Grep/Glob for search — fully functional, no extra setup. If your vault grows large or you want concept-level matches across your sources, you can plug in QMD: a local MCP server that runs lex+vec queries against indexed collections.

Setup:

1. Install QMD and add it to your MCP config (see the QMD repo for instructions).
2. Index your wiki and/or source documents:

   qmd index --name wiki /path/to/your/vault
   qmd index --name papers /path/to/your/sources

3. Set the collection names in your .env:

   QMD_WIKI_COLLECTION=wiki      # used by wiki-query
   QMD_PAPERS_COLLECTION=papers  # used by wiki-ingest (source discovery)

What changes with QMD enabled:

• wiki-query runs a semantic pass (lex+vec) against your wiki collection before falling back to Grep. Finds conceptually related pages even when the exact terms don't match.
• wiki-ingest queries your papers collection before writing a new page — surfaces related sources, spots contradictions, and decides whether to create a new page or merge into an existing one.

Both skills degrade gracefully: if QMD_WIKI_COLLECTION / QMD_PAPERS_COLLECTION are not set, they skip the QMD step silently and use Grep instead.

_raw/ Staging Directory

_raw/ is a staging area inside your vault for unprocessed captures — rough notes, clipboard pastes, quick voice-memo transcripts. Drop files there and the next wiki-ingest run will promote them to proper wiki pages and remove the originals.

The directory is created automatically by wiki-setup. The path is configurable via OBSIDIAN_RAW_DIR in .env (defaults to _raw).

---

Skills

Everything lives in .skills/. Each skill is a markdown file the agent reads when triggered:

Skill	What it does	Slash Command
wiki-setup	Initialize vault structure	/wiki-setup
wiki-ingest	Distill documents into wiki pages	/wiki-ingest
wiki-history-ingest	Unified history router (claude, codex, or hermes)	`/wiki-history-ingest <claude
claude-history-ingest	Mine your ~/.claude conversations and memories	/claude-history-ingest
codex-history-ingest	Mine your ~/.codex sessions and rollout logs	/codex-history-ingest
hermes-history-ingest	Mine your ~/.hermes memories and sessions	/hermes-history-ingest
openclaw-history-ingest	Mine your ~/.openclaw MEMORY.md and sessions	/openclaw-history-ingest
data-ingest	Ingest any text — chat exports, logs, transcripts	/data-ingest
wiki-status	Show what's ingested, what's pending, the delta	/wiki-status
wiki-rebuild	Archive, rebuild from scratch, or restore	/wiki-rebuild
wiki-query	Answer questions from the wiki	/wiki-query
wiki-lint	Find broken links, orphans, contradictions	/wiki-lint
cross-linker	Auto-discover and insert missing wikilinks	/cross-linker
tag-taxonomy	Enforce consistent tag vocabulary across pages	/tag-taxonomy
llm-wiki	The core pattern and architecture reference	/llm-wiki
wiki-update	Sync current project's knowledge into the vault	/wiki-update
wiki-export	Export vault graph to JSON, GraphML, Neo4j, HTML	/wiki-export
skill-creator	Create new skills	/skill-creator

Note: Slash commands (/skill-name) work in Claude Code, Cursor, and Windsurf. In other agents, just describe what you want and the agent will find the right skill.

Recommended: Obsidian Skills by Kepano

We handle the knowledge management workflow — ingest, query, lint, rebuild. For Obsidian format mastery, we recommend installing kepano/obsidian-skills alongside this framework. These are optional but improve the quality of wiki output:

Skill	What it adds
obsidian-markdown	Teaches the agent correct Obsidian-flavored syntax — wikilinks, callouts, embeds, properties
obsidian-bases	Create and edit .base files (database-like views of notes)
json-canvas	Create and edit .canvas files (visual mind maps, flowcharts)
obsidian-cli	Interact with a running Obsidian instance via CLI (search, create, manage notes)
defuddle	Extract clean markdown from web pages — less noise than raw fetch, saves tokens during ingest

Both projects use the same Agent Skills spec, so they coexist in the same .skills/ directory with no conflicts.

Install:

npx skills add kepano/obsidian-skills

After installing, your agent will automatically pick up the new skills alongside the existing wiki skills.

Project Structure

obsidian-wiki/
├── .skills/                          # ← Canonical skill definitions (source of truth)
│   ├── wiki-setup/SKILL.md
│   ├── wiki-ingest/SKILL.md
│   ├── wiki-history-ingest/SKILL.md
│   ├── claude-history-ingest/SKILL.md
│   ├── codex-history-ingest/SKILL.md
│   ├── hermes-history-ingest/SKILL.md
│   ├── openclaw-history-ingest/SKILL.md
│   ├── data-ingest/SKILL.md
│   ├── wiki-status/SKILL.md
│   ├── wiki-rebuild/SKILL.md
│   ├── wiki-query/SKILL.md
│   ├── wiki-lint/SKILL.md
│   ├── cross-linker/SKILL.md
│   ├── tag-taxonomy/SKILL.md
│   ├── wiki-update/SKILL.md
│   ├── llm-wiki/SKILL.md
│   ├── wiki-export/SKILL.md
│   └── skill-creator/SKILL.md
│
├── CLAUDE.md                            # Bootstrap → Claude Code / Kilocode (→ AGENTS.md)
├── GEMINI.md                            # Bootstrap → Gemini CLI (→ AGENTS.md)
├── AGENTS.md                            # Bootstrap → Codex, OpenCode, Aider, Droid, Trae, Hermes, OpenClaw, Kilocode
├── .hermes.md                           # Bootstrap → Hermes (symlink → AGENTS.md)
├── .cursor/rules/obsidian-wiki.mdc      # Always-on → Cursor (alwaysApply: true)
├── .windsurf/rules/obsidian-wiki.md     # Always-on → Windsurf
├── .kiro/steering/obsidian-wiki.md      # Always-on → Kiro (inclusion: always)
├── .agent/rules/obsidian-wiki.md        # Always-on → Google Antigravity
├── .agent/workflows/obsidian-wiki.md    # Slash-command registry → Google Antigravity
├── .github/copilot-instructions.md      # Always-on → GitHub Copilot (VS Code Chat)
│
├── .claude/skills/   → symlinks to .skills/*  (created by setup.sh)
├── .cursor/skills/   → symlinks to .skills/*  (created by setup.sh)
├── .windsurf/skills/ → symlinks to .skills/*  (created by setup.sh)
├── .agents/skills/   → symlinks to .skills/*  (created by setup.sh)
├── .kiro/skills/     → symlinks to .skills/*  (created by setup.sh)
│
├── ~/.claude/skills/              → portable skills (wiki-update, wiki-query)
├── ~/.gemini/skills/              → global symlinks — Gemini CLI
├── ~/.gemini/antigravity/skills/  → global symlinks — Antigravity (legacy path)
├── ~/.codex/skills/               → global symlinks — Codex
├── ~/.hermes/skills/              → global symlinks — Hermes
├── ~/.openclaw/skills/            → global symlinks — OpenClaw (managed)
├── ~/.copilot/skills/             → global symlinks — GitHub Copilot CLI
├── ~/.trae/skills/                → global symlinks — Trae
├── ~/.trae-cn/skills/             → global symlinks — Trae CN
├── ~/.kiro/skills/                → global symlinks — Kiro CLI
├── ~/.agents/skills/              → global symlinks — OpenCode, Aider, Droid, generic
│
├── setup.sh                          # One-command agent setup
├── .env.example                      # Configuration template
├── README.md                         # You are here
└── SETUP.md                          # Detailed setup guide

Using from other projects

The whole point is that your wiki should stay up to date as you work across different codebases. You don't want to come back to the obsidian-wiki repo every time. So setup.sh installs two global skills that work from any project: wiki-update and wiki-query.

When you run bash setup.sh, it does the following:

1. Writes a config to ~/.obsidian-wiki/config with your vault path and the repo location. This is how the skills know where to read and write.
2. Symlinks wiki-update and wiki-query into ~/.claude/skills/ so they're available everywhere in Claude Code.
3. Symlinks all skills into every agent's global discovery path:
   • ~/.gemini/skills/ — Gemini CLI (canonical)
   • ~/.gemini/antigravity/skills/ — Google Antigravity (legacy)
   • ~/.codex/skills/ — Codex
   • ~/.hermes/skills/ — Hermes
   • ~/.openclaw/skills/ — OpenClaw (managed)
   • ~/.copilot/skills/ — GitHub Copilot CLI
   • ~/.trae/skills/ + ~/.trae-cn/skills/ — Trae / Trae CN
   • ~/.kiro/skills/ — Kiro CLI
   • ~/.agents/skills/ — OpenCode, Aider, Factory Droid, and other AGENTS.md-aware agents

After that, you're in some project, say ~/projects/my-cool-app, working with Claude. Two commands:

# You're working on some project
cd ~/projects/my-cool-app
claude

# Write to the wiki: distill what you've learned
> /wiki-update

# Read from the wiki: pull context about anything you've captured before
> /wiki-query what do I know about rate limiting?

/wiki-update reads your project, figures out what's worth keeping, and distills it into your Obsidian vault. Architecture decisions, patterns you discovered, key concepts, trade-offs you evaluated. It doesn't copy code or dump file listings. It distills the stuff you'd forget in 3 months. Next time you run it from the same project, it checks what changed since last sync (via git log) and only processes the delta.

/wiki-query goes the other direction. You're working on something and you want to know what your wiki says about a topic. Maybe you solved a similar problem 2 months ago in a different project and the answer is already in your vault. The agent searches the wiki, reads the relevant pages, and gives you a synthesized answer with citations.

Both skills follow the same Karpathy pattern as everything else. If a concept page already exists in the vault, it merges into it. Everything gets cross-linked with [[wikilinks]], tracked in .manifest.json, and logged.

Contributing

This is early. The skills work but there's a lot of room to make them smarter — better cross-referencing, smarter deduplication, handling larger vaults, new ingest sources. If you've been thinking about this problem or have a workflow that could be a skill, PRs are welcome.

Adding a new skill

1. Create a folder in .skills/your-skill-name/
2. Add a SKILL.md with YAML frontmatter (name, description) and markdown instructions
3. Run bash setup.sh to symlink into all agent directories
4. Test with your agent by saying something that matches the description

See .skills/skill-creator/SKILL.md for the full guide on writing effective skills.