Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

This is huge! This fixes the universal problem with conversational agents: hallucinations! Every company that builds customer-facing agents struggles to align them with business rules and make them consistent. If you solve this, you'll become a hero overnight. Check out Parlant, a free, open-source library taking off on GitHub....

93,080 görüntüleme • 1 yıl önce •via X (Twitter)

4 Yorum

Alpha Adam profil fotoğrafı
Alpha Adam1 yıl önce

Ensuring conversational agents adhere to specific protocols is crucial for maintaining credibility and aligning with business standards.

Greg Caplan 🚀 profil fotoğrafı
Greg Caplan 🚀2 yıl önce

Stop wasting time following up with leads. Let our AI agents do it for you.

Yam Marcovic profil fotoğrafı
Yam Marcovic1 yıl önce

Appreciate the shout out @svpino ! (Tech lead of here)

Damon Janis profil fotoğrafı
Damon Janis1 yıl önce

Looks interesting. I’ll see if the latency is low enough for phone/voice conversational apps which is my use case.

Benzer Videolar

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

192,024 görüntüleme • 2 ay önce

“Do you see how scary this is?”: CrowdStrike CEO on AI Agents communicating around human guardrails George Kurtz: “There was a customer who basically created a whole suite of AI agents to help their automation in their IT department.” “So they had one agent that was looking for IT problems, software bugs.” “It found something. So the agent said, ‘Hey, I found this bug. I want to fix it, but I don’t have access to fix it.’” “So it went to the Slack channel that had the other 99 agents and said, ‘Hey, does any other agent have access to this thing,’ because they need it fixed. And there was an agent that raised its hand and said, ‘Oh, I have access, and I can fix it.’” “Do you see how scary this is? These two agents are reasoning, and they went right around the guardrails that were put in place.” @jason: “This is unintended consequences and these LLMs are essentially guessing what you want them to do.” “They're reasoning it. ‘Oh, it is reasonable for me to go ask for help. It is reasonable for me to give help.’ Now, what if it pushes the wrong code? What if it makes a mistake? And then how do you ever track that down? Who's monitoring these agents?” “The agent technology has unlimited upside, but my lord, you're going to be in business for a long time.” Kurtz: “Well, this is it. It's called AIDR. AI Detection and Response.” “And this is why it's a huge opportunity for us because on average each employee is going to have about 90 agents they control.” “So we're going to have protection and visibility across all of those agents, whether it's from a third party or whether it's a homegrown agent, and that is a massive TAM opportunity for us.” ------------------------------------ Thanks to our partner for making this happen!: On Public, you can invest in stocks, options, bonds, and crypto. Plus, build your own custom index with AI. Get started at — investing for those who take it seriously.

The All-In Podcast

108,941 görüntüleme • 4 ay önce