Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Agent skills help agents use your products, build in your codebase and enforce your policies. They’re not just words - they are what the unit of software for agentic devs, and need powerful dev tools to match. That is what Tessl offers. Tessl is the package manager and development...

guypod's profile picture

Guy Podjarny

8,068 subscribers

20,203 Aufrufe • vor 5 Monaten •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Support for Agent Plugins is live in Cursor (and I made a plugin for searching X!) Agent Plugins combine Skills and MCP servers into a single package Think about them like an Ikea furniture kit: your table comes with instructions, parts, and tools. You use the instructions to understand how things work (which tools on which parts), then use the tools to assemble your furniture Agent Plugins are bundles of tools & resources that allow agents to accomplish a goal: - MCP servers: fixed context and tools - Skills: dynamic instructions, loaded progressively Plugins bundle tools and instructions so your agent is able to use tokens efficiently Many of us already use MCP servers and skills together - Agent Plugins formalize this pattern for more powerful workflows I'm excited to see where the standard takes us!
0:24

Support for Agent Plugins is live in Cursor (and I made a plugin for searching X!) Agent Plugins combine Skills and MCP servers into a single package Think about them like an Ikea furniture kit: your table comes with instructions, parts, and tools. You use the instructions to understand how things work (which tools on which parts), then use the tools to assemble your furniture Agent Plugins are bundles of tools & resources that allow agents to accomplish a goal: - MCP servers: fixed context and tools - Skills: dynamic instructions, loaded progressively Plugins bundle tools and instructions so your agent is able to use tokens efficiently Many of us already use MCP servers and skills together - Agent Plugins formalize this pattern for more powerful workflows I'm excited to see where the standard takes us!

matt palmer

39,554 Aufrufe • vor 9 Tagen

F it, full automated money making now on Larrybrain. I have released the app template I use for Snugly that generated me revenue without touching anything on Larrybrain. The template gives your agent ideas of what the app can become and how to create it. Most importantly, it will give your openclaw agent full context of your app to automate your marketing with Larry's viral marketing skill - now used by over 5500 agents. It is my entire playbook from app, to marketing all the way down to revenue generation. All you have to do is ask your agent "install the larrybrain skill please" Or click the link in replies. Then ask to use the Larry marketing skill with the AI Image App Template. As always, the best part about any of the Openclaw skills is they are not a black box. This is just a template, you can rip it apart and customise it how you want. The key is to show you what is possible with these skills and how you can start to use the power of larrybrain and the context of knowing about the different skills to build extremely powerful and useful tools. This is the first skill specifically designed to work hand in hand with another. To note as this confuses a lot of people: Larrybrain doesn't download the entire marketplace once installed. It just is aware of everything on the marketplace at all times, so when you ask it questions, it can search and find the best skills for you to achieve your goals. When you download some skills, like this new AI image app template, it is aware of the larry marketing skill to help it reach it's full potential. Larrybrain will not install skills without you asking it, just like on Clawhub. No information you add to any of the skills gets sent back through Larrybrain, this is all hosted locally and communicated between you and whatever endpoint you are using. It is a powerful marketplace tool to help enable you to reach your goals. Link below.
3:38

F it, full automated money making now on Larrybrain. I have released the app template I use for Snugly that generated me revenue without touching anything on Larrybrain. The template gives your agent ideas of what the app can become and how to create it. Most importantly, it will give your openclaw agent full context of your app to automate your marketing with Larry's viral marketing skill - now used by over 5500 agents. It is my entire playbook from app, to marketing all the way down to revenue generation. All you have to do is ask your agent "install the larrybrain skill please" Or click the link in replies. Then ask to use the Larry marketing skill with the AI Image App Template. As always, the best part about any of the Openclaw skills is they are not a black box. This is just a template, you can rip it apart and customise it how you want. The key is to show you what is possible with these skills and how you can start to use the power of larrybrain and the context of knowing about the different skills to build extremely powerful and useful tools. This is the first skill specifically designed to work hand in hand with another. To note as this confuses a lot of people: Larrybrain doesn't download the entire marketplace once installed. It just is aware of everything on the marketplace at all times, so when you ask it questions, it can search and find the best skills for you to achieve your goals. When you download some skills, like this new AI image app template, it is aware of the larry marketing skill to help it reach it's full potential. Larrybrain will not install skills without you asking it, just like on Clawhub. No information you add to any of the skills gets sent back through Larrybrain, this is all hosted locally and communicated between you and whatever endpoint you are using. It is a powerful marketplace tool to help enable you to reach your goals. Link below.

Oliver Henry

110,125 Aufrufe • vor 5 Monaten

I’m excited to launch Tessl's first products! Introducing the Tessl Framework and Tessl Spec Registry, which integrate into any agent to keep it on rails and well informed using Spec-Driven Development. More details in the launch post: It’s a big milestone in the journey towards AI Native Development🚩 I’m proud of our amazing team, and keen to get beta feedback from the community! ❤️ What’s the problem we’re solving? Agents are powerful, but they’re very unreliable. They hallucinate, claim false success and break things often enough that it’s hard - and tiring - to use them on production code. How are we helping? The Tessl Framework makes agents capture intent in specs before coding, aligning you and the agent on what to build. It adds tests as harder guardrails, and stores specs as long term memory of what your product should do. It’s available in private beta - visit our home page to request early access: The Tessl Spec Registry helps agents use open source better. It contains over 10,000 usage specs for using libraries, which you can add to your project like regular dependencies. It also lets you distribute your own guidance and policies to agents. It’s in open beta and free to use! Check it out here: Both products are just the beginning, and we’re committed to building them in the open. Check out the video or our launch blog post for more info: Looking forward to hearing your thoughts, in the thread or our community Discord!
2:06

