正在加载视频...

视频加载失败

🛑 If you're still exporting Google Docs as Markdown, or spreadsheets as CSVs... it's time to stop! The GWorkspace and Obsidian CLIs have saved me so much time pulling context into Claude Code, Codex, etc. Here's a rundown

54,298 次观看 • 7 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

I still don’t understand why people keep building a Claude second brain by hand when these 10 repos already built the whole system They turn your Claude sessions into a wiki, let Claude read and write your vault from your phone, and one of them comes straight from Obsidian’s own CEO 01 llm-wiki → your Claude Code and Codex sessions become a searchable wiki, with an MCP server to query it 02 llm-wiki-claude-skill → one skill file teaches Claude to ingest sources, answer from them, lint the wiki and compile it into clean pages 03 obsidian-skills → Obsidian’s own CEO teaches Claude how Obsidian really works 04 llm-wiki → a Claude Code plugin with init, ingest, compile, query and lint, where every change is committed to git 05 obsidian-dev-second-brain → your tickets, sprints and project docs live in the vault as notes, and Claude keeps them in sync with the code 06 obsidian-mcp-server → 14 tools to read, write, search and surgically edit notes, tags and frontmatter 07 mcpvault → safe vault access with a read-only mode, and Obsidian doesn’t even need to be running 08 obsidian-claude-code-mcp → connect Claude Code to your open vault with one /ide command 09 obsidian-web-mcp → reach your vault from your phone or any MCP client, with OAuth and a Cloudflare Tunnel 10 obsidian-mcp → a git-backed vault with 18 tools, running locally or on AWS Lambda Nobody is going to build your second brain for you, and every chat you close without one is knowledge thrown away. Bookmark this, pick one repo from 01 to 05 and ingest your first source tonight. A month from now you have a wiki, and everyone who skipped it is still opening a blank chat.

Ryven

10,722 次观看 • 7 天前