Skills are becoming a problem. Not because they don't work. But because they're so effective. I'm now seeing teams (on the buyside) where individuals have a 5-20 skills. They work and they're used often. But here's the problem. Skills are still stuck in single-player mode. How do you share a skill? Email me the .md file. (And piss off, if it's a zip file.) Then the models change and Claude recommends shrinking skills by 80%. The power users do it. No one else received the memo. (Duh, they're not on X all day.) Some skills are centralized. Do we really need 20 review-nda skills? One person should own this, make sure it's always dialed-in. But who is that person? How do you ensure that everyone has the most up-to-date skill? (And what happens if that person leaves?) Other necessary items: Version control, ownership, search-ability and discovery, descriptions. Pretty easy stuff, but not available in the current harness. And don't get me started on testing. Right now it's all based on vibes. (I'm guilty of this too.) It's hard to run evals on qualitative knowledge work. Don't tell me git. That proves you've not understood how the average knowledge worker operates. They will NEVER use git. EVER. Who's building the solution?