Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

I built a Claude Code skill that allows it to generate a deep research report over any collection of complex docs (PDFs, Word, Pptx)….and generate word-level citations and bounding boxes directly back to the source! 📝 Check out “/research-docs”. 1. It parses out text and bounding boxes from every...

77,259 görüntüleme • 3 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Two big steps towards our vision for NotebookLM as the ultimate research platform: • Integrating Deep Research, with a set of only-at-Notebook features that let you explore the retrieved sources • Launching a series of Featured Notebooks curated by Google Research These developments are designed to enhance the full life cycle of research and scholarship: using the power of AI to assemble the knowledge base you need to advance your understanding, and then making your work accessible and intelligible to a wider audience using all the explanatory tools that Notebook offers. If you've used DeepResearch in the Gemini app, you already know that it's a pioneering advance in assembling complex, grounded information on any topic imaginable—collecting an entire trove of material for you and writing a nuanced research report that summarizes the findings. But because NotebookLM is designed to manage and explore potentially hundreds of sources, the Deep Research report is only the beginning of your journey. In our integration, Deep Research gives you an overview all of the sources it found during its research phase, with annotated commentary explaining how each source related to your original query. You can then choose to import some or all of the sources to the notebook, along with the report itself, which you can then explore or transform using the full suite of tools that Notebook offers: grounded chat with citations, Mind Maps, Audio/Video overviews, and much more. And it's that suite of tools that make the Google Research Featured Notebooks so compelling as well. Each notebook contains a curated collection of articles on a specific topic, published by the Google Research team. Think of them as a kind of knowledge base of Google's best thinking on a series of compelling research questions: How do scientists link genetics to health? How will quantum computing be useful? If you're a specialist in these fields, you can read the original papers or ask nuanced questions in chat and advance your understanding of the latest developments. But these notebooks can also make the complex but important topics understandable to non-specialists or students. Each notebook comes with pre-generated audio and video overviews, flashcards, and other Studio artifacts designed to make the scientific and technological concepts accessible and interesting. And you can always explore the material with our new "Learning Guide" chat mode that effectively gives you a personal tutor to enhance your understanding. There's much more to come on this front, but you can see in these two announcements how we see Notebook as both a workbench for conducting research and a publishing platform for sharing the results of that research once you're ready to make it public. Deep Research is rolling out this week to all users. The first two Google Research notebooks are live now, both of them deep dives into our most recent discoveries involving genetics and health. (Links in the following tweets.) We'll be publishing new notebooks in the series every other week or so for the next few months.

Steven Johnson

104,814 görüntüleme • 8 ay önce

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

55,345 görüntüleme • 1 ay önce

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

Nityesh

68,221 görüntüleme • 23 gün önce