← All IntelClip / EducationSkill pickup and conflicting skills
From Full Walkthrough: Writing & Using Skills — Nick Nisi and Zack Proser · ≈31:02
Names the scaling failure of skill libraries and the practical mitigations: broad descriptions stuffed with the relevant acronyms, or explicitly invoking the skill by name or slash command.
What’s in it
- Names the scaling failure of skill libraries and the practical mitigations: broad descriptions stuffed with the relevant acronyms, or explicitly invoking the skill by name or slash command.
Clip transcript
Right. Uh skill pick up. Uh so, if you get lots of skills, uh the models might ignore a skill or decide I don't need a skill. I'll just I'll just do it. What's your kind of experience with this to A like tested, find it, and then maybe improve it? >> Yeah. Um great question. We That that is a problem, and the more skills that you get like you can have conflicting skills. Uh and so like which one is it going to pick? Um the solution to that like like for the Work OS one specifically like we try and keep it like for these public ones we try and keep it like very generic like mention all of the you know the the acronyms and things that we would want we would expect to cover uh from that. So, that'll trigger it to load. Uh and it usually does a pretty good job. You can also like if you're in a skill uh or sorry, in Claude, uh you can just do like Work OS for example like the slash command uh if you know that you want to do it. And so like a lot of times we'll just like suggest, you know, if if that's what you want, I'll say like just run slash Work OS and it'll it'll load it. >> I'll I'll I'll call a skill by name if I want a specific like image gen or something. I'll say or I'll say like use the superpower brainstorm skill in order to determine a better plan. >> Yeah. >> Yeah. Yeah. But also if you got if they really wasn't behaving, that's why you use the bang and then put a command. >> Right. >> Yeah.
Comments
Sign in to comment.
Loading comments…