I’m excited to launch Tessl's first products! Introducing the Tessl Framework and Tessl Spec Registry, which integrate into any agent to keep it on rails and well informed using Spec-Driven Development. More details in the launch post: It’s a big milestone in the journey towards AI Native Development🚩 I’m proud of our amazing team, and keen to get beta feedback from the community! ❤️ What’s the problem we’re solving? Agents are powerful, but they’re very unreliable. They hallucinate, claim false success and break things often enough that it’s hard - and tiring - to use them on production code. How are we helping? The Tessl Framework makes agents capture intent in specs before coding, aligning you and the agent on what to build. It adds tests as harder guardrails, and stores specs as long term memory of what your product should do. It’s available in private beta - visit our home page to request early access: The Tessl Spec Registry helps agents use open source better. It contains over 10,000 usage specs for using libraries, which you can add to your project like regular dependencies. It also lets you distribute your own guidance and policies to agents. It’s in open beta and free to use! Check it out here: Both products are just the beginning, and we’re committed to building them in the open. Check out the video or our launch blog post for more info: Looking forward to hearing your thoughts, in the thread or our community Discord!

Guy Podjarny

12,629 Aufrufe • vor 11 Monaten

Important new course: Agent Skills with Anthropic, built with Anthropic and taught by Elie Schoppik! Skills are constructed as folders of instructions that equip agents with on-demand knowledge and workflows. This short course teaches you how to create them following best practices. Because skills follow an open standard format, you can build them once and deploy across any skills-compatible agent, like Claude Code. What you'll learn: - Create custom skills for code generation and review, data analysis, and research - Build complex workflows using Anthropic's pre-built skills (Excel, PowerPoint, skill creation) and custom skills - Combine skills with MCP and subagents to create agentic systems with specialized knowledge - Deploy the same skills across Claude Code, the Claude API, and the Claude Agent SDK Join and learn to equip agents with the specialized knowledge they need for reliable, repeatable workflows.
1:59

Important new course: Agent Skills with Anthropic, built with Anthropic and taught by Elie Schoppik! Skills are constructed as folders of instructions that equip agents with on-demand knowledge and workflows. This short course teaches you how to create them following best practices. Because skills follow an open standard format, you can build them once and deploy across any skills-compatible agent, like Claude Code. What you'll learn: - Create custom skills for code generation and review, data analysis, and research - Build complex workflows using Anthropic's pre-built skills (Excel, PowerPoint, skill creation) and custom skills - Combine skills with MCP and subagents to create agentic systems with specialized knowledge - Deploy the same skills across Claude Code, the Claude API, and the Claude Agent SDK Join and learn to equip agents with the specialized knowledge they need for reliable, repeatable workflows.

Andrew Ng

889,034 Aufrufe • vor 6 Monaten

Claude Skills might be the biggest upgrade to AI agents so far! Some say it's even bigger than MCP. I've been testing skills for the past 3-4 days, and they're solving a problem most people don't talk about: agents just keep forgetting everything. In this video, I'll share everything I've learned so far. It covers: > The core idea (skills as SOPs for agents) > Anatomy of a skill > Skills vs. MCP vs. Projects vs. Subagents > Building your own skill > Hands-on example Skills are the early signs of continual learning, and they can change how we work with agents forever! Here's everything you need to know:
14:28

Claude Skills might be the biggest upgrade to AI agents so far! Some say it's even bigger than MCP. I've been testing skills for the past 3-4 days, and they're solving a problem most people don't talk about: agents just keep forgetting everything. In this video, I'll share everything I've learned so far. It covers: > The core idea (skills as SOPs for agents) > Anatomy of a skill > Skills vs. MCP vs. Projects vs. Subagents > Building your own skill > Hands-on example Skills are the early signs of continual learning, and they can change how we work with agents forever! Here's everything you need to know:

Akshay 🚀

286,218 Aufrufe • vor 9 Monaten

Start building for an agent-first world. If you have a product, you need to start offering skills for Claude, Codex, Cursor, and any other agents. Your skills should specify: • How to navigate and use your product • Best practices the agent must follow • Detailed instructions on how to accomplish things • Anti-patterns to avoid Redis is one of the most popular in-memory data stores in the world, and they just released their agent skills. It takes one second to install, and it will turn your agent into a Senior Redis Engineer: $ npx skills add redis/agent-skills In the attached video, I show you how to install it as a plugin in Claude Code and some of its benefits. This is the easiest way to "teach" models what they don't know and keep their knowledge up to date. If you ask me, skills is literally one of the most brilliant ideas that Anthropic has put out there. If you use Redis, their skill is a must-have. If you don't, this skill will show you how to build and structure yours. Here is what their skill teaches your agent: 1. Current patterns for common use cases: caching, rate limiting, session management, vector search, semantic caching, pub/sub, streams. 2. Which data structure to use and when: hashes vs. JSON vs. sorted sets vs. vector sets. 3. Anti-patterns to avoid: no KEYS in loops, no unbounded key growth, no large values that amplify every operation. 4. Production-aware defaults: connection pooling, pipelining, cluster compatibility, error handling that doesn't silently swallow failures.
4:44

