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

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

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

Dynamic workflows are a generalization of harnesses, automations, loops, routing, and graphs. It's the most powerful feature I have built into my agent orchestrator. Supports all kinds of patterns that leverage different agent backends (claude, codex, pi, hermes,...). It's a meta-harness approach that unlocks new forms of test-time compute.... Example of use cases it supports: > LLM councils to get different perspectives from LLMs or plan more intensively > Dynamically routing tasks to different agents based on needs (e.g., cost efficiency and optimal intelligence) > Advisor/Judge + executor workflows and pretty much any complex graph-based pattern required by the task. I find it especially useful for long-running work and code reviewing. > Agent teams that talk to each other if needed for the task. I like to use this for AI editing, artifact creation, and other creative tasks. And I am sure it supports so many things that I haven't discovered yet. I got inspired by the dynamic workflow feature released by the Claude Code team. I had actually built it earlier this year but wanted to generalize it across different agent backends. I think this is going to become more popular in the coming days. I will share more of my findings soon.show more

elvis

312,132 subscribers

27,377 просмотров • 1 день назад •via X (Twitter)

Наука и технологии Образование

Anya Rossi• Live Now

Private livecam show

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

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

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

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

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

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

I just built my own wiki generator plugin for my agents. My agents can now generate wikis for anything I ask. One of my favorite wikis is called PaperWiki. This is a great example of what Andrej Karpathy describes. It uses obsidian vaults to organize papers, retrieve LLM-generated summaries, diagrams, and other advanced views for paper exploration. When Obsidian UI is not enough, I use my own artifact generator inside my agent orchestrator (see clip for example). This allows my agents to build any kind of view or exploration feature that I need. The papers are all curated with automations and several rules/patterns I have manually built over the years. On the surface, this looks basic. But behind the scenes, there are advanced search capabilities, connections, metadata, derived data, and other interesting bits of information that are extremely useful for my research agents. This is mostly built for agents. The artifact preview is just a high-level way to validate and quickly assess the quality of the wiki, suggest improvements, and it's also great for research. I use tobi lutke's qmd for all search capabilities. Everything is markdown. The summaries and even the diagrams. The wiki updates on its own based on several automations I have optimized over the past couple of weeks. The wiki grows and self-improves based on several requirements important for my research use cases. This is as personalized as it gets. There is nothing like it out there. And I use my research expertise to continue improving it over time. This is a vanilla wiki. There are so many things I want to build on top of this. Different aggregations, views, artifacts, etc. All to help automate more of my research work and accelerate productivity. I think the biggest leverage here is how powerful this could be for discovery and experimentation. One of my goals is to use it to find deeper connections and insights that would otherwise elude the top human researchers and use those to generate interesting new hypotheses and research experiments. That way, my agents can use autoresearch to explore research ideas at the frontier. Stay tuned for more.

I just built my own wiki generator plugin for my agents. My agents can now generate wikis for anything I ask. One of my favorite wikis is called PaperWiki. This is a great example of what Andrej Karpathy describes. It uses obsidian vaults to organize papers, retrieve LLM-generated summaries, diagrams, and other advanced views for paper exploration. When Obsidian UI is not enough, I use my own artifact generator inside my agent orchestrator (see clip for example). This allows my agents to build any kind of view or exploration feature that I need. The papers are all curated with automations and several rules/patterns I have manually built over the years. On the surface, this looks basic. But behind the scenes, there are advanced search capabilities, connections, metadata, derived data, and other interesting bits of information that are extremely useful for my research agents. This is mostly built for agents. The artifact preview is just a high-level way to validate and quickly assess the quality of the wiki, suggest improvements, and it's also great for research. I use tobi lutke's qmd for all search capabilities. Everything is markdown. The summaries and even the diagrams. The wiki updates on its own based on several automations I have optimized over the past couple of weeks. The wiki grows and self-improves based on several requirements important for my research use cases. This is as personalized as it gets. There is nothing like it out there. And I use my research expertise to continue improving it over time. This is a vanilla wiki. There are so many things I want to build on top of this. Different aggregations, views, artifacts, etc. All to help automate more of my research work and accelerate productivity. I think the biggest leverage here is how powerful this could be for discovery and experimentation. One of my goals is to use it to find deeper connections and insights that would otherwise elude the top human researchers and use those to generate interesting new hypotheses and research experiments. That way, my agents can use autoresearch to explore research ideas at the frontier. Stay tuned for more.

