Are MCPs already old news Ryan Carson makes the...
I saw someone in the chat ask, are skills equivalent to MCP or use it behind? Or are they the new MCP? I think we're still in a world where a few things should be MCPs. But overall, I would say skills are becoming the new MCPs. They're more portable. They're easy to use. They're just text, you know, and you can literally check them into Git. So all of my skills are in my home directory, my .agents folder and my skills folder. And then I've created a Git repo, and then I just got a new MacBook, for instance. And then I just cloned that repo locally. And all of a sudden, magically, I had my skills again. That's the benefit of GitHub. For people who don't know, GitHub is basically taking the Git tree functionality that Ryan was just talking about and putting it on the cloud. And you can download it and manage it that way.
Summary
Ryan Carson discusses the shift from traditional MCPs to skills as the new focus in AI. Skills are more portable and manageable through Git, enhancing practical use.
Key Points
- Skills are becoming the new MCPs in the tech landscape.
- Skills are more portable and easier to use than traditional MCPs.
- Users can store skills in Git repositories for easy access.
- GitHub allows for cloud management of skills and repositories.
- The transition focuses on practical capabilities of AI.
Tags
Repurpose Ideas
- LinkedIn post: Why skills are the future of AI.
- Tweet: The benefits of using Git for AI skills.
- Checklist: Setting up your skills repository on GitHub.
Save videos. Search everything.
Build your personal library of inspiration. Find any quote, hook, or idea in seconds.
Create Free Account No credit card required