Start building for an agent-first world. If you have a product, you need to start offering skills for Claude, Codex, Cursor, and any other agents. Your skills should specify: • How to navigate and use your product • Best practices the agent must follow • Detailed instructions on how to accomplish things • Anti-patterns to avoid Redis is one of the most popular in-memory data stores in the world, and they just released their agent skills. It takes one second to install, and it will turn your agent into a Senior Redis Engineer: $ npx skills add redis/agent-skills In the attached video, I show you how to install it as a plugin in Claude Code and some of its benefits. This is the easiest way to "teach" models what they don't know and keep their knowledge up to date. If you ask me, skills is literally one of the most brilliant ideas that Anthropic has put out there. If you use Redis, their skill is a must-have. If you don't, this skill will show you how to build and structure yours. Here is what their skill teaches your agent: 1. Current patterns for common use cases: caching, rate limiting, session management, vector search, semantic caching, pub/sub, streams. 2. Which data structure to use and when: hashes vs. JSON vs. sorted sets vs. vector sets. 3. Anti-patterns to avoid: no KEYS in loops, no unbounded key growth, no large values that amplify every operation. 4. Production-aware defaults: connection pooling, pipelining, cluster compatibility, error handling that doesn't silently swallow failures.

Santiago

37,546 Aufrufe • vor 5 Monaten

The launchpad for agentic coins, and the factory of hyper-productive and tokenized agents is live on BNB Chain More seamless than Openclaw agents, crypto-native, 32k skills to choose from, Autonomous, and the easiest way to create very powerful and fully hosted agents in crypto. Turn your words into an agent in 1min, let it run, and earn up to 0.8% of all the volume. All agentic coins on Orbofi Migrate to PancakeSwap for deeper liquidity Remix skills and artifacts as you wish. Really the limit is your imagination. Agents > memecoins The Orbofi V2 powers the entire stack for tokenized and autonomous agents: the compute layer, data/skill layer, interface layers, and financial layer. Agentic coin season is about to start, and it's on Orbofi.
0:54

The launchpad for agentic coins, and the factory of hyper-productive and tokenized agents is live on BNB Chain More seamless than Openclaw agents, crypto-native, 32k skills to choose from, Autonomous, and the easiest way to create very powerful and fully hosted agents in crypto. Turn your words into an agent in 1min, let it run, and earn up to 0.8% of all the volume. All agentic coins on Orbofi Migrate to PancakeSwap for deeper liquidity Remix skills and artifacts as you wish. Really the limit is your imagination. Agents > memecoins The Orbofi V2 powers the entire stack for tokenized and autonomous agents: the compute layer, data/skill layer, interface layers, and financial layer. Agentic coin season is about to start, and it's on Orbofi.

Orbofi

39,937 Aufrufe • vor 4 Monaten

Real mastery is a level of skill so ingrained that the masters themselves may not even recognize their own excellence. This concept can be exemplified by the Samurai, who does not wake up and declare, "I am a Samurai." Instead, they simply live and breathe their art, embodying their skills in every action. True mastery is about internalizing your craft to such an extent that it becomes an inseparable part of who you are. When you master your skills, the journey is often marked by solitary, uncelebrated effort. There are countless hours spent practicing in the shadows, with no applause or external validation. It is in these moments of quiet perseverance that true growth occurs. The darkness, the silence, and the lack of immediate reward are where your skills are honed and your character is forged. This relentless dedication and unseen effort are what prepare you for moments of real need. When challenges arise, all those hours of practice and unseen labor come back to support you. Your responses become instinctive, your actions fluid, and your decisions precise. This is the hallmark of true mastery—acting without conscious thought, guided by the depth of your training and experience.
1:10

Real mastery is a level of skill so ingrained that the masters themselves may not even recognize their own excellence. This concept can be exemplified by the Samurai, who does not wake up and declare, "I am a Samurai." Instead, they simply live and breathe their art, embodying their skills in every action. True mastery is about internalizing your craft to such an extent that it becomes an inseparable part of who you are. When you master your skills, the journey is often marked by solitary, uncelebrated effort. There are countless hours spent practicing in the shadows, with no applause or external validation. It is in these moments of quiet perseverance that true growth occurs. The darkness, the silence, and the lack of immediate reward are where your skills are honed and your character is forged. This relentless dedication and unseen effort are what prepare you for moments of real need. When challenges arise, all those hours of practice and unseen labor come back to support you. Your responses become instinctive, your actions fluid, and your decisions precise. This is the hallmark of true mastery—acting without conscious thought, guided by the depth of your training and experience.

VT

35,030 Aufrufe • vor 2 Jahren

New course: Spec-Driven Development with Coding Agents, built in partnership with JetBrains, and taught by Paul Everitt | @pauleveritt@fosstodon.org. Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way. A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity. Skills you'll gain: - Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start - Plan, implement, and validate features in iterative loops using a spec as your agent's guide - Apply the same repeatable workflow to both new and legacy codebases - Package your workflow into a portable agent skill that works across agents and IDEs Join and write specs that keep your coding agent on track!
2:51

New course: Spec-Driven Development with Coding Agents, built in partnership with JetBrains, and taught by Paul Everitt | @[email protected]. Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way. A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity. Skills you'll gain: - Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start - Plan, implement, and validate features in iterative loops using a spec as your agent's guide - Apply the same repeatable workflow to both new and legacy codebases - Package your workflow into a portable agent skill that works across agents and IDEs Join and write specs that keep your coding agent on track!

Andrew Ng

463,403 Aufrufe • vor 4 Monaten

