Install
https://github.com/mcollina/skillsWho it is for
This fits people doing AI-assisted development whose task already lands on the few skills named in the source. The official title is Matteo Collina’s skill set, and it says: Skills for AI-assisted development. The repository blurb points at modern Node.js development, but the body table names only four rows; do not expand it into a complete framework inventory.
It fits better if you already write Fastify, already have a repository note to maintain, already touch Node.js internals, or are handling complex TypeScript types. It does not fit people still looking for an install command: the source cited on this page gives no npx, plugin marketplace, or other installer.
Before you start, open the official repository and confirm you will use a name from the table. Do not invent skill paths or install commands.
First try in 3 minutes
Use only the path the source actually gives: the official repository itself. The first time, do a read-only check; do not generate or overwrite repository files yet.
Prerequisites: you already have a local Node.js / TypeScript project, or you can already load this skill set in an assistant. If the skill has not appeared, stay on the repository page; do not invent install steps.
Install location: the source has no install command. The official place is the repository:
https://github.com/mcollina/skills
Low-risk trigger: if the skill is already available, ask the assistant for a read-only check along the fastify row — the source says Comprehensive best practices for Fastify development. Only check whether existing code drifts from those practices; do not change files yet. If the skill is unavailable, the success condition is not met; do not switch to an installer that was never named.
Success signal: the assistant discusses existing code explicitly against fastify best practices and does not change the disk. If you see it start writing AGENTS.md or other files, stop and confirm first.
Usage examples
Example 1: Check Fastify best practices. Use fastify from the table. It fits people who already have a Fastify service and want to compare it with comprehensive best practices. The evidence is only that one sentence; it does not list concrete rules. Check read-only first; if you will change route or plugin code, confirm which files first.
Example 2: Tighten TypeScript types. Use typescript-magician: the source says it focuses on advanced type systems, complex generics, and removing any. It fits people whose types are already messy and who want to find any first. Produce the check result first, then decide whether to change type definitions. Do not turn it into type-filling for an arbitrary language.
Limits
The source has no install command. Do not add npx skills add or other marketplace commands. The only official place you can give is:
https://github.com/mcollina/skills
The table also names init: create and maintain a high-signal AGENTS.md for a repository. That writes a file; before you run it you must confirm the target repository and whether an existing note will be overwritten.
nodejs-core covers Node.js internals, including C++ addons, V8, libuv, and the build system. The evidence stops at those topics; there are no operation steps. Do not treat it as a general Node introduction.
Do not invent skill names outside the table. The source also gives no exclusive assistant roster and no mutually exclusive language scope.