skills-npm

Clear and concise description of the problem While the proposal of building the skills into the NPM package is great, it will take time when all package maintainers add this. But people want to add all skills as dependencies already now. Suggested solution For now, the service https://skills.sh/ already provides a lot of skills, and is quite popular. But its approach is to download skills once and place it into the git repo, which will go to production with all that garbage. So, would be great to extend the package to support downloading and managing skills from the https://skills.sh/ too, together with other skills, bundled in NPM packages. Alternative _No response_ Additional context _No response_ Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Clear and concise description of the problem Summary In a pnpm monorepo, only seems to discover skills from dependencies declared in the workspace root . If a package that ships skills is installed in a workspace package's , running from either the root script or the workspace package's script does not discover/install the skills. Moving the same dependency to the root makes discovery work. Reproduction Given a pnpm workspace like this: : Root : Workspace package : ships a skill under: Then run: or manually: I also tried adding a script inside and running install from there, but the skill was still not discovered. Actual behavior No skill from is discovered or symlinked when the dependency is declared only in the workspace package. If I move to the root , discovers and installs the skill successfully. Expected behavior should be able to discover skills from dependencies declared in workspace package manifests, not only from the root package manifest. Suggested solution NOP Alternative _No response_ Additional context _No response_ Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Clear and concise description of the problem The recommendation of the current approach is to add skills as files to each NPM package. But these skill files are not needed in the production build at all! So, with bundling skills to the main packages, we are just wasting resources on production servers with no benefits. Suggested solution A good solution will be installing skills as dev dependencies, so as not to bring these files to the production builds. This approach seems not easy to implement, because it will require building separate packages with skills and without skills, but if we found a simple solution for this, it will be a good improvement of the whole approach! What do you think about this idea? Alternative _No response_ Additional context _No response_ Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.