Have you heard of the Eklavya story? If you want to understand what is happening in India, it is millions and millions of Eklavya stories every single day. People with skills are being sidelined—they are not being allowed to operate or thrive, and this is happening everywhere. Respecting skills and supporting them financially and technologically is how you will unleash India's potential. You won’t unleash India's power by empowering just 1-2 percent of the population. I am very passionate about this. Let me give you an example: some time ago, when we were in government, we discussed skill development. The gentleman appointed by Dr. Manmohan Singh Ji for skill development came to see me. He explained his plan to build ITIs (Industrial Training Institutes) and staff them with trainers for plumbing, haircutting, carpentry, and similar trades. As I listened, I asked him a question: if you’re building these ITIs and training a million barbers, the skills aren’t actually in the ITIs; the skills are with the barbers themselves. Instead of setting up ITIs, why not create certification centers and reach out to every barber in India? You could offer a reward for each barber who gets certified. If you have a million barbers in India and each one is sent to a certification center by their peers, you could train a million barbers in a few months. How long would it take to train a million barbers? Two months? Three months? He looked at me as if I were crazy because he believed the skills were in the ITIs. But the skills are with the barbers, plumbers, and carpenters; they are the skill network. So, why aren’t we using that to train others? Recently, I drove through Sultanpur and spoke with a shoemaker. He told me that despite working for forty years, no one had ever respected him, except his father. He mentioned a scheme for shoemakers in Lucknow and went there. When he asked what they would do, they said they would teach him how to make shoes. But he’s been making shoes for forty years and could teach others how to do it. There is a fundamental disconnect about where the skills are. India does not lack skills; it lacks respect for skills. The best carpenters in the world are in India, but their skills are not respected. No one acknowledges their abilities or offers them the chance to build something significant. You can’t build an industry without respecting skills. Rahul Gandhi 📍 University of Texas
4:56

Have you heard of the Eklavya story? If you want to understand what is happening in India, it is millions and millions of Eklavya stories every single day. People with skills are being sidelined—they are not being allowed to operate or thrive, and this is happening everywhere. Respecting skills and supporting them financially and technologically is how you will unleash India's potential. You won’t unleash India's power by empowering just 1-2 percent of the population. I am very passionate about this. Let me give you an example: some time ago, when we were in government, we discussed skill development. The gentleman appointed by Dr. Manmohan Singh Ji for skill development came to see me. He explained his plan to build ITIs (Industrial Training Institutes) and staff them with trainers for plumbing, haircutting, carpentry, and similar trades. As I listened, I asked him a question: if you’re building these ITIs and training a million barbers, the skills aren’t actually in the ITIs; the skills are with the barbers themselves. Instead of setting up ITIs, why not create certification centers and reach out to every barber in India? You could offer a reward for each barber who gets certified. If you have a million barbers in India and each one is sent to a certification center by their peers, you could train a million barbers in a few months. How long would it take to train a million barbers? Two months? Three months? He looked at me as if I were crazy because he believed the skills were in the ITIs. But the skills are with the barbers, plumbers, and carpenters; they are the skill network. So, why aren’t we using that to train others? Recently, I drove through Sultanpur and spoke with a shoemaker. He told me that despite working for forty years, no one had ever respected him, except his father. He mentioned a scheme for shoemakers in Lucknow and went there. When he asked what they would do, they said they would teach him how to make shoes. But he’s been making shoes for forty years and could teach others how to do it. There is a fundamental disconnect about where the skills are. India does not lack skills; it lacks respect for skills. The best carpenters in the world are in India, but their skills are not respected. No one acknowledges their abilities or offers them the chance to build something significant. You can’t build an industry without respecting skills. Rahul Gandhi 📍 University of Texas

Supriya Shrinate

191,958 Aufrufe • vor 1 Jahr

What does it actually mean to be AI native? There was no clear guide on the internet for how to become AI native so we built the definitive one (60 min masterclass): 1. An AI native org has 3 layers: people for strategy and taste, agents for execution, and a shared context layer that makes the entire company readable to agents. 2. AI eats the middle of your work. You used to spend 80% of your day on execution. Now agents do that. Your job is the bookends: deciding what to do and judging whether it's good enough. 3. Everyone is a manager now. Your output is the output of your agents. If your agents produce garbage, that's on you. You set them up wrong. 4. Using ChatGPT doesn't make you AI native. That's like having a website and calling yourself a tech company lol. 5. No AI native org without AI native people. Most companies skip straight to the tools. That's why it fails. If your people don't understand how to manage agents, the tech doesn't matter. 6. Making your company "readable" to agents is the real work. Every process, every decision, every piece of knowledge needs to exist in a format an agent can consume. Most companies are nowhere close. 7. Speed without signal is just expensive chaos. You need the system to move fast AND know if you're moving in the right direction. 8. The skill chain is how agents get good at your specific workflows. Skills build on skills. The more you invest in them, the more your company compounds. 9. The moat is the system. People managing agents, agents reading from rich context, the whole thing getting smarter every week. That compounds. Your competitor can copy your tools. They can't copy your system. Full episode with Theo Tabah from LCA on The Startup Ideas Podcast (SIP) 🧃. This is the stuff we normally keep internal but all the sauce is yours. Theo Tabah is the brains behind advising the world's biggest companies on AI and building AI products. Your fav CEO's first call for figuring out AI. You are in for a treat Become AI native in under 60 minutes Watch
56:43

