Loading...
Loading...
Found 10 Skills
Save session context, decisions, progress, and plans to the Claude Brain Logseq graph. Triggers: "save to brain", "save this", "remember this", "store this decision", "log this", "save progress", "before I quit", "wrap up". Don't fire for read operations (use brain-load) or status checks (use brain-status).
Enables Claude to create and manage notes in Logseq via Playwright MCP
Set up the Claude Brain Logseq graph (first-time) or add a new project page. Triggers: "init brain", "setup brain", "init brain project <name>", "add project to brain". Don't fire for loads, saves, or status checks — those are handled by brain-load, brain-save, and brain-status.
Load project context from the Claude Brain Logseq graph into the current session. Triggers: "load brain", "load <project>", "resume <project>", "continue work on <project>", "what do we know about <topic>". Don't fire for write operations (use brain-save), generic questions about Logseq itself, or "open <file>" / "switch to <branch>" requests that mean opening files or switching git branches rather than loading project memory.
Operate the current Logseq command-line interface to inspect or modify graphs, pages, blocks, tags, and properties; run Datascript queries; show page/block trees; manage graphs; and manage db-worker-node servers. Use when a request involves running `logseq` commands or interpreting CLI output.
Logseq Datascript schema, built-in properties/classes, and :db/ident discovery for composing or reviewing Datascript queries about blocks/pages/tags/properties/classes. Use whenever editing or reviewing Datascript pull selectors or queries, or any code that adds/removes attributes in pull patterns, or touches property namespaces/identifiers, or requires reasoning about property value shapes/ref/cardinality in Logseq.
Format and file Logseq notes to this user's vault conventions — the `journals/` and `pages/` directories, `YYYY_MM_DD.md` journal filenames, heading-and-hashtag categories, namespaces, and page properties. Use this skill whenever reading, creating, formatting, or modifying Logseq notes. Triggers on "logseq", "journal entry", "daily note", "add this to my notes", "#learnings", "namespace", or any edit to a file inside a Logseq vault.
Auto-capture technical realizations to Logseq when the user shares how tools or systems actually work. PROACTIVELY invoke without waiting to be asked. Pattern: declarative statements (not questions) revealing expectation vs reality — 'didn't know X does Y', 'turns out Z', '[tool] actually [behavior]', 'figured out why', 'the reason is', 'good to know', 'oh interesting', 'TIL', 'wait so', 'huh'. Skip questions, task requests, trivial fixes, and secondhand info. Manual trigger: user says 'capture/save/document this learning'.
Show a dashboard of all projects in the Claude Brain graph. Triggers: "brain status", "show projects", "show brain", "what's in my brain", "project dashboard", "brain overview", "list projects", "summary". Don't fire for loads (use brain-load) or saves (use brain-save).
Universal migration from Obsidian, Notion, Logseq, markdown, CSV, JSON, Roam