Crediting open source inside a skill you ship
If a skill ships someone else's code, their licence and credit go with it, visibly. How to do that properly, and when recommending a tool beats bundling it.
Skills are often built on top of open source. Doing that fairly is simple and non-negotiable: if their code ships, their credit ships with it.
If you include their code
- Keep their licence file and copyright line in the package.
- Credit them where people will see it: the README and the product page.
- Never describe their work as yours, or imply they endorse you.
Or recommend instead of bundling
For ui-ux-pro-max, an MIT-licensed project by nextlevelbuilder, we ship none of its code. Our skills explain how to install it from its own repository and credit it clearly. Users get the tool from its author, under its author's terms. How the two work together is in using ui-ux-pro-max with a design skill; licensing more broadly is in choosing a licence for a skill.
Questions
What does attribution usually require?
Most permissive licences require keeping the original copyright notice and licence text with the code. Many authors also appreciate a visible credit and a link.
Is reading open source for ideas the same as using its code?
No. Learning an approach from a project is different from copying its code. Once you copy code, its licence applies to that code.
Can I recommend an open-source tool instead of bundling it?
Yes, and it keeps licensing simple: users install it from its own source under its own licence, and your product credits it without shipping it.