how to organize your Claude Skills

Let's tackle something I've been putting off. Updating my Claude skills. I use Claude for technical work and creative work, but I treat them very differently. For technical work, I have my agents. They have their own skills, but for creative work, I still do a lot of prompting. I'm using AI to help accelerate, not outsource my creativity. My creative skills are so a mess right now. So here are a few updates I made. First, I created two dedicated top-level skills: a brief skill and a brand skill. These are my mini managers. When another skill has a question about me, my voice, my tone, how I make decisions, it will go to one of them first. It's one additional layer of context on top of the project, so I don't have to repeat myself. Second, create skills to run workflows. Hierarchy. I built orchestration patterns around single tasks that orchestrate everything. Let's think about something like analytics. I have one skill that can look at my goals, another one that can grab the analytics and a third that can actually make sense of the analytics and generate a report. Each one has a specific task with different context in mind. This allows me to have leaner skills so they perform better. And third, make sure skills are self-healing. Your skills are living documents and should be treated as such. You change your processes, change. And when you don't update them, they get stale. So I created a skill that runs at the end of every session, pulls out any new information about how I work or how I make decisions, and then uses that information to update the relevant skills accordingly. They stay current, so I don't have to think about it. I'm shifting my creative skills to look a little bit more engineering, but still with a lot of space for me to remain in the loop. If you want me to break down any of these patterns I talked about in more detail, let me know in the comments below.