elvis

66,903 просмотров • 3 месяцев назад

LLM Knowledge Base → Slides When Andrej Karpathy shared his LLM Knowledge Base setup, many were wondering how to generate more visual forms of the wiki. There are many options, but I think Gamma is one of the best at producing high-quality, rich presentations. To showcase this, I just built a pipeline that turns my AI papers wiki (1K+ papers across 20 AI agent topics) into polished slide presentations using Gamma. The flow: Obsidian vault → Gamma MCP → embedded preview in my dashboard. I give one command to my agent, which pulls the top papers from each topic (via the wiki), feeds them to Gamma, and renders the presentation inline. The Gamma connector for Claude is a great choice for generating beautiful and professional slides. Easy to use. Go to your Claude instance and add the official Gamma connector. That's it! Claude Code will now have access to all the necessary MCP tools for generating slides. I use the Claude Agent SDK for my agent orchestrator, so I use the official Gamma MCP tools and embed the generated slides in an iframe via my artifact preview. See the clip below for an example.

LLM Knowledge Base → Slides When Andrej Karpathy shared his LLM Knowledge Base setup, many were wondering how to generate more visual forms of the wiki. There are many options, but I think Gamma is one of the best at producing high-quality, rich presentations. To showcase this, I just built a pipeline that turns my AI papers wiki (1K+ papers across 20 AI agent topics) into polished slide presentations using Gamma. The flow: Obsidian vault → Gamma MCP → embedded preview in my dashboard. I give one command to my agent, which pulls the top papers from each topic (via the wiki), feeds them to Gamma, and renders the presentation inline. The Gamma connector for Claude is a great choice for generating beautiful and professional slides. Easy to use. Go to your Claude instance and add the official Gamma connector. That's it! Claude Code will now have access to all the necessary MCP tools for generating slides. I use the Claude Agent SDK for my agent orchestrator, so I use the official Gamma MCP tools and embed the generated slides in an iframe via my artifact preview. See the clip below for an example.

elvis

47,204 просмотров • 3 месяцев назад

Building a personal knowledge base for my agents is increasingly where I spend my time these days. Like Andrej Karpathy, I also use Obsidian for my MD vaults. What's different in my approach is that I curate research papers on a daily basis and have actually tuned a Skill for months to find high-signal, relevant papers. I was reviewing and curating papers manually for some time, but now it's all automated as it has gotten so good at capturing what I consider the best of the best. There are so many papers these days, so this is a big deal. You all get to benefit from that with the papers I feature in my timeline and on DAIR.AI. The papers are indexed using tobi lutke qmd cli tool (all of it in markdown files along with useful metadata). So good for semantic search and surfacing insights, unlike anything out there. I am a visual person, so I then started to experiment with how to leverage this personal knowledge base of research papers inside my new interactive artifact generator (mcp tools inside my agent orchestrator system). The result is what you see in the clip. 100s of papers with all sorts of insights visualized. I keep track of research papers daily, so believe me when I tell you that this system is absolutely insane at surfacing insights. This is the result of months of tinkering on how to index research and leverage agent automations for wikification and robust documentation. But this is just the beginning. The visual artifact (which is interactive too) can be changed dynamically as I please. I can prompt my agent to throw any data at it. I can add different views to the data. Different interactions. I feel like this is the most personalized research system I have ever built and used, and it's not even close. The knowledge that the agents are able to surface from this basic setup is already extremely useful as I experiment with new agentic engineering concepts. I feel like this knowledge layer and the higher-level ones I am working on will allow me to maximize other automation tools like autoresearch. The research is only as good as the research questions. And the research questions are only as good as the insights the agents have access to. Where I am spending time now is on how to make this more actionable. I am obsessed about the search problem here. The automations, autoresearch, ralph research loop (I built one months ago) are easier to build but are only as good as what you feed them. Work in progress. More updates soon. Back to building.

