正在加载视频...

视频加载失败

Every skill file I write ends with a self-improvement loop. It sits at the bottom of the skill.md and runs before the skill finishes: - Did any step fail or need a workaround? - Did I correct or reject anything meaningful? - Did you discover something a future run...

11,799 次观看 • 1 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

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

194,841 次观看 • 6 个月前

HERMES AGENT /LEARN IS ONE OF THE MOST UNDERRATED FEATURE. SHOW IT A WORKFLOW ONCE. IT SAVES THE SKILL. REPEATS IT FOREVER WITHOUT RE-EXPLAINING. you publish a YouTube video: write the title, create the thumbnail, write the description, set tags, schedule it. do it once with Hermes watching. type /learn. Hermes distills that workflow into a reusable skill. next time you say "publish this video," the agent follows the exact same steps. no re-explaining. no missed steps. WHAT YOU CAN TEACH IT: → show it your publishing workflow → /learn → give it an article → /learn → walk it through a client onboarding process → /learn → feed it API documentation → /learn → show it how you process invoices → /learn anything you do more than twice should become a /learn skill. THREE WAYS TO USE /LEARN: from a workflow you walked through: do the task once in chat. then /learn. Hermes extracts the procedure from the conversation. from a directory: /learn ~/docs/youtube-publishing/ reads every file. creates the skill. from a URL: /learn https:// any-documentation-page. com reads the page. distills the skill. the skill saves to ~/.hermes/skills/ with a SKILL.md containing: → when to trigger → step-by-step procedure → pitfalls to avoid → verification steps available as a slash command from that moment. WHY THIS CHANGES DAILY WORK: before /learn: you explain the same process to the agent every time you start a new session. session ends. context lost. start over. after /learn: you explain once. the skill persists. every future session already knows the procedure. the agent follows it without prompting. the boring repetitive tasks you do every week become one-command skills you never think about again. comment LEARN and I'll send you the full guide on turning any workflow into a permanent Hermes skill. full Hermes architecture deep-dive in the article 👇

YanXbt

13,150 次观看 • 3 个月前

i genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. you give Grok Bot one folder on its own cloud computer, feed it your emails, links and photos from your phone, and it reads them, links them, and files them into a living wiki of everything you know. it compounds like interest, the more you feed it, the smarter it gets. doesn't matter if you're a developer, a salesperson or a student, you need this the full setup: > create a bot in Grok Bot, name it Brain and add Gmail and Google Calendar in Connect apps. it runs on its own cloud computer, so it keeps working while your laptop is shut > paste the prompt from chapter 07 of my article below into its chat. one message builds the folder, the routines and the rules > it reads the last 100 emails you sent and writes voice.md, 10 rules of how you write, each with a real line of yours. no more "hope this finds you well" drafts > label any email "Brain" and every night at 11 PM it saves the original and files it on the page of that person or project > at 7:30 AM you get one page with what came in, what it drafted and what waits for your yes, ranked by the 5 projects you actually work on > correct it once and the fix goes into rules.md, which it rereads before every task. every Sunday it tells you what you decided and forgot five minutes to set up, and you never start from a blank chat again. every prompt is in the 7-step course below. or paste the whole article into Brain's chat and it builds the brain for you. bookmark this

Argona

69,911 次观看 • 4 天前