Using a new NPM package that Claude doesn’t have training data for sucks, generally. Even getting it to follow the latest minor version conventions (like in Vue) is difficult. To solve that, what do we usually do? Manually point it to the README, docs, or dist each time. Add rules to your CLAUDE.md (pollutes context and creates a maintenance burden). Trust some random guy who built a “best-practices-skill”. Build our own skill, try to figure out the best practices ourselves, and manually add notes for every bug we run into. As I’m sure you’re all Claude pros, you’ve probably realized the best way to generate a skill is just to give Claude the right context and let it do the work. I built skilld to automate this. From the NPM package alone, it resolves the docs either from GitHub tags for your specific version or straight from doc sites. It pulls data directly from GitHub (release notes, issues, and discussions) and links the dist files. It then asks Claude to generate API changes and best practices based on all of this data to spit out exactly what you need for the version you’re actually using. Try it out, steal the code, do as you please: https://github.com/harlan-zw/skilld npx skilld submitted by /u/loonpwn
Originally posted by u/loonpwn on r/ClaudeCode