Загрузка видео...

Не удалось загрузить видео

На главную

with only a couple of prompts, Gemini CLI can convert a messy folder containing hundreds of notes into a neatly named, well-structured, cross-linked Obsidian knowledge graph all in about half an hour and at minimal cost. from r/singularity/Ryoiki-Tokuiten

415,737 просмотров • 1 год назад •via X (Twitter)

Комментарии: 10

Фото профиля Rohan Paul
Rohan Paul1 год назад

OP first saved all his notes—about 400 markdown files—from another app onto his computer. He put these files into an Obsidian folder. Next, he opened Gemini’s CLI tool and typed two short instructions: one told Gemini to rename and neatly sort every note into folders, and the other told it to link related notes so Obsidian’s graph view would show the connections. Gemini ran for ~30mins, used only a small part of its memory window, and finished with most notes correctly organized and cross-linked

Фото профиля Pale Blue Mediocrity
Pale Blue Mediocrity1 год назад

I've seen so many of these demoes over the past DECADES, yet not a single time I've seen a person actually doing something with this "generated PKM knowledge graph". I've seen plenty of manually structured notes which are always used like second nature. Just an observation.

Фото профиля ⓧaugmntd 🛞 Xakubio
ⓧaugmntd 🛞 Xakubio1 год назад

sheesh

Фото профиля Kayli Lewis
Kayli Lewis1 год назад

🧐

Фото профиля Yinan (Steven) Na
Yinan (Steven) Na1 год назад

Thank you for this Rohan

Фото профиля Rohan Paul
Rohan Paul1 год назад

👊👊🙏

Фото профиля Danny Sun
Danny Sun1 год назад

why a cli text interface? c64 vibes.

Фото профиля alby13
alby131 год назад

Great visual!

Фото профиля Richand Handsome
Richand Handsome1 год назад

Thought it was free

Фото профиля Rohan Paul
Rohan Paul1 год назад

Gemini CLI itself is a free, open-source tool, and and you get up to 1000 model requests a day (60 per minute i think.) But beyond this limit, when the CLI tool talks to the paid Gemini API or to Vertex AI keys, that will be billed by the million tokens normally.

Похожие видео

Obsidian just became the most dangerous folder on your computer, and Andrej Karpathy predicted it with 1 markdown file. His method is called append-and-review. He described it years ago and almost nobody listened: 1 single note, every thought appended to the top, reviewed on random scrolls. No tags, no folders, no Notion dashboards with 40 linked databases. The problem was always the same the note remembers, but it can't act. That changed the moment people pointed Claude Code at an Obsidian vault. Here's the setup that's quietly spreading: Part 1 — The vault becomes a database. Obsidian stores everything as plain markdown on your disk, which means Claude Code can read it like a codebase. You open a terminal inside the vault folder and your 2,000 notes turn into queryable memory. Part 2 — The CLAUDEmd file becomes the brain stem. One file at the root tells the agent who you are, what you're building, and how your notes are structured. From that point every session starts with full context instead of a blank chat window. Part 3 — Karpathy append log becomes fuel. You dump raw thoughts all day ideas, links, half-sentences. Then 1 command at night: review today's appends, extract action items, draft the 3 posts hiding in there, link them to existing notes. The messy log goes in, structured output comes out, and the vault rewrites itself while you sleep. Part 4 — Agents start living in your notes. People are running weekly reviews, content calendars, even market research as scheduled Claude Code runs over their vault. Your second brain stops being a graveyard of highlights and starts shipping. The honest math: setup takes about 90 minutes, the first week feels like overkill, and by day 30 you're sitting on a system where every note you've written in 5 years is working for you instead of rotting in a folder. Notion needed a server, a subscription and your data on someone else's machine. Obsidian needed a text file and now the text file has an employee.

Spike 1%

58,428 просмотров • 28 дней назад

Build better RAG by letting a team of agents extract and connect your reference materials into a knowledge graph. Our new short course, “Agentic Knowledge Graph Construction,” taught by Neo4j Innovation Lead Andreas Kollegger, shows you how. Knowledge graphs are an important way to store information accurately but they are a lot of work to build manually. In this course you’ll learn how to build a team of agents that turn data– in this case product reviews and invoices from suppliers–into structured graphs of entities and relationships for RAG. Learn how agents can automatically handle the time-consuming work of building graphs — extracting entities and relationships (e.g., Product "contains" Assembly, Part "supplied_by" Supplier, Customer review "mentions" Product), deduplicating them, fact-checking them, and committing them to a graph database — so your retrieval system can find right information to generate accurate output. For example, you can use agents to help trace customer complaints directly to specific suppliers, manufacturing processes, and product hierarchies, thus turning fragmented information into queryable business intelligence. Skills you’ll gain: - Build, store, and access knowledge graphs using the Neo4j graph database - Build multi-agent systems using Google’s Agent Development Kit (ADK) - Set up a loop of agentic workflows to propose and refine a graph schema through fact-checking - Connect agent-generated graphs of unstructured and structured data into a unified knowledge graph This course gets into the practicum of why knowledge graphs give more accurate information retrieval than vector search alone, especially for high-stakes applications where precision matters more than fuzzy similarity matching. Sign up here:

Andrew Ng

168,153 просмотров • 11 месяцев назад