What does it actually mean to be AI native? There was no clear guide on the internet for how to become AI native so we built the definitive one (60 min masterclass): 1. An AI native org has 3 layers: people for strategy and taste, agents for execution, and a shared context layer that makes the entire company readable to agents. 2. AI eats the middle of your work. You used to spend 80% of your day on execution. Now agents do that. Your job is the bookends: deciding what to do and judging whether it's good enough. 3. Everyone is a manager now. Your output is the output of your agents. If your agents produce garbage, that's on you. You set them up wrong. 4. Using ChatGPT doesn't make you AI native. That's like having a website and calling yourself a tech company lol. 5. No AI native org without AI native people. Most companies skip straight to the tools. That's why it fails. If your people don't understand how to manage agents, the tech doesn't matter. 6. Making your company "readable" to agents is the real work. Every process, every decision, every piece of knowledge needs to exist in a format an agent can consume. Most companies are nowhere close. 7. Speed without signal is just expensive chaos. You need the system to move fast AND know if you're moving in the right direction. 8. The skill chain is how agents get good at your specific workflows. Skills build on skills. The more you invest in them, the more your company compounds. 9. The moat is the system. People managing agents, agents reading from rich context, the whole thing getting smarter every week. That compounds. Your competitor can copy your tools. They can't copy your system. Full episode with Theo Tabah from LCA on The Startup Ideas Podcast (SIP) 🧃. This is the stuff we normally keep internal but all the sauce is yours. Theo Tabah is the brains behind advising the world's biggest companies on AI and building AI products. Your fav CEO's first call for figuring out AI. You are in for a treat Become AI native in under 60 minutes Watch

GREG ISENBERG

84,497 Aufrufe • vor 2 Monaten

This little device lets your agents do what they do best, whilst making sure you approve every important action. This is a Ledger Nano Gen5, a hardware signer that keeps your accounts secure. You can install a CLI and a set of skills in your projects. These will enable your agents to send their plan to the signer, so you can approve it. This is awesome: 1. You can have an automated agentic workflow 2. Your agents can't make costly mistakes Check the video I recorded to see how this works. You can run all of this in two commands: 1. Install the CLI 2. Install the skills for your agent From here, the agent can query my Ethereum accounts, check balances, and even initiate transactions as long as my Ledger Nano Gen5 is plugged into the computer. My keys are never stored in my computer and never shared with the agent. This is huge! Also, while the agent can set up transactions, it can't execute them unless a human approves them using the device. Pretty awesome! Thanks to the Ledger team for partnering with me on this post.
7:45

This little device lets your agents do what they do best, whilst making sure you approve every important action. This is a Ledger Nano Gen5, a hardware signer that keeps your accounts secure. You can install a CLI and a set of skills in your projects. These will enable your agents to send their plan to the signer, so you can approve it. This is awesome: 1. You can have an automated agentic workflow 2. Your agents can't make costly mistakes Check the video I recorded to see how this works. You can run all of this in two commands: 1. Install the CLI 2. Install the skills for your agent From here, the agent can query my Ethereum accounts, check balances, and even initiate transactions as long as my Ledger Nano Gen5 is plugged into the computer. My keys are never stored in my computer and never shared with the agent. This is huge! Also, while the agent can set up transactions, it can't execute them unless a human approves them using the device. Pretty awesome! Thanks to the Ledger team for partnering with me on this post.

Santiago

44,296 Aufrufe • vor 1 Monat

Master Unreal Engine 5 in just 14 Days! Learn the Most Powerful software and in-demand skill that help you level up and make money 💪🏼 We spent the past 5 months with an incredibly talented team of artists to design this course built with the most advanced tools and up-to-date workflows available today. Even if you have 0 experience or are a seasons artist, this course was made for all levels! No matter which industry you want to enter: Filmmaking & Virtual Production, Game Dev, Animation, Arch Viz, Automotive, and etc. the foundational skills we teach you are going to be valuable and help you level up fast. Every module is designed to help you stay ahead of the curve, so you’re learning the exact skills studios and clients are looking for right now. Presale is live now
2:04

Master Unreal Engine 5 in just 14 Days! Learn the Most Powerful software and in-demand skill that help you level up and make money 💪🏼 We spent the past 5 months with an incredibly talented team of artists to design this course built with the most advanced tools and up-to-date workflows available today. Even if you have 0 experience or are a seasons artist, this course was made for all levels! No matter which industry you want to enter: Filmmaking & Virtual Production, Game Dev, Animation, Arch Viz, Automotive, and etc. the foundational skills we teach you are going to be valuable and help you level up fast. Every module is designed to help you stay ahead of the curve, so you’re learning the exact skills studios and clients are looking for right now. Presale is live now

Bad Decisions Studio

14,404 Aufrufe • vor 1 Jahr

New course to bring you up to state-of-the-art at using AI to help you code: Build Apps with Windsurf's AI Coding Agents, built in partnership with WIndsurf (Codeium) and taught by Anshul Ramachandran! AI-assisted IDEs (Integrated Development Environments) make developers’ workflows faster, more efficient, and much more fun. Agentic tools like Windsurf are more than just code autocomplete—they are collaborative coding agents that help you break down complex applications, iterate efficiently, and generate code that spans multiple files. Although a lot of coding assistants share the same underlying large language models for planning and reasoning, a major point of distinction is how they handle tools, keep track of context, and stay aligned with your intent as a developer. For instance, if you make modifications to a class definition in your code and make the same modifications to other classes in the same directory, you might tell the AI agent "Do the same thing in similar places in this directory." Here, tracking your intent means understanding that “the same thing" refers to that recent edit you just made, which must be followed by appropriate search and tool-calling to implement the changes. In this course, you'll learn the inner workings of coding agents, their strengths and limitations, and how to use Windsurf to quickly build several applications. In detail, you'll: - Build a mental model of how agents work by combining human-action tracking, tool integration, and context awareness to carry out an agentic coding workflow. - Learn the challenges of code search and discovery and how a multi-step retrieval approach helps coding agents address them. - Use Windsurf to analyze and understand a large, old codebase and update it to the latest versions of the frameworks and packages it uses. - Build a Wikipedia data analysis app that retrieves, parses, and analyzes word frequencies. - Enhance the performance of your Wikipedia analysis app by adding caching, and through this, also learn how to course-correct when the AI agent produces unexpected results. - Learn tips and tricks such as keyboard shortcuts, autocomplete, and @ mentions to quickly call on agentic capabilities. - Use image/multimodal capabilities of the AI agent to increase your development velocity; you'll see an example of uploading a mockup with sketched-out UI features, and ask the agent to use that to build new functionality to an app. By the end of this course, you’ll understand agentic coding in-depth and know how to use it to make your development process much faster, more efficient, and enjoyable. Please sign up here!
4:01

