nathanaday
UserMulti-tasking upgrade! Store durable knowledge in all your projects and connect them together. Let agents work using the full context of everything you are working on at once.
Categories
Indexed Skills (57)
task-finish
Finish a task: done with an outcome, or cancelled with a reason; archive its page, then offer the knowledge base what the work taught. Use for finish, done with the task, close, cancel, kill, abandon, drop this task.
task-plan
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.
task-run
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.
task
Orient in a project's tasks and route: list what is open by phase, show one task, move it between statuses without ceremony, create or change a phase, review the whole list for what is misguided or missing, 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, phases, review my tasks, what should I work on.
atlas-knowledge
Create a knowledge base step by step: name, location, a scope written well, the filing mode. Also change a scope, rename, adopt an existing Obsidian vault, or forget one. Use for new knowledge base, create a knowledge base, knowledge base for papers, change the scope, adopt this vault, forget this knowledge base.
atlas-merge
Merge the wikis of a hub's members into the hub's own: find the pages two members wrote about one thing and upgrade them into the hub, and build bridge pages that join neighbouring pages across members, as one merge the user approves. Use for merge the members, consolidate the wikis, merge the knowledge bases, what overlaps across projects, find duplicates across projects, bridge the vaults, upgrade pages to the parent, adopt a new member's wiki. Duplicates inside one wiki are wiki-review's.
atlas-onboard
Make a folder a project in one guided flow: a blank folder gets its wiki, its threads, and a git repository; a long-lived repository or folder of documents also gets the page that describes it, a wiki structure the user approves, and threads for the work already in flight (TODO and FIXME markers, roadmap documents, open issues). Use for onboard this, onboard this repo, new project, init here, make this a project, set up a wiki here, set up atlas, adopt this codebase, start a project.
thread-work
Move work forward: take a thread, or a sentence that becomes one, to its next stage, and on through the stages while the user agrees: stub, spec, plan, run, receipt. It sizes the ceremony to the change, stops for the user's yes at the spec and at the plan, and works in small commits with subagents. Use for do this, make this change, implement, build, fix this, work on this, start on this now, continue this thread, next step, move this thread on, take this to the next stage. To only look at the board, thread.
wiki-base
Draft, explain, and change Obsidian Bases views over the wiki: .base files with filters, formulas, properties, summaries, and table, card, or list views, written as one reviewed operation. Use for a Base, Bases, a database view of the wiki, a dynamic table, a reading list, a tracker, filters, formulas, .base file edits.
wiki-canvas
Create, inspect, and change Obsidian canvas boards in the wiki: JSON Canvas files with text, file, link, and group nodes and the edges between them, written as one reviewed operation. Use for a canvas, a visual map, a board, zones, a spatial layout, add these pages to a canvas, put this on the canvas, canvas status.
wiki-describe
Describe the work in the project's own wiki: stage a snapshot of it at the current commit, read it and the code, and write the entity page that says what the project is, how it is built and laid out, what it delivers, and the concepts it introduces; or bring that page up to date after the work moved on. Use for describe this project, map the repo, the wiki does not know this work, update the project page, the project page is behind. A whole first setup of a folder is atlas-onboard, which calls this.
wiki-edit
Change wiki pages that exist, as one reviewed operation: rewrite or correct a page, rename or move it with every link that names it updated, split a page that grew too big, combine two pages about one thing, restructure folders after a mode or profile change, repair what wiki-review found, and seed the pages the wiki's links want. Use for edit this page, fix this page, rename the page, move the page, split this page, combine these pages, merge these two pages, reorganize the wiki, fix the dead links, fix the lint findings, repair, stub the wanted pages, fill the stubs. New knowledge from a source is wiki-ingest; from the conversation, wiki-save.
wiki-review
Check the wiki's health and report what is wrong, without changing it. Quick review is deterministic and cheap: lint's structure findings, near-duplicate pages, pages that cite no source, stubs, and wanted pages, from the tools alone. Deep review sends read-only reviewers over sections of the wiki for gaps, errors, contradictions, and stale claims, and costs more. Use for review the wiki, wiki health, lint, audit the wiki, find orphans, find dead links, find duplicates, what is wrong with the wiki, deep review, check the wiki for mistakes, find gaps, find contradictions. Fixing what it finds is wiki-edit.
wiki-save
Keep something from the conversation in the project's wiki: an answer, a decision, an insight, or a session summary the user selects, as one reviewed operation. Use for save this, save that answer, keep this, file this decision, keep this insight, preserve this result, remember this in the wiki. Not for files or URLs (wiki-ingest) or for changing a page that exists (wiki-edit).
atlas-project
Change a project that exists: its name, description, filing mode (generic or lyt), threads on or off, and members, which make it a hub that mirrors other projects' wikis; sync the members; or forget the project. Use for rename the project, change the description, what is my mode, switch to lyt, use generic, turn threads off, add a member, link projects, make a hub, mirror another project, sync the members, forget this project. To make a new project, atlas-onboard.
thread-receipt
Verify and close a thread with its receipt: before completed, run the checks and, for a change to code, have a fresh reviewer read the diff against the spec; then file what was delivered and how it was verified, or, killed, the reason; then offer the wiki what the work taught. Use for finish, done, close this thread, complete, ship it, review the work, kill, cancel, abandon, drop this thread, wrap up.
thread-run
Do the work of a thread and keep its plan document current: work the plan in slices, commit along the way, test, write progress at every stopping point, and hand off when done or blocked. Use for run this thread, work on, implement, continue, resume, pick up where we left off, next step.
thread-spec
Turn a thread's stub into a spec: read the stub, research the code and the wiki, decide what can be decided, ask only what cannot, and file the spec document. Use for spec this, define this thread, brainstorm, think this through, weigh the options, tradeoffs, what should this be, flesh out the stub, requirements, design this.
thread
Orient in the project's threads: show the board by stage or one thread end to end, change a card (priority, phase, title, block, unblock), create or change a phase, and review the whole board for what is misguided, duplicated, or missing. Use for threads, board, what is open, what should I work on next, my threads, block, unblock, reprioritize, phases, review the board. To move a thread forward, thread-work.
wiki-fold
Roll up a range of the wiki's log into one fold page: extractive, bounded, and the same every time for the same entries; previewed first, applied as one operation on request. Use for fold the log, run a fold, log rollup, roll up log entries, what happened in the wiki lately, commit the fold. Never changes the entries or the pages they name.
wiki-ingest
Turn sources into linked, source-cited wiki pages: files waiting in the project's inbox, files or folders elsewhere, or text the user pastes. A source of any size: a short one is read whole, a long one (a book, a slide deck, hundreds of pages) is split across parallel workers and reduced into pages. Use for ingest, ingest the inbox, process this source, read and file this, batch ingest, ingest this PDF, ingest this book. Not for keeping part of the conversation; that is wiki-save.
wiki-query
Answer a question from the project's wiki, with citations, without changing it: the project's own pages and the mirrors of its members. Use for query the wiki, what does the wiki say, what do we know about, explain from the wiki, summarize the wiki, find in the wiki, search the wiki, based on my notes. Not for general-knowledge questions; keeping the answer is wiki-save.
wiki
Orient in this project and its wiki: what the project is, what the wiki holds, the rules for changing it, and which wiki skill does what. Use for /wiki, project status, what is in this wiki, where am I, how does the wiki work, how do I change a page, Obsidian vault, second brain, open the vault, Obsidian colors, plugins.
atlas
The front door: see every project on this machine and what is wrong with them, change the atlas settings, and find the right skill for any request. Use for /atlas, my projects, list projects, what projects do I have, which skill should I use, what can atlas do, refresh the atlas, atlas settings, set new-days, what is wrong with the atlas.
thread-plan
Plan a thread: read its spec, explore the code as in plan mode, and file what you found as the plan document: the approach, where the work lands, the order, how it is tested, the risks. Use for plan this thread, how should we build this, approach, break it down, ready this thread.
canvas
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.
describe
Describe the work in the project's own wiki: stage a snapshot of it at the current commit, read it and the code, and write the entity page that says what the project is, how it is built and laid out, what it delivers, and the concepts it introduces; or bring that page up to date after the work moved on. Use for describe this project, map the repo, onboard this codebase, the wiki does not know this work, update the project page, the project page is behind.
obsidian-bases
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.
obsidian-markdown
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
Save a user-selected answer, decision, insight, or session summary into the project's wiki 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.
think
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.
wiki-lint
Run the deterministic, read-only health check on the project's wiki. Use for lint, wiki 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.
save
Save a user-selected answer, decision, insight, or session summary into the knowledge base 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.
wiki-ingest
Turn sources into linked, source-cited wiki pages: files waiting in the knowledge base'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.
wiki-query
Answer a question from the knowledge base without changing it. Use when the user selects the knowledge base as the evidence source: query the wiki, what does the knowledge base say, explain from the wiki, summarize the wiki, find in wiki, search the wiki, based on my notes. Not for general-knowledge questions.
wiki
Orient in a claude-atlas session and route work to the right skill. Use for /wiki, set up wiki, vault status, what is in this knowledge base, which skill should I use, adopt this vault, Obsidian vault, second brain, persistent wiki, knowledge base setup.
wiki-lint
Run the deterministic, read-only health check on the knowledge base. 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.
atlas-project
Make the current folder a project, or change one: name, description, which knowledge base it uses; link, unlink, rename, describe, forget. Use for new project, init here, make this a project, project for this repo, link the knowledge base, unlink, rename the project, forget this project.
atlas
Orient in the whole atlas and route: every knowledge base and the projects that use it, what is wrong, the settings. Use for /atlas, my vaults, list knowledge bases, what projects do I have, which knowledge bases, refresh the atlas, atlas settings, set new-days, what is wrong with the atlas.
describe
Describe a project in its knowledge base: stage a snapshot of its work at the current commit, read it and the work, and write the entity page that says what the project is, how it is built and laid out, what it delivers, and the concepts it introduces; or bring such a page up to date after the work moved on. Use for describe this project, map the repo, onboard this codebase, the knowledge base does not know this project, update the project page, project pages are behind.
work
Take a change from a sentence to work in the right projects, as a thread: gather the facts from the knowledge base and the project pages, name the projects the change touches, open a thread in each, file its plan, and start. Use for do this, make this change, implement, build, fix this, fix this across the projects, work on this, which project does this go in, start on this now.
thread-receipt
Close a thread with its receipt: completed, with what was delivered and how it was verified, or killed, with the reason; then offer the knowledge base what the work taught. Use for finish, done, close this thread, complete, ship it, kill, cancel, abandon, drop this thread, wrap up.
thread-run
Do the work of a thread and keep its plan document current: work the plan in slices, commit along the way, test, write progress at every stopping point, and hand off when done or blocked. Use for run this thread, work on, implement, continue, resume, pick up where we left off, next step.
thread-spec
Turn a thread's stub into a spec: read the stub, research the code and the knowledge base, decide what can be decided, ask only what cannot, and file the spec document. Use for spec this, define this thread, brainstorm, think this through, what should this be, flesh out the stub, requirements, design this.
thread
Orient in a project's threads and route: show the board by stage, show one thread end to end, reprioritize, block or unblock, rename, move to a phase, create or change a phase, review the whole board for what is misguided or missing, or hand off to the stage skills. Use for threads, board, what is open, what should I work on, todo, tasks, my threads, block, unblock, reprioritize, phases, review the board.
wiki-fold
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.
canvas
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.
obsidian-bases
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.
obsidian-markdown
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.
think
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.
task-plant
Plant a task from a sentence, from the notes in a project's atlas/inbox/, or into any project from its knowledge base: 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, plant this in project X.
thread-stub
Open a thread and stop there: a card and a stub in the user's words, from a sentence, from notes waiting in the project's inbox, or in another project the atlas lists, with no questions asked. Use for add a thread, note this, stub this, remember to, open a thread, report a bug, idea for later, todo, inbox notes, open this in project X. To start the work now, thread-work.
wiki-mode
Read or change the project's filing mode and see where a new wiki page of a type belongs: generic (typed folders) or lyt (atomic notes and Maps of Content). Use for wiki mode, what is my mode, set the mode, switch to LYT, use generic, methodology routing. Does not move existing notes.
work
Take a change from a sentence to working code, as a thread: gather the facts from the wiki and the work, open the thread, file its plan, and start. Use for do this, make this change, implement, build, fix this, work on this, start on this now.
thread-plan
Plan a thread: read its spec, explore the code as in plan mode, and file what you found as the plan document: the approach, where the work lands, the order, how it is tested, the risks. Use for plan this thread, how should we build this, approach, break it down, ready this thread.
thread-stub
Open a thread from a sentence, from the notes in a project's atlas/<name>/inbox/, or in any project from its knowledge base: a card and a stub in the user's words, no questions asked. Use for add a thread, note this, stub this, remember to, open a thread, report a bug, idea for later, todo, inbox notes, open this in project X.
wiki-mode
Read or change the knowledge base'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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.