Building a personal knowledge base for my agents is increasingly where I spend my time these days. Like Andrej Karpathy, I also use Obsidian for my MD vaults. What's different in my approach is that I curate research papers on a daily basis and have actually tuned a Skill for months to find high-signal, relevant papers. I was reviewing and curating papers manually for some time, but now it's all automated as it has gotten so good at capturing what I consider the best of the best. There are so many papers these days, so this is a big deal. You all get to benefit from that with the papers I feature in my timeline and on DAIR.AI. The papers are indexed using tobi lutke qmd cli tool (all of it in markdown files along with useful metadata). So good for semantic search and surfacing insights, unlike anything out there. I am a visual person, so I then started to experiment with how to leverage this personal knowledge base of research papers inside my new interactive artifact generator (mcp tools inside my agent orchestrator system). The result is what you see in the clip. 100s of papers with all sorts of insights visualized. I keep track of research papers daily, so believe me when I tell you that this system is absolutely insane at surfacing insights. This is the result of months of tinkering on how to index research and leverage agent automations for wikification and robust documentation. But this is just the beginning. The visual artifact (which is interactive too) can be changed dynamically as I please. I can prompt my agent to throw any data at it. I can add different views to the data. Different interactions. I feel like this is the most personalized research system I have ever built and used, and it's not even close. The knowledge that the agents are able to surface from this basic setup is already extremely useful as I experiment with new agentic engineering concepts. I feel like this knowledge layer and the higher-level ones I am working on will allow me to maximize other automation tools like autoresearch. The research is only as good as the research questions. And the research questions are only as good as the insights the agents have access to. Where I am spending time now is on how to make this more actionable. I am obsessed about the search problem here. The automations, autoresearch, ralph research loop (I built one months ago) are easier to build but are only as good as what you feed them. Work in progress. More updates soon. Back to building.

elvis

464,399 просмотров • 3 месяцев назад

Increasingly, HTML Artifacts are becoming a core part of how I work with AI agents. Long-horizon agent sessions need a better way to surface insights about what work it has done. This may not be obvious right now, but as you start to let your agent work on dynamic workflows, large codebases, long-running loops (e.g., using /goal), and deep research tasks, you need a good way to present results. Chat window is not it. You also don't want to just trust everything the agents do. Artifacts help provide an important verification layer, which in turn enables important decision-making. I like HTML artifacts because I can just ask the agent to produce as many of them (and in whatever form) as I need to verify the work and make sense out of everything. I even built a nice tab system for my artifacts. They are great for continual learning and research. I use HTML artifacts for logging, tracking experiments, brainstorming, managing my inbox, code reviews, agent session management, deep research, writing, reading, and so much more. I believe Andrej Karpathy wrote about this somewhere: As we move on to more advanced applications of AI agents and outputs get more complex, we will start to find the need for even more advanced forms of interactions with AI, including interactive neural videos/simulations.

Increasingly, HTML Artifacts are becoming a core part of how I work with AI agents. Long-horizon agent sessions need a better way to surface insights about what work it has done. This may not be obvious right now, but as you start to let your agent work on dynamic workflows, large codebases, long-running loops (e.g., using /goal), and deep research tasks, you need a good way to present results. Chat window is not it. You also don't want to just trust everything the agents do. Artifacts help provide an important verification layer, which in turn enables important decision-making. I like HTML artifacts because I can just ask the agent to produce as many of them (and in whatever form) as I need to verify the work and make sense out of everything. I even built a nice tab system for my artifacts. They are great for continual learning and research. I use HTML artifacts for logging, tracking experiments, brainstorming, managing my inbox, code reviews, agent session management, deep research, writing, reading, and so much more. I believe Andrej Karpathy wrote about this somewhere: As we move on to more advanced applications of AI agents and outputs get more complex, we will start to find the need for even more advanced forms of interactions with AI, including interactive neural videos/simulations.