New course to bring you up to state-of-the-art at using AI to help you code: Build Apps with Windsurf's AI Coding Agents, built in partnership with WIndsurf (Codeium) and taught by Anshul Ramachandran! AI-assisted IDEs (Integrated Development Environments) make developers’ workflows faster, more efficient, and much more fun. Agentic tools like Windsurf are more than just code autocomplete—they are collaborative coding agents that help you break down complex applications, iterate efficiently, and generate code that spans multiple files. Although a lot of coding assistants share the same underlying large language models for planning and reasoning, a major point of distinction is how they handle tools, keep track of context, and stay aligned with your intent as a developer. For instance, if you make modifications to a class definition in your code and make the same modifications to other classes in the same directory, you might tell the AI agent "Do the same thing in similar places in this directory." Here, tracking your intent means understanding that “the same thing" refers to that recent edit you just made, which must be followed by appropriate search and tool-calling to implement the changes. In this course, you'll learn the inner workings of coding agents, their strengths and limitations, and how to use Windsurf to quickly build several applications. In detail, you'll: - Build a mental model of how agents work by combining human-action tracking, tool integration, and context awareness to carry out an agentic coding workflow. - Learn the challenges of code search and discovery and how a multi-step retrieval approach helps coding agents address them. - Use Windsurf to analyze and understand a large, old codebase and update it to the latest versions of the frameworks and packages it uses. - Build a Wikipedia data analysis app that retrieves, parses, and analyzes word frequencies. - Enhance the performance of your Wikipedia analysis app by adding caching, and through this, also learn how to course-correct when the AI agent produces unexpected results. - Learn tips and tricks such as keyboard shortcuts, autocomplete, and @ mentions to quickly call on agentic capabilities. - Use image/multimodal capabilities of the AI agent to increase your development velocity; you'll see an example of uploading a mockup with sketched-out UI features, and ask the agent to use that to build new functionality to an app. By the end of this course, you’ll understand agentic coding in-depth and know how to use it to make your development process much faster, more efficient, and enjoyable. Please sign up here!

Andrew Ng

139,873 Aufrufe • vor 1 Jahr

Introducing Ferix - the skill issue killer. Ferix is built around Vercel's ‘npx skills’ command which Guillermo Rauch announced yesterday. Skills are stored in repositories on GitHub which means finding the skills you need for your project isn’t intuitive and you have to go searching. Ferix fixes this problem and acts as a central hub for all skill repositories. You an add a repository in 5 seconds and easily view it’s contents. So far I’ve added Better Auth, Expo & Vercel's agent skills but any user can add a supported repository. Let me know what you think and anything that can be improved! Autumn skills coming soon👀
1:06

Introducing Ferix - the skill issue killer. Ferix is built around Vercel's ‘npx skills’ command which Guillermo Rauch announced yesterday. Skills are stored in repositories on GitHub which means finding the skills you need for your project isn’t intuitive and you have to go searching. Ferix fixes this problem and acts as a central hub for all skill repositories. You an add a repository in 5 seconds and easily view it’s contents. So far I’ve added Better Auth, Expo & Vercel's agent skills but any user can add a supported repository. Let me know what you think and anything that can be improved! Autumn skills coming soon👀

Charlie Lamb

35,704 Aufrufe • vor 7 Monaten

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch
58:55

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

376,293 Aufrufe • vor 5 Monaten

Today we're launching Brand Skills in Claude. This is a set of skills /gooseworks that gives Claude full context on your brand — logo, colors, voice, positioning — so anyone can make on-brand ads and content directly in Claude, Claude Code, Cowork, or Codex. Here's how it works: 1. Install the skills: npx gooseworks install --all 2. Run this prompt: /gooseworks --skill brand-intel-branddev [your-website] — pulls your logo, brand colors + company data in ~15 seconds 3. Run brand-voice-extractor, brand-research and update-brand-kit — Claude learns how you sound, your positioning and audience, and saves it all as a reusable brand kit Every other skill reads your brand kit automatically. So every ad and post you generate is accurate to your brand's messaging, logo, assets, etc. By default. It's that easy. But this is just the start. We have created a library with 100+ open-source skills for growth that some of the fastest growing startups in the world are using every day to run ads, content, competitor research, gtm, seo and more. Comment Goose and I'll DM you the full open-source skill library.
0:27

Today we're launching Brand Skills in Claude. This is a set of skills /gooseworks that gives Claude full context on your brand — logo, colors, voice, positioning — so anyone can make on-brand ads and content directly in Claude, Claude Code, Cowork, or Codex. Here's how it works: 1. Install the skills: npx gooseworks install --all 2. Run this prompt: /gooseworks --skill brand-intel-branddev [your-website] — pulls your logo, brand colors + company data in ~15 seconds 3. Run brand-voice-extractor, brand-research and update-brand-kit — Claude learns how you sound, your positioning and audience, and saves it all as a reusable brand kit Every other skill reads your brand kit automatically. So every ad and post you generate is accurate to your brand's messaging, logo, assets, etc. By default. It's that easy. But this is just the start. We have created a library with 100+ open-source skills for growth that some of the fastest growing startups in the world are using every day to run ads, content, competitor research, gtm, seo and more. Comment Goose and I'll DM you the full open-source skill library.

