AUTOMATION

What are Claude Skills?

𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 was never meant to hold entire workflows.

But that's exactly where they end up. General rules, coding conventions, 20-step security review processes, deployment checklists. All in one file that loads into every single session, eating… https://t.co/fCLQezp4lG pic.twitter.com/VPLfFEYrTR

— Akshay 🚀 (@akshay_pachaar) 29 mars 2026

What are Claude Skills? 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 was never meant to hold entire workflows. But that's exactly where they end up. General rules, coding conventions, 20-step security review processes, deployment checklists. All in one file that loads into every single session, eating context even when Claude is just renaming a variable. 𝗦𝗸𝗶𝗹𝗹𝘀 fix this by turning workflows into self-contained packages that Claude loads only when the task demands it. Here's the idea. A skill is a folder inside .𝗰𝗹𝗮𝘂𝗱𝗲/𝘀𝗸𝗶𝗹𝗹𝘀/. Each folder contains a 𝗦𝗞𝗜𝗟𝗟.𝗺𝗱 file with two things: a 𝗱𝗲𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻 that tells Claude when to activate it, and the workflow instructions that tell Claude what to do. The description is the trigger. Claude reads all available skill descriptions, watches the conversation, and when your request matches, it pulls in that skill automatically. You don't paste the steps. You don't type a command. Claude recognizes the intent and invokes the right skill on its own. You can also trigger any skill explicitly with a slash command like /𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆-𝗿𝗲𝘃𝗶𝗲𝘄 when you want manual control. I recorded a deep dive on skills when they were first released, and everything in it is even more relevant today. The video below walks through exactly how this works. But auto-invocation is just the surface. The real power is what skills can carry with them. Skills are full packages, not just instruction files. A 𝗦𝗞𝗜𝗟𝗟.𝗺𝗱 can reference supporting files that live right next to it using the @ symbol. A detailed security standards document. A release notes template. A compliance checklist. Whatever the workflow needs, the skill bundles it together. Inside 𝗦𝗞𝗜𝗟𝗟.𝗺𝗱, YAML frontmatter defines the name, description, and which tools the skill is allowed to use. The 𝗮𝗹𝗹𝗼𝘄𝗲𝗱-𝘁𝗼𝗼𝗹𝘀 field is worth paying attention to. A security review skill only needs 𝗥𝗲𝗮𝗱, 𝗚𝗿𝗲𝗽, and 𝗚𝗹𝗼𝗯. It has no business writing files. Restricting tool access makes the skill safer and far more predictable. Skills live at two levels. Project skills go in .𝗰𝗹𝗮𝘂𝗱𝗲/𝘀𝗸𝗶𝗹𝗹𝘀/ and get committed to git so the whole team shares them. Personal skills go in ~/.𝗰𝗹𝗮𝘂𝗱𝗲/𝘀𝗸𝗶𝗹𝗹𝘀/ and follow you across every project. A 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 with a 20-step security process baked in is dead weight in 90% of your sessions. A 𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆-𝗿𝗲𝘃𝗶𝗲𝘄 skill that activates only when security is on the table is precision. 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 tells Claude what rules to follow. Skills tell Claude what workflows to execute. The article below is a complete guide to 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱, hooks, skills, agents, and permissions, and how to set them up properly. Akshay 🚀 (@akshay_pachaar) x.com/i/article/203496196714… — https://nitter.net/akshay_pachaar/status/2035341800739877091#m

→ View original post on X — @akshay_pachaar, 2026-03-29 10:13 UTC