elvis

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

We (Claude and I) made a new package: voxmlx It's an MLX implementation of Mistral's Voxtral mini realtime speech recognition model. It supports streaming audio and runs pretty fast on a laptop. To use it, simply: `uvx voxmlx` Also I did not write a single line of code for this package. Every line of code was written by Claude Code. More on that in thread.

We (Claude and I) made a new package: voxmlx It's an MLX implementation of Mistral's Voxtral mini realtime speech recognition model. It supports streaming audio and runs pretty fast on a laptop. To use it, simply: `uvx voxmlx` Also I did not write a single line of code for this package. Every line of code was written by Claude Code. More on that in thread.

Awni Hannun

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

Claude Code Desktop now opens a new window for each session This makes it much easier to visualize multiple Claude Code agents running in parallel My current stack depends on the task: - Ghostty: when starting a project. Bash commands, git, env variables, provider connections. All manual through the terminal with a Claude panel running alongside. - Claude Code Desktop: once everything is configured. GitHub connected, CLAUDE.md, Skills, subagents and Hooks ready. Claude Code runs on its own, no more terminal setup, just panels running and outputs to review. - VSCode: when I need to review code by hand. I use it less and less, but there are moments where I have to confirm Claude got it right. I usually open the Claude extension inside VSCode, but it lacks most of the CLI features so it's limited Solid update. Worth trying once your workflows are already set up 👇

Claude Code Desktop now opens a new window for each session This makes it much easier to visualize multiple Claude Code agents running in parallel My current stack depends on the task: - Ghostty: when starting a project. Bash commands, git, env variables, provider connections. All manual through the terminal with a Claude panel running alongside. - Claude Code Desktop: once everything is configured. GitHub connected, CLAUDE.md, Skills, subagents and Hooks ready. Claude Code runs on its own, no more terminal setup, just panels running and outputs to review. - VSCode: when I need to review code by hand. I use it less and less, but there are moments where I have to confirm Claude got it right. I usually open the Claude extension inside VSCode, but it lacks most of the CLI features so it's limited Solid update. Worth trying once your workflows are already set up 👇

Daniel San

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

New library almost done, can't wait to fill it with all my books 🥰 I've designed and built lots furniture in the past but this has been the most complex and challenging by far. In the past I have mostly worked with plywood. For this project I wanted to build out of solid oak and use Japanese joinery techniques. I don't have time to fabricate complex projects these days, and I wasn't confident enough in my woodworking skills. So I collaborated with a local carpenter. This allowed for so many more interesting design details that I wouldn't have thought of myself. Whatever your furniture needs are, consider being a patron of your local carpenters, cabinetmakers, and woodworkers. Yes it's slower and more expensive than going to IKEA but the process is much more rewarding, and the results will be more unique and long lasting.

New library almost done, can't wait to fill it with all my books 🥰 I've designed and built lots furniture in the past but this has been the most complex and challenging by far. In the past I have mostly worked with plywood. For this project I wanted to build out of solid oak and use Japanese joinery techniques. I don't have time to fabricate complex projects these days, and I wasn't confident enough in my woodworking skills. So I collaborated with a local carpenter. This allowed for so many more interesting design details that I wouldn't have thought of myself. Whatever your furniture needs are, consider being a patron of your local carpenters, cabinetmakers, and woodworkers. Yes it's slower and more expensive than going to IKEA but the process is much more rewarding, and the results will be more unique and long lasting.

kepano

303,252 просмотров • 2 лет назад