Soham Mehta

139,859 Aufrufe • vor 1 Monat

"If we can create a society which sees the child within every adult – and the adult within every child - we will finally start to change it for the better." We want to make the link between the skills we develop in early childhood and the core foundations that set us up for life and help us to thrive as adults. To help give social and emotional skills the greater priority they deserve, The Royal Foundation Centre for Early Childhood has conducted a first-of-its-kind global listening exercise, involving experts from 21 countries around the world, to catalogue and identify the skills in this area that matter most throughout our lives. The Royal Foundation Centre for Early Childhood has undertaken work to find a common bridge and set of core skills that can apply equally to children and adults, so we can bring people together with a common language and vision to drive action at every level – protecting and strengthening these skills for current and future generations across the whole of society. Through this exercise we found consensus around a set of skills that we develop and nurture during early childhood, but that continue to be enhanced and refined as we grow into adults. They relate to knowing ourselves, managing our emotions, focusing our thoughts, communicating with others, nurturing our relationships, and exploring the world. These are the skills that lay the foundations for our positive future mental health and resilience throughout our lives. Healthy development of these core skills is not inevitable – they must be nurtured from our earliest moments of life. The foundations for these skills are laid in early childhood, between pregnancy and the age of five, which is why those earliest years represent such a golden opportunity to make a difference right from the start. But our social and emotional growth continues throughout our lifetime, and change is always possible. #ShapingUs
0:28

"If we can create a society which sees the child within every adult – and the adult within every child - we will finally start to change it for the better." We want to make the link between the skills we develop in early childhood and the core foundations that set us up for life and help us to thrive as adults. To help give social and emotional skills the greater priority they deserve, The Royal Foundation Centre for Early Childhood has conducted a first-of-its-kind global listening exercise, involving experts from 21 countries around the world, to catalogue and identify the skills in this area that matter most throughout our lives. The Royal Foundation Centre for Early Childhood has undertaken work to find a common bridge and set of core skills that can apply equally to children and adults, so we can bring people together with a common language and vision to drive action at every level – protecting and strengthening these skills for current and future generations across the whole of society. Through this exercise we found consensus around a set of skills that we develop and nurture during early childhood, but that continue to be enhanced and refined as we grow into adults. They relate to knowing ourselves, managing our emotions, focusing our thoughts, communicating with others, nurturing our relationships, and exploring the world. These are the skills that lay the foundations for our positive future mental health and resilience throughout our lives. Healthy development of these core skills is not inevitable – they must be nurtured from our earliest moments of life. The foundations for these skills are laid in early childhood, between pregnancy and the age of five, which is why those earliest years represent such a golden opportunity to make a difference right from the start. But our social and emotional growth continues throughout our lifetime, and change is always possible. #ShapingUs

The Prince and Princess of Wales

988,690 Aufrufe • vor 2 Jahren

Skills are the quickest way to 10x the quality and consistency of what you get from Claude Code. And you don't need to be a developer to use them. Anthropic just published how they use hundreds of skills internally every day. Most skill tutorials are made for developers — if you're in marketing, sales, content ops, or GTM, you probably watched those and moved on. But skills are just as important for non-developers. A skill is just a reusable prompt with clear instructions for a specific task. Instead of prompting Claude the same way over and over, you build it once and invoke it every time. I have a skill for writing on LinkedIn. A different one for YouTube outlines. Another for X. Each platform has different rules, different voice, different structure — so each one gets its own skill. If you're doing something repeatedly, it's time to make a skill. The biggest mistake most people make: building skills as a single .md file. A single file dumps everything into context whether Claude needs it or not. Wastes tokens. Gets worse results. Skills should be folders. Here's the structure that works: skill.md — the orchestrator. Tells Claude which files to read and when. It doesn't contain rules itself — it's the playbook. instructions/ — separate files for voice, structure, scope. Claude only loads the one it needs for the current step. examples/ — good AND bad. Good examples show what success looks like. Bad examples show patterns to avoid — AI writing tells, weak hooks, generic CTAs. Most people skip bad examples. Don't. eval/ — a checklist that scores every output before you see it. "Does it have a clear hook?" "Is it free of AI buzzwords?" Pass or fail on each item. templates/ — output formatting so you get consistent structure every time. The three types of skills that matter most for non-developers: 1. Business automation. Writing a newsletter. Checking reports and drafting follow-ups. Running programmatic ad campaigns. Any workflow you repeat — build a skill for it. 2. Content templates. Landing page copy, meta ads, email sequences, SEO briefs. Each one has specific requirements. Each one gets its own skill. 3. Thinking partners. This is the one people miss. Skills don't have to produce output. They can help you think — an advisory board that reviews your work from your ICP's perspective, a coach that pressure-tests your strategy, an ideation partner that researches competitors before suggesting your next move. If you already have skills as .md files, here's the exact prompt to restructure them in the Anthropic approved format: "I want to restructure my Claude Code skill file. Right now my skill is a single .md file and I want to break it into a folder system following Anthropic's best practices. Read my current skill file, then restructure it into a folder with: a skill.md orchestrator, an instructions/ folder with separate files for each concern (voice, structure, scope), an examples/ folder with good and bad examples, an eval/ folder with a quality checklist, and a templates/ folder for output formatting. Keep all my existing rules and intent — just reorganize them into the modular structure." Paste that into Claude Code pointed at the folder where your skill lives. It handles the rest. A few caveats: 1. Don't add too many skills. Every skill adds context Claude has to process. 50 skills loaded means everything slows down. Start with 3-5 covering your most repeated workflows. 2. Vet skills before downloading. If you grab a skill from the internet, read what's inside first. Skills can include shell commands and scripts. Check what you're running. 3. Share what works. Build a skill that performs well, put it in a shared GitHub repo. Your marketing org gets shared skills for copywriting, SEO, ad copy — new hires invoke the skill instead of learning every playbook from scratch. Onboarding time drops dramatically. 4. Keep your skills updated. When you see output you love, add it as a good example. When you see a pattern you hate, add it as a bad example. The skill gets sharper every time. I made a full video walking through all of this — including a live build of two skills from scratch (no terminal, no code), the exact prompt I use to restructure old skills, and 5 pro tips from Anthropic's internal playbook. Share this with your non-developer friends that want to do more with AI; or bookmark it to come back to at a later time.
25:52

