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

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

На главную

Made an updated version this weekend Here's how you do it (raw notes) > Grab Andrej Karpathy's latest gist (in the first comment) > Download Peter Steinberger 🦞 summarize CLI > Download yt-dlp > Download obsidian > Download tobi lutke qmd --> Setup a node or Golang CLI called...

599,043 просмотров • 5 месяцев назад •via X (Twitter)

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

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

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

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇

YanXbt

34,987 просмотров • 2 месяцев назад

I stack Hermes agents with OpenClaw for financial research, and the results should be illegal. I track every politician, insider trader, and I know EXACTLY what moves they're making. If you can't beat them, join them. The exact playbook for printing money from insider trading (copy me): Requirements: • OpenClaw setup • Hermes Agent setup Step 1. Define your research thesis Before you send any prompts to either tool, you'll need to clarify exactly what you're trying to research. This could be: a specific industry, asset class, market sector, and so on. Examples: • Tracking smart money buys in the semiconductor industry • Tracking smart money buys in crypto • Tracking a specific politician and where they're bidding (like Nancy Pelosi) Step 2. Deploy Hermes agents to track the smart money (in parallel) Hermes is your data layer. Spin up 5 agents at the same time, each with one job: Agent 1: Track every politician's disclosed trades from the last 30 days (House and Senate stock disclosures) Agent 2: Pull insider transactions (Form 4 filings, CEO/CFO buys and sells) Agent 3: Scrape X sentiment from top 50 accounts on the topic Agent 4: Pull on-chain data (whale wallets, TVL, exchange flows) *if applicable* Agent 5: Monitor news, regulatory filings, and announcements from the last 30 days Each agent runs independently. You're not waiting for one to finish before the next starts. Step 3. Consolidate the output Once your Hermes agents finish, dump every output into a single document. (don't filter or summarize) - you want OpenClaw to see the raw data. Step 4. Feed it all into OpenClaw Open OpenClaw and paste the consolidated research file with this prompt: "Act as an elite macro analyst. Below is raw data gathered from multiple sources on [thesis], including politician disclosures and insider transactions. Synthesize the findings, identify the strongest signals and contradictions, flag any unusual smart-money activity, and give me a clear directional view with conviction levels. Flag any data gaps that need follow-up." OpenClaw will go deep, run its own reasoning chain, and produce a synthesized report. Done. Now you're literally tapping into the financial data they don't want you to see (it's all public - you just had to find it). Make sure to save this playbook so you don't lose it!

Miles Deutscher

19,955 просмотров • 4 месяцев назад

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

Avi Chawla

30,932 просмотров • 9 месяцев назад

your AI agent can watch any video now - paste a URL and it sees every frame, hears every word, all for free 🤯 bradautomates/claude-video gives Claude the ability to watch YouTube, Loom, TikTok, local files - anything yt-dlp supports what people actually use it for: → analyze a competitor launch - what hook, what visuals, what structure → debug from a screen recording - Claude reads the exact frame where it breaks → summarize a 49-min talk in 30 seconds with frame-accurate timestamps → strip the hype from product videos - "what's actually new, skip the pitch" the mechanism: yt-dlp pulls free captions first (zero cost). ffmpeg extracts frames at scene-aware intervals - not uniform sampling, so you don't waste tokens on 12 identical frames of the same slide. Claude reads every frame as an image with timestamp markers. Groq Whisper only kicks in when a video has no caption track how to set up (3 min): > claude code: /plugin marketplace add bradautomates/claude-video then /plugin install watch@claude-video > or npx skills add bradautomates/claude-video -g for codex, cursor, gemini cli > dependencies auto-install on macOS via brew two caveats: free captions cover most but not all videos. past 10 min use --start/--end for focused sections or the token-burner mode for full coverage your buddy still watches every tutorial at 2x speed taking manual notes. you paste a URL and your agent extracts the substance in seconds for $0

Alvaro Cintas

308,334 просмотров • 1 месяц назад

I just built a Claude Cowork skill that turns your Google Ads data into a visual performance dashboard in 60 seconds 🤯 One prompt → campaign breakdowns, CPA trends, spend vs conversions charts, and hourly conversion patterns, all rendered as an interactive HTML dashboard you open in Chrome. All inside Claude Cowork. Perfect for DTC brands and agencies who are pulling Google Ads data into spreadsheets every week, manually building charts, and spending an hour formatting a report that's outdated by the time you send it. If you're managing Google Ads and your weekly reporting workflow looks like this — export a CSV, open Google Sheets, build a pivot table, copy the numbers into a slide deck, manually create charts, format everything, realize you forgot a campaign, start over ... This skill does the whole thing in one prompt: → Connects to your live Google Ads data via MCP → Pulls spend, conversions, CPA, ROAS, CTR across every campaign → Builds an interactive HTML dashboard → Summary cards at the top: total spend, total conversions, avg CPA, avg ROAS → Bar chart comparing spend vs conversions by campaign → CPA trend line over the last 30 days → Campaign table ranked by performance, color-coded green/yellow/red → Opens in Chrome: hover over charts, compare campaigns, screenshot for your team No spreadsheets. No manual chart building. No hour-long formatting sessions. What you get: → A visual dashboard from live data in under 60 seconds → Campaign performance you can actually see, not just read in a table → CPA trends that show you where things are heading, not just where they are → A dashboard you can screenshot and drop into Slack, a client report, or a team standup → Reusable — run it weekly and the data updates automatically One prompt. Live data. A finished dashboard you open in your browser. I put together a playbook with the full skill file, the setup, and the exact prompts to customize the dashboard for your account. Want it for free? > Like this post > Comment "DASH" And I'll send it over (must be following so I can DM)

Mike Futia

38,936 просмотров • 5 месяцев назад