I try to keep my collection of community skills short, usually a few established names (mattpocock, mcollina, trailsofbit). And then I check new releases (or when mattpocock published a youtube video for instance :D)
> keep them organized
For skills I wrote myself, I have my own private github repo. I use skills like /commands most of the time, so I can tell if they work straight away.
For community skills, a package manager really helps. vercel-labs/skills and withastro/rosie are good options. I also built one myself: https://github.com/osrim/ski. It has some cool features like an update command and a security scan.
Seems too easy :D I can see how this gets you up and running with a twin env on a simple stack, I have more questions about the enterprise setup: I couldn't find much on cloud services, does it emulate AWS services like s3/SQS?
"you probably shouldn’t let it write it for you if you actually expect the rest of us to read it." definitely resonates with me.
Where I kind of disagree is that I don't think most readers will revolt. I think the mountain of LLM slop has actually changed people's behavior in more ways than one. Some are already relying on LLMs to summarize articles: then it doesn't matter to them who wrote it, they're just consuming machine-condensed content with no way to tell if a human or an LLM wrote the original piece. Or if their summarizer hallucinated.
I try to keep my collection of community skills short, usually a few established names (mattpocock, mcollina, trailsofbit). And then I check new releases (or when mattpocock published a youtube video for instance :D)
> keep them organized
For skills I wrote myself, I have my own private github repo. I use skills like /commands most of the time, so I can tell if they work straight away.
For community skills, a package manager really helps. vercel-labs/skills and withastro/rosie are good options. I also built one myself: https://github.com/osrim/ski. It has some cool features like an update command and a security scan.
reply