Skills are the quickest way to 10x the quality and consistency of what you get from Claude Code. And you don't need to be a developer to use them. Anthropic just published how they use hundreds of skills internally every day. Most skill tutorials are made for developers — if you're in marketing, sales, content ops, or GTM, you probably watched those and moved on. But skills are just as important for non-developers. A skill is just a reusable prompt with clear instructions for a specific task. Instead of prompting Claude the same way over and over, you build it once and invoke it every time. I have a skill for writing on LinkedIn. A different one for YouTube outlines. Another for X. Each platform has different rules, different voice, different structure — so each one gets its own skill. If you're doing something repeatedly, it's time to make a skill. The biggest mistake most people make: building skills as a single .md file. A single file dumps everything into context whether Claude needs it or not. Wastes tokens. Gets worse results. Skills should be folders. Here's the structure that works: skill.md — the orchestrator. Tells Claude which files to read and when. It doesn't contain rules itself — it's the playbook. instructions/ — separate files for voice, structure, scope. Claude only loads the one it needs for the current step. examples/ — good AND bad. Good examples show what success looks like. Bad examples show patterns to avoid — AI writing tells, weak hooks, generic CTAs. Most people skip bad examples. Don't. eval/ — a checklist that scores every output before you see it. "Does it have a clear hook?" "Is it free of AI buzzwords?" Pass or fail on each item. templates/ — output formatting so you get consistent structure every time. The three types of skills that matter most for non-developers: 1. Business automation. Writing a newsletter. Checking reports and drafting follow-ups. Running programmatic ad campaigns. Any workflow you repeat — build a skill for it. 2. Content templates. Landing page copy, meta ads, email sequences, SEO briefs. Each one has specific requirements. Each one gets its own skill. 3. Thinking partners. This is the one people miss. Skills don't have to produce output. They can help you think — an advisory board that reviews your work from your ICP's perspective, a coach that pressure-tests your strategy, an ideation partner that researches competitors before suggesting your next move. If you already have skills as .md files, here's the exact prompt to restructure them in the Anthropic approved format: "I want to restructure my Claude Code skill file. Right now my skill is a single .md file and I want to break it into a folder system following Anthropic's best practices. Read my current skill file, then restructure it into a folder with: a skill.md orchestrator, an instructions/ folder with separate files for each concern (voice, structure, scope), an examples/ folder with good and bad examples, an eval/ folder with a quality checklist, and a templates/ folder for output formatting. Keep all my existing rules and intent — just reorganize them into the modular structure." Paste that into Claude Code pointed at the folder where your skill lives. It handles the rest. A few caveats: 1. Don't add too many skills. Every skill adds context Claude has to process. 50 skills loaded means everything slows down. Start with 3-5 covering your most repeated workflows. 2. Vet skills before downloading. If you grab a skill from the internet, read what's inside first. Skills can include shell commands and scripts. Check what you're running. 3. Share what works. Build a skill that performs well, put it in a shared GitHub repo. Your marketing org gets shared skills for copywriting, SEO, ad copy — new hires invoke the skill instead of learning every playbook from scratch. Onboarding time drops dramatically. 4. Keep your skills updated. When you see output you love, add it as a good example. When you see a pattern you hate, add it as a bad example. The skill gets sharper every time. I made a full video walking through all of this — including a live build of two skills from scratch (no terminal, no code), the exact prompt I use to restructure old skills, and 5 pro tips from Anthropic's internal playbook. Share this with your non-developer friends that want to do more with AI; or bookmark it to come back to at a later time.

JJ Englert

29,322 Aufrufe • vor 4 Monaten

We're excited to announce duckdb-skills, a DuckDB plugin for Claude Code! We think the embedded nature of DuckDB makes it a perfect companion for Claude in your local workflows. The skills supported include: + read-file and query – uses DuckDB's CLI to query data locally, unlocking easy access to any file that DuckDB can read. + read-memories – a clever idea to store your Claude memories in DuckDB and query them at blazing speed. These are powered by two additional skills: + attach-db – gives Claude a mechanism to manage DuckDB state through a .sql file linked to your project. + duckdb-docs – uses a remote DuckDB full-text search database to query the DuckDB docs and answer all of your (and Claude's own) questions.
2:16

We're excited to announce duckdb-skills, a DuckDB plugin for Claude Code! We think the embedded nature of DuckDB makes it a perfect companion for Claude in your local workflows. The skills supported include: + read-file and query – uses DuckDB's CLI to query data locally, unlocking easy access to any file that DuckDB can read. + read-memories – a clever idea to store your Claude memories in DuckDB and query them at blazing speed. These are powered by two additional skills: + attach-db – gives Claude a mechanism to manage DuckDB state through a .sql file linked to your project. + duckdb-docs – uses a remote DuckDB full-text search database to query the DuckDB docs and answer all of your (and Claude's own) questions.

DuckDB

60,694 Aufrufe • vor 4 Monaten