ZH version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 369 words in the discussion.
Trending Topics
#skills#specific#suite#sure#learned#every#agent#https#github#artrichards

Discussion (6 Comments)Read Original on HackerNews
For example, you could just put “always follow TDD” in there. If you want to be very complete you could add “first write tests and make sure they’re red before continuing to code. Make sure tests are green on completion”.
Skills are useful for calling specific scripts, adding specific data (like branding info) or detailing truly unusual, bespoke workflows (like the use of cutting-edge machine learning algorithms you’ve developed yourself or something). If you’re detailing something like TDD, you’re probably hampering the model by giving it a definition that is less accurate than the one it has learned in training.
It turns out productivity skill sets for Claude are a bit like opinions and assholes (everyone has one, and ...)
I mean, just to give you an idea of how common this is, my CEO made a suite like this ... although he had the self-awareness to realize what he made was very specific to him.
I love reading them to see if theres a way mine could be improved, what topics they hit on, how they approach different problems.
https://github.com/ArtRichards/agent-playbook-suite
https://artrichards.github.io/agent-playbook-suite/blog/
https://github.com/ArtRichards/docs-cli
I've personally learned from reading his skills.
Trying to start with these preset banks of instructions just never seems like it works out in the long run. It’s also unsettling catching it behaving in an odd way, and realizing that it was taking a cue from instructions you never wrote, but imported from elsewhere. Like playing a game of pretend with someone else’s rules.