claude-atlas
v1.2.1Source-cited Obsidian knowledge vaults for Claude Code: an inbox to ingest from, one reviewed operation per change, git history in every vault, and skills for ingesting, querying, linting, tasks that live across sessions, canvases, and Bases. Pairs with the claude-atlas binary, which serves the tools.
By nathanadayLicense: MIT0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 17 skill or MCP entries
- Source updated
- Sep 17, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install claude-atlas for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install claude-atlas@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/nathanaday/claude-atlasClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .claude-plugin/plugin.json├── skills/canvas/SKILL.md├── skills/obsidian-bases/SKILL.md├── skills/obsidian-markdown/SKILL.md├── skills/save/SKILL.md├── skills/task/SKILL.md├── skills/task-finish/SKILL.md├── skills/task-plan/SKILL.md├── skills/task-plant/SKILL.md├── skills/task-run/SKILL.md├── skills/think/SKILL.md├── skills/wiki/SKILL.md├── skills/wiki-fold/SKILL.md├── skills/wiki-ingest/SKILL.md├── skills/wiki-lint/SKILL.md├── skills/wiki-mode/SKILL.md├── skills/wiki-query/SKILL.md└── .mcp.json
Included Skills16
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, create canvas, add to canvas, put this on the canvas.
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
Explain, draft, or validate Obsidian Flavored Markdown: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user asks for Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.
Save a user-selected answer, decision, insight, or session summary into the vault as one reviewed operation. Use only when the user asks to keep specific conversation content: /save, save this, save that answer, file this decision, keep this insight, preserve this result. Not for files or URLs; that is wiki-ingest.
Orient in the vault's tasks and route: list what is open, show one task, move it between statuses without ceremony, or hand off to task-plant, task-plan, task-run, and task-finish. Use for tasks, todo, what is open, task board, block or unblock a task, reprioritize, set a due date, my tasks.
Finish a task: done with an outcome, or cancelled with a reason; move its page to the archive and refresh the hot cache. Use for finish, done with the task, close, cancel, kill, abandon, drop this task.
Plan a task: read it, ask what changes the plan, choose an approach or a skill, write the Plan section with a definition of done, and set the status to planned. Use for plan this task, groom, break it down, how should we do this, ready this task.
Plant a task from a sentence or from the notes in inbox/tasks/: a page with status planted, in the user's words, no questions asked. Use for add a task, note a todo, plant this, remember to, open end, later, inbox tasks, task notes.
Execute a planned task and keep its page current: set it active, work the plan, write progress at every stopping point, and hand off when done or blocked. Use for run this task, work on, continue, resume, pick up where we left off, next step on the task.
Apply the 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. A reasoning review, not a vault health check or repair.
Orient in a claude-atlas vault and route work to the right skill. Use for /wiki, set up wiki, vault status, what is in this vault, which skill should I use, adopt this vault, Obsidian vault, second brain, persistent wiki, knowledge base setup.
Create a bounded, extractive, structurally idempotent rollup of recent wiki log entries, previewed by default and applied as one operation on request. Use for fold the log, run a fold, log rollup, roll up log entries, commit the fold. Never modifies child pages.
Turn sources into linked, source-cited wiki pages: files waiting in a project's inbox, or text the user pastes. Use for ingest, ingest the inbox, process this source, read and file this, batch ingest. Not for saving an assistant answer; that is save.
Run the deterministic, read-only health check on the wiki. Use for lint, vault health, audit wiki health, find orphans, find dead links, frontmatter audit, wiki audit. Reports links, orphans, index gaps, frontmatter, empty sections, and ledger problems; it does not repair files.
Read or change the vault's filing mode and see where a new page of a type belongs: generic (typed folders) or lyt (atomic notes and Maps of Content). Use for wiki mode, what is my vault mode, set vault mode, switch to LYT, use generic, methodology routing. Does not move existing notes.
Answer a vault-scoped question from the wiki without changing it. Use when the user selects the vault as the evidence source: query the wiki, what does the vault say, explain from the wiki, summarize the vault, find in wiki, search the wiki, based on my notes. Not for general-knowledge questions.
MCP servers1
- command
- ${CLAUDE_PLUGIN_ROOT}/scripts/atlas
- args
- mcp
Plugin manifests1
{
"name": "claude-atlas",
"version": "1.2.1",
"description": "Source-cited Obsidian knowledge vaults for Claude Code: an inbox to ingest from, one reviewed operation per change, git history in every vault, and skills for ingesting, querying, linting, tasks that live across sessions, canvases, and Bases. Pairs with the claude-atlas binary, which serves the tools.",
"author": {
"name": "nathanaday",
"url": "https://github.com/nathanaday"
},
"license": "MIT",
"homepage": "https://github.com/nathanaday/claude-atlas",
"repository": "https://github.com/nathanaday/claude-atlas",
"keywords": [
"obsidian",
"knowledge-base",
"wiki",
"vault",
"markdown",
"second-brain",
"pkm",
"canvas"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[claude-atlas on Agent Plugins Marketplace](https://pluginsmp.com/plugins/claude-atlas)