warp code feels like a combination of a cli agent and cursor-style ux design it's a cli that looks like an ide because it gives you: - editor code view - project explorer - one-click to view command output - switch between agent/cli - context/credit spend tracking - task lists - shared context with warp drive there is a learning curve because it's a different workflow, but the agent was top of terminal bench until recently and i can see why would love to see them add: - subagents - an agent sdk - sidebar fonts increasing with cmd +/- not being paid to post this, btw (feel like i have to add that these days 😉) i have been using warp for a long while as a terminal and sometimes agent on the $15/mo plan

warp code feels like a combination of a cli agent and cursor-style ux design it's a cli that looks like an ide because it gives you: - editor code view - project explorer - one-click to view command output - switch between agent/cli - context/credit spend tracking - task lists - shared context with warp drive there is a learning curve because it's a different workflow, but the agent was top of terminal bench until recently and i can see why would love to see them add: - subagents - an agent sdk - sidebar fonts increasing with cmd +/- not being paid to post this, btw (feel like i have to add that these days 😉) i have been using warp for a long while as a terminal and sometimes agent on the $15/mo plan

Ian Nuttall

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

BREAKING: OpenAI just launched ChatGPT Agent It allows ChatGPT to think, plan, and execute complex tasks on its own virtual computer while you do other things I had early access, and ChatGPT Agent built me a complete early retirement plan in 20 minutes: > Found local tax laws (Vancouver) > Analyzed average monthly spend rates > Calculated savings needed to retire at 30 > Researched optimal investment allocations > Found tax optimization strategies I'd never heard of > Built multiple FIRE scenarios > Created a downloadable presentation with results This would've cost me $5,000+ from a financial advisor and taken weeks I think with ChatGPT Agent now, and especially as it gains access to more tools, we're finally going to see the rise of a new AI skill category in *Agent Management* Agents are finally becoming capable of doing real work autonomously, so anyone who learns how to effectively orchestrate agents will have a huge advantage

BREAKING: OpenAI just launched ChatGPT Agent It allows ChatGPT to think, plan, and execute complex tasks on its own virtual computer while you do other things I had early access, and ChatGPT Agent built me a complete early retirement plan in 20 minutes: > Found local tax laws (Vancouver) > Analyzed average monthly spend rates > Calculated savings needed to retire at 30 > Researched optimal investment allocations > Found tax optimization strategies I'd never heard of > Built multiple FIRE scenarios > Created a downloadable presentation with results This would've cost me $5,000+ from a financial advisor and taken weeks I think with ChatGPT Agent now, and especially as it gains access to more tools, we're finally going to see the rise of a new AI skill category in Agent Management Agents are finally becoming capable of doing real work autonomously, so anyone who learns how to effectively orchestrate agents will have a huge advantage

Rowan Cheung

653,805 просмотров • 1 год назад

Claude Code Agent Teams are f*cking ridiculous 🤯 One prompt → a team lead breaks your project into pieces, spins up multiple AI agents, and they all work on different parts simultaneously. Research, builds, reviews, and debugging: all happening at the same time. All inside Claude Code. If you're running complex projects where every step waits on the last one... Agent teams eliminate the entire bottleneck: → Tell Claude what you need and describe the team structure in plain English → A lead agent breaks the work into a shared task list → It spawns 3-5 teammates — each with their own context and workspace → Teammates research, build, test, and review in parallel → They message each other, share findings, and challenge each other's work → The lead synthesizes everything into a finished deliverable No managing agents yourself. No waiting for step 1 to finish before step 2 starts. No single-lens reviews that miss half the issues. What you get: → Competitive research across 5 brands done in minutes instead of hours → Multi-component builds where frontend, backend, and data layers happen simultaneously → Creative reviews from 3 different angles at once — brand voice, conversion, differentiation → Funnel debugging where 4 agents investigate 4 theories and debate until they find the real answer Built 100% in Claude Code with one settings change. I put together a full DTC playbook: 5 workflows with copy-paste prompts, the exact setup process, token management tips, and honest guidance on when agent teams are worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)

Mike Futia

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

