핵심 요약
MCP에 버금가는 게임체인저인 Claude 스킬(에이전트 스킬)이 무엇이고 왜 중요한지 설명하고, 오늘 바로 즉시 성과를 내는 사용·제작법을 18분 안에 정리한다.
주요 포인트
- 스킬은 'Claude에게 작업 방식을 가르치는 재사용 지침 매뉴얼'로, 컨텍스트에 따라 어디서나 자동 실행됨. 프로젝트 커스텀 지침과 달리 이식 가능(portable)하고 쌓아 쓸 수 있음(stackable)
- 생태계 구분: Claude=두뇌, 스킬=지침 매뉴얼, MCP=외부 도구, 프로젝트=이들을 결합하는 작업 공간. 경쟁이 아니라 함께 쓰는 빌딩 블록
- 스킬 3종류: 공식 스킬(설정의 capabilities에서 code execution·file creation 켜고 필요한 것만 활성화), 커스텀 스킬(skill-creator로 비개발자도 제작), 커뮤니티 스킬(보안 주의). 자동 트리거가 불안정하므로 계정 레벨 커스텀 지침에 '관련 스킬을 항상 고려하라'를 추가 권장
- 커스텀 스킬 제작 3가지 방법: ① 공식 스킬을 확장(예: 브랜드 템플릿으로 branded deck), ② 기존 워크플로/프로젝트를 스킬로 패키징(MCP 도구는 꼭 필요한 것만 선별), ③ 여러 스킬을 처음부터 만들어 프로젝트에서 MCP와 함께 사용
- 스킬이 필요한지 판단하는 3가지 질문: 같은 지침을 3번 이상 반복하는가, 실제 사람을 교육해야 할 과정인가, 매번 품질·형식 일관성이 필요한가. MCP 도구 변경에 대비한 백업 플랜을 넣고 한 스킬에 도구를 너무 많이 쓰지 말 것
Claude skills or agent skills. This is something I have been waiting for a long time, and honestly, I'm so excited because these has a huge potential and such a game changer, just like MCP in changing how we design AI workflows or AI agents. And not just within Claude, other AI models might likely adopt similar concepts. So in this video I explain what skills actually is, why this is another game changer, and most importantly, how you can start using them today to get immediate results. Let's go. So what is Claude skills? Really, the official definitions is very confusing. The easiest way to think of it is reusable instructions manual that Teach Claude how you want task to be done, what tools to use, what standard to follow so it execute automatically anytime, anywhere when you need it. Before Claude skills. When you execute repetitive tasks like writing, marketing, emails that follow your brand voice or process, you will have to repeat the same instructions in every single chat. This is inconsistent and time consuming. Now, you might be think, just use a Claude project with custom instructions, right? Yes, 100% and this is what most people are already doing, but there are still two fundamental limitations. First, these instructions are not portable. Imagine next time when you're doing another campaign, you either have to execute inside this project or you repeat all the instructions again. And second, it's not stackable. Imagine you have a specialized project for copywriting and other project for campaign analysis. You can't just combine them together for a new task. They operate in complete isolation. And so you have to build so many different projects, which might actually end up with overlapping workflows. And that's why the solution Claude skills. So instead of embedding all these workflow instructions and resources inside a project, you extract them out and package them into what they call the fancy term skills and make them available at the account level, including the web app, Claude code, or Claude API. So once you understand this, you can have so many kinds of user manual, perhaps an email writing manual, market research manual, design template manual, and they can be used all together as well. And that is why this is a game changer, as now you have way more flexibility and portability of these skills for your workflow or agent design. Now another big confusion is between skills and MCP and projects. And someone might tell you skills is just Anthropic's way to fix the MCP problems. And this is a big misconception. If you view it under the lens of Claude's, ecosystem, Claude itself is the brain. The core intelligence that make decisions. skills are the instruction manual, the reusable instructions for how specific tasks should be done. MCP provides the tools, the actual capabilities to do things outside of Claude's knowledge, like creating a file, calling a database. Projects are the dedicated workspace where you can combine skills. MCP tools and background knowledge for specific ongoing work. And this is exactly what makes this Claude ecosystem so powerful. You can mix and match based on what your specific workflow needs. Not every workflows needs all these components. They are not competing. They are building blocks and are designed to be coexist, to build powerful workflows or agents. Basically there are three types of skills you can use with Claude. For this video demo, I'll be using the Claude web application. First, the official skills by Antrhopic these are ready to use skills built right inside Claude. Just go to settings under capabilities here. You will control what capabilities Claude will use in the chat, but first you have to make sure code execution and file creation has been turned on in order to use skills. Then you will see a list of predefined skills. I do not recommend you turn them on all at once. Just pick the one that you are really gonna use, because more skills might confuse Claude when executing the workflow. Besides the official skills created by Anthropic, they're also skills created by Anthropic's partner like Notion. So you can check out the official GitHub repository and scroll down to partner skills where you can download the skills and use them on Claude so I will put the link in the description. And second custom skills. So these are your own creation. It can be your own workflow instructions, resource template, or even coding script. You prepare your own skill file according to the official format, and you activate them by uploading the skill file. You can also turn on and use the official skill called “skill-creator” to create your custom skill if you’re a non-technical. This is how you personalize Claude to your way of working, and I'll show you how in just a minute. Third is Community-created skills. So there is also a growing ecosystem of skills created by other Claude user, but you want to be cautious about security when using these community skills. **** And