Run - Summarizer
Summary
successSummarizer
Inputs
{
"model": "claude-opus-4-8",
"params": {
"prompt": "Given the source below, can you create a report in the requested format?\n\nYou're given a source (articles, PDFs, or Youtube videos). Can you summarize and extract the core points from the given source? Make it one paragraph in length\n\nImagine the author is my friend. He/she is explaining to me what the text is about over a lunch. The author uses simple words, breaks down the jargon when needed and just overalls simplifies the text so that it's easily understood.\n\nThis idea came to me as an inspiration from this podcast snippet:\n\n-Snippet-\n\n[Person A]: Why do you think, by default, people who are genuine experts in their field are often bad at explaining it to somebody ramping up?\n\n[Person B]: It's the curse of knowledge and expertise. This is a real phenomenon, and I suffered from it myself as much as I try not to. But you take certain things for granted, and you can't put yourself in the shoes of new people who are just starting out. This is pervasive and happens to me as well. One thing that's extremely helpful is... If somebody writes a paper or a blog post or an announcement, it is in 100% of cases that just the narration or the transcription of how they would explain it to you over lunch is way more, not only understandable, but actually also more accurate and scientific, in the sense that people have a bias to explain things in the most abstract, jargon-filled way possible and to clear their throat for four paragraphs before they explain the central idea. But there's something about communicating one-on-one with a person which compels you to just… say the thing!\n\n[Person A]: Haha! Just say the thing! Exactly, that’s really good. I noticed this many, many times. The most prominent example is that I remember back in my PhD days doing research. You read someone's paper, and you work to understand what it's doing. Then you catch them, you're having beers at the conference later, and you ask them, \"So this paper, what were you doing? What is the paper about?\" They will just tell you these three sentences that perfectly captured the essence of that paper and totally give you the idea. And you didn't have to read the paper. It's only when you're sitting at the table with a beer or something, and they're like, \"Oh yeah, the paper is just, you take this idea, you take that idea and try this experiment and you try out this thing.\" They have a way of just putting it conversationally just perfectly. And you’re like… “Why isn't that the abstract?” Haha!\n\n-Snippet-\n\n---\n\nSource:\n${source}",
"max_tokens": 8192,
"temperature": 1
},
"inputMappings": {},
"outputVariableName": "summary"
}Output
summaryReport: "You've Been Kicked Out of the Arena, You Just Don't Know It Yet"
So here's what the author is basically telling you over lunch: a ton of companies think they're keeping up with the AI wave, but they're actually already losing—they just haven't realized it yet. Picture a business that looked great three years ago—$100M+ in revenue, good customers, solid team. Now they're slapping chatbots onto their product, giving it a cute name, and saying stuff like "we need to be the Cursor for X." But underneath, nothing's really changed—sales sells the same way, meetings still drag on, and everyone's waiting until "next quarter" or "when we have headcount." They feel busy, so they assume they're still competing. The problem? Their real competition isn't the familiar rival companies anymore—it's scrappy startups who naturally use the best AI tools without any bureaucratic hoops, and who've already built the product you have sitting on a slide and are quietly poaching your customers and your best people. The author's simple test for whether you're already out of the game: can you get anything done in a single day? (Fix a bug, launch a landing page, upgrade to a new model.) If you could move fast but don't, that's a you problem. The advice for startups is to be even more aggressive—steal talent, clone the incumbent's product for a fraction of the cost, and have more fun doing it. For the big companies that actually want to survive, it takes brutal moves: force everyone to automate 80% of their own job in two weeks, get legal/security/finance out of the way, fire resistant execs (and engineers) fast, buy what you can't build, and rebuild your product from scratch. But honestly? The author doubts most will have the guts. The closing gut-punch: take a look around and ask not just "where am I?" but "where am I not?"
Final output
SummaryReport: "You've Been Kicked Out of the Arena, You Just Don't Know It Yet"
So here's what the author is basically telling you over lunch: a ton of companies think they're keeping up with the AI wave, but they're actually already losing—they just haven't realized it yet. Picture a business that looked great three years ago—$100M+ in revenue, good customers, solid team. Now they're slapping chatbots onto their product, giving it a cute name, and saying stuff like "we need to be the Cursor for X." But underneath, nothing's really changed—sales sells the same way, meetings still drag on, and everyone's waiting until "next quarter" or "when we have headcount." They feel busy, so they assume they're still competing. The problem? Their real competition isn't the familiar rival companies anymore—it's scrappy startups who naturally use the best AI tools without any bureaucratic hoops, and who've already built the product you have sitting on a slide and are quietly poaching your customers and your best people. The author's simple test for whether you're already out of the game: can you get anything done in a single day? (Fix a bug, launch a landing page, upgrade to a new model.) If you could move fast but don't, that's a you problem. The advice for startups is to be even more aggressive—steal talent, clone the incumbent's product for a fraction of the cost, and have more fun doing it. For the big companies that actually want to survive, it takes brutal moves: force everyone to automate 80% of their own job in two weeks, get legal/security/finance out of the way, fire resistant execs (and engineers) fast, buy what you can't build, and rebuild your product from scratch. But honestly? The author doubts most will have the guts. The closing gut-punch: take a look around and ask not just "where am I?" but "where am I not?"