New feature in Claude Code 2.1.14 just dropped! You can now search and install plugins from the marketplaces installed in your current Claude Code session. This is huge if you’re building plugins on top of Claude Code’s marketplace layer (Skills, Agents, Hooks, etc). How it works: - Run /plugin - The official Claude marketplace is installed by default - Use the search bar to find the plugin you want - Select one or multiple plugins with space, then press i to install - Go to the Installed tab to browse and enable them With the exponential growth of Skills and Agent-based components running in the CLI, improving plugin discoverability is a big win. Pretty sure more marketplace-related features are coming

New feature in Claude Code 2.1.14 just dropped! You can now search and install plugins from the marketplaces installed in your current Claude Code session. This is huge if you’re building plugins on top of Claude Code’s marketplace layer (Skills, Agents, Hooks, etc). How it works: - Run /plugin - The official Claude marketplace is installed by default - Use the search bar to find the plugin you want - Select one or multiple plugins with space, then press i to install - Go to the Installed tab to browse and enable them With the exponential growth of Skills and Agent-based components running in the CLI, improving plugin discoverability is a big win. Pretty sure more marketplace-related features are coming

Daniel San

40,994 просмотров • 6 месяцев назад

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

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

LLM Artifacts Connected to Andrej Karpathy's LLM Knowledge base idea, I've been building out a fun way to generate dynamic artifacts from these knowledge bases with the goal of discovering and revealing meaningful and deeper insights. LLM KBs are hard to consume for humans, as I think they are more built for agents. So the question is, what form would be useful for humans to take actions and make important decisions? That's what I am trying to figure out with these artifacts. The artifact example shows a pulse on HN discussions around AI-related stories. The insights can go deeper, of course, but this is already super fun and thought-provoking, like some of my favorite podcasts. The format and depth matter a lot. The aggregation skills of agents are outstanding if you tune the prompts and skill carefully. I built this artifact generator in a few minutes through an agent skill, but I feel like there are so many ways that LLM-generated information can be used and consumed. Like generating deeper insights and analysis, and things that are just not feasible for humans today. The generated artifact (including its data and design) serves as reusable templates or can be updated in real-time via auomations, which is something I am also working on. It is truly an insane way to monitor and track information. Better than a newsletter. Better than newspapers. There is something about this that gets me really excited about the future of AI agents for knowledge generation and discovery. Lots of hidden gems everywhere just waiting to be discovered and acted on if the information is presented correctly. This is not perfect. The format, style/prose can be improved, but this is easy to customize via skill. You can personalize it to your liking. I feel like these dynamic artifacts are going to emerge as a strong new medium to stay on the cutting edge of things, both for agents and humans. My target is research, of course. This was just a basic example. Besides animation, I am also targeting other components like voice, videos, images, slides, etc. This space is full of opportunities to explore. Skill for this coming soon.

LLM Artifacts Connected to Andrej Karpathy's LLM Knowledge base idea, I've been building out a fun way to generate dynamic artifacts from these knowledge bases with the goal of discovering and revealing meaningful and deeper insights. LLM KBs are hard to consume for humans, as I think they are more built for agents. So the question is, what form would be useful for humans to take actions and make important decisions? That's what I am trying to figure out with these artifacts. The artifact example shows a pulse on HN discussions around AI-related stories. The insights can go deeper, of course, but this is already super fun and thought-provoking, like some of my favorite podcasts. The format and depth matter a lot. The aggregation skills of agents are outstanding if you tune the prompts and skill carefully. I built this artifact generator in a few minutes through an agent skill, but I feel like there are so many ways that LLM-generated information can be used and consumed. Like generating deeper insights and analysis, and things that are just not feasible for humans today. The generated artifact (including its data and design) serves as reusable templates or can be updated in real-time via auomations, which is something I am also working on. It is truly an insane way to monitor and track information. Better than a newsletter. Better than newspapers. There is something about this that gets me really excited about the future of AI agents for knowledge generation and discovery. Lots of hidden gems everywhere just waiting to be discovered and acted on if the information is presented correctly. This is not perfect. The format, style/prose can be improved, but this is easy to customize via skill. You can personalize it to your liking. I feel like these dynamic artifacts are going to emerge as a strong new medium to stay on the cutting edge of things, both for agents and humans. My target is research, of course. This was just a basic example. Besides animation, I am also targeting other components like voice, videos, images, slides, etc. This space is full of opportunities to explore. Skill for this coming soon.

elvis

31,213 просмотров • 3 месяцев назад

Dexter vs. Claude Code I ran tests overnight and Dexter came out ahead on complex financial tasks that required deep research. Dexter won on: • speed (by 92%) • cost (by 26%) • correctness (by 31%) I use Claude Code often, so this was fun to see. A key challenge for CC is that it relies on web search for financial data. Most of what it finds comes from news sites, blogs, and other secondary sources. Dexter uses primary source data from Financial Datasets, so the performance gap makes sense. Plenty of room to improve on Dexter. The gap will only grow from here. Evals from vals. Report coming next.

Dexter vs. Claude Code I ran tests overnight and Dexter came out ahead on complex financial tasks that required deep research. Dexter won on: • speed (by 92%) • cost (by 26%) • correctness (by 31%) I use Claude Code often, so this was fun to see. A key challenge for CC is that it relies on web search for financial data. Most of what it finds comes from news sites, blogs, and other secondary sources. Dexter uses primary source data from Financial Datasets, so the performance gap makes sense. Plenty of room to improve on Dexter. The gap will only grow from here. Evals from vals. Report coming next.

virat

26,638 просмотров • 7 месяцев назад

We are entering an extremely exciting era for open-weight models. Kimi K2.6 now feels like a top agentic model. I took it for a spin via Fireworks AI fast inference APIs. Kimi K2.6 has impressive agentic capabilities, design skills, and the ability to synthesize large amounts of information. I built a little Skill that produces survey papers on any AI research topic you want. (see example in the clip) You can use the skill to tell your agent to generate a survey on whatever topic and watch it go to work. The artifact was fully generated by Kimi.ai's Kimi K2.6. It's cheap and fast. Next step for me is to explore ways to continue integrating the capabilities of these models on use cases like automating my LLM knowledge bases and augmenting my agent memory capabilities. Stay tuned for more.

We are entering an extremely exciting era for open-weight models. Kimi K2.6 now feels like a top agentic model. I took it for a spin via Fireworks AI fast inference APIs. Kimi K2.6 has impressive agentic capabilities, design skills, and the ability to synthesize large amounts of information. I built a little Skill that produces survey papers on any AI research topic you want. (see example in the clip) You can use the skill to tell your agent to generate a survey on whatever topic and watch it go to work. The artifact was fully generated by Kimi.ai's Kimi K2.6. It's cheap and fast. Next step for me is to explore ways to continue integrating the capabilities of these models on use cases like automating my LLM knowledge bases and augmenting my agent memory capabilities. Stay tuned for more.

elvis

47,678 просмотров • 3 месяцев назад

I'm going to quit my job to dedicate myself 100% to Claude. I asked it to do this: Analyze undervalued markets on Polymarket to find arbitrage opportunities and detect the wallets that are taking advantage of them so I can copy them. I turned $2K into $11K overnight. It monitored +1,000 wallets. I realized something very quickly. There are arbitrage bots against which I can't compete without knowing how to program. But I can find them. And copy them. Claude built me a monitoring terminal connected to a copytrading bot on Telegram. It's not a script. Not even a bot. It's an AI agent that improves every time it finds a new wallet. It analyzes the behavior of each wallet. How it operates. Its arbitrage patterns. The size of its positions. The exact moment it enters. • 70% hit rate. • 7 wallets being copied right now out of more than 500 monitored. The bot never stops. Never bets. It just follows the math and seeks profit. You only need: • Claude • A device • 1 hour a day I'm going to share it for free for the next 24 hours. To get it: 1. Comment “claude” 2. Like and RT 3. Follow me

