Skills Hub guide
Choose a skill for the actual job
Compare the task, source and requested access before choosing a reusable skill.
Start with fit, then inspect trust and maintenance
Search for the specific workflow you need, not only a popular tool name. Read the actual instructions and upstream source. Check which version was reviewed, whether it has changed and what the runtime must provide.
- Task fit: a recognizable input and useful output.
- Provenance: the upstream repository, version and license.
- Review state: passed, held or incomplete, with its meaning.
- Runtime needs: tools, packages, permissions and network access.
Compare two document-review skills
A longer skill is not necessarily a better fit. Check the scope you need to delegate.
For each candidate skill, record whether it only reviews a supplied document or also modifies files. Note the required tools, external network destinations, license and reviewed version. Prefer the smallest scope that completes this task. Test it first with non-sensitive sample material, and inspect both its proposed changes and unexpected actions.
Popularity cannot replace inspection
Downloads, stars or inclusion in a library do not establish that a skill is suitable for your environment. A previous review may not cover a changed package or a new dependency.
Common questions
Should I use a library skill or generate my own?
Use a reviewed library skill when its scope and behavior fit. Generate or adapt a skill when the task has specific requirements, then inspect and test that result too.
Sources and review
Reviewed