Loading video...

Video Failed to Load

Go Home

CODEX SKILL THAT FINDS THE BEST PRICING FOR YOUR STARTUP! I made a Codex skill that analyzes your startup and recommends how you should monetize it. Send it your startup URL while Codex researches competitors, compares pricing models, and recommends concrete plans and price hypotheses. -> monthly vs annual...

15,117 views • 1 month ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

I just went down this rabbit hole, and it's so fascinating. So apparently, airlines have been selling your data to competitors for years. Strange right? I know, hear me out... It's called dynamic pricing. Dynamic pricing is when a company charges you a price calculated specifically for you, based on what they know about you, rather than a fixed price everyone sees. Nobody called it surveillance. The mainstream take on dynamic pricing is that it's sinister and new. Corporations secretly watching, jacking up prices, exploiting desperation. That anger is mostly right. Dynamic pricing isn't a bug that crept into capitalism. It's the entire architecture of how information asymmetry becomes profit. Airlines have always charged different people different prices for the same seat. Hotels. Insurance companies. Actuarial profiling predates the internet. What changed isn't the behavior. It's the resolution. Your battery at 8% telling Uber you're stranded is a higher-resolution version of the taxi driver who saw you running in the rain and didn't turn the meter off. The new part is the precision. They know you searched the same flight six times. They know you're on a Mac. They know your zip code and how long you've been sitting on the page. Old dynamic pricing responded to demand. Surveillance pricing responds to you. The counterargument from the market side is real. Personalization can mean discounts. But companies optimizing for revenue will use behavioral data to find the ceiling, not the floor. What are your thoughts? Is this fair or pure greed from big corp? That's a wrap. Li is a gallery for the greatest minds in economics, psychology, and history. Follow if that interests you. We are ONE genius away. -- P.S. I'm building a course on how the world actually works. Not the surface story, but the incentive layer underneath it. Who funds what. Who benefits from what you believe? Why the official explanation is rarely the complete one. Comment "yes" if you're interested in something like this. Waitlist opens soon.

GeniusThinking

38,698 views • 5 months ago

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 views • 2 months ago