I'm going to quit my job to dedicate myself 100% to Claude. I asked it to do this: Analyze undervalued markets on Polymarket to find arbitrage opportunities and detect the wallets that are taking advantage of them so I can copy them. I turned $2K into $11K overnight. It monitored +1,000 wallets. I realized something very quickly. There are arbitrage bots against which I can't compete without knowing how to program. But I can find them. And copy them. Claude built me a monitoring terminal connected to a copytrading bot on Telegram. It's not a script. Not even a bot. It's an AI agent that improves every time it finds a new wallet. It analyzes the behavior of each wallet. How it operates. Its arbitrage patterns. The size of its positions. The exact moment it enters. • 70% hit rate. • 7 wallets being copied right now out of more than 500 monitored. The bot never stops. Never bets. It just follows the math and seeks profit. You only need: • Claude • A device • 1 hour a day I'm going to share it for free for the next 24 hours. To get it: 1. Comment “claude” 2. Like and RT 3. Follow me

Marry Evan

18,569 просмотров • 11 дней назад

The past year has seen me have a renaissance, in the truest sense… I won’t go into details now but will at some point before long. What has brought so much happiness to my life and those around me this past year has been my falling back in love with sport. Cycling has, and always will be, my number one. Yet I’d forgotten that I simply love sport, not for results but for the sheer joy of doing it, I’d completely forgotten that the health of my mind is intrinsically connected to the health of my body. I’ve rediscovered the love I had for sport that existed before the world of professional cycling took over in the way it did. I’ve been pushing myself and trying new things this past year, indifferent to the results, just out having fun and at times going deeper than I thought I was capable of anymore. Last week I got on a TT bike for the first time in a decade, Factor Bikes built me a bike, I’ve been looking at it for two years and decided it was time to get fitted, getting back on it felt like going home. Anyway, the long and the short of this is that it’s inspired me to create a club to inspire and be inspired. A community for us to share our love for getting out there and doing it, because I’ve realized that although I spend most of my sporting life on my own I derive the most pleasure when feeling part of something. It’s in its early days, I’ve called it Sporting Club CHPT3 aka SCC3, I’d love you to check it out and join. It’s still in its infancy, but I hope it’s going to grow into something that will inspire you as much as me.

The past year has seen me have a renaissance, in the truest sense… I won’t go into details now but will at some point before long. What has brought so much happiness to my life and those around me this past year has been my falling back in love with sport. Cycling has, and always will be, my number one. Yet I’d forgotten that I simply love sport, not for results but for the sheer joy of doing it, I’d completely forgotten that the health of my mind is intrinsically connected to the health of my body. I’ve rediscovered the love I had for sport that existed before the world of professional cycling took over in the way it did. I’ve been pushing myself and trying new things this past year, indifferent to the results, just out having fun and at times going deeper than I thought I was capable of anymore. Last week I got on a TT bike for the first time in a decade, Factor Bikes built me a bike, I’ve been looking at it for two years and decided it was time to get fitted, getting back on it felt like going home. Anyway, the long and the short of this is that it’s inspired me to create a club to inspire and be inspired. A community for us to share our love for getting out there and doing it, because I’ve realized that although I spend most of my sporting life on my own I derive the most pleasure when feeling part of something. It’s in its early days, I’ve called it Sporting Club CHPT3 aka SCC3, I’d love you to check it out and join. It’s still in its infancy, but I hope it’s going to grow into something that will inspire you as much as me.

David Millar

111,669 просмотров • 2 лет назад

Got to use a T-bar row for the 2nd time in the past year and a half Likely going to be joining a new gym soon that has this. I dearly look forward to that day Im not a science based lifter, but i am a BIG fan of the deeeeppp streeetchhh. And this bad boy was made for it

Got to use a T-bar row for the 2nd time in the past year and a half Likely going to be joining a new gym soon that has this. I dearly look forward to that day Im not a science based lifter, but i am a BIG fan of the deeeeppp streeetchhh. And this bad boy was made for it

MM

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