Matteo Collina's Skills
Node.js skills from a Fastify co-creator: Node and Fastify practices, TypeScript, OAuth, linting and documentation
- 1,961 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skills consist of instructions and reference rules
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/matteo-collina-s-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills consist of instructions and reference rules
This is third-party code. Review the repository files before installing.
What it does
A personal skill set from Matteo Collina, Node.js TSC member and Fastify co-creator. The fastify and node skills cover server development practices, while nodejs-core digs into Node internals: V8, libuv, native addons and builds. There are skills for advanced TypeScript types, OAuth 2.0 and 2.1 specs with Fastify integration, linting with neostandard and ESLint 9 flat config, and git and GitHub work through gh. It also includes a Diataxis documentation skill, an AGENTS.md generator and a skill for improving other skills' activation.
Who it is for. For Node.js and TypeScript developers, especially those building servers with Fastify.
Good fit when
- The agent builds a Fastify or Node.js service
- You need OAuth implemented to spec rather than by guesswork
- You need to remove any from complex TypeScript types
Not a fit when
- The project is not on Node.js
- You want a one-command install: the README has no install instructions
Example request
Add OAuth 2.1 with PKCE to the Fastify service and check it follows the specLimitations
The README lists skills but not installation, so folders must be copied manually. Guidance reflects the author's views, such as choosing neostandard for linting.
How to disable. Delete the copied skill folders from the agent's skills directory.
FAQ
How is each skill structured?
Each folder has a SKILL.md with triggers and instructions, and detailed rules live in separate rules/ files.
Discussion
No questions or reviews yet.
Related
SkillsThe official FastAPI skill, bundled with the package, teaching agents to write code for the installed version
Better Auth skills
Better Auth Skills
Official Better Auth skills: scaffold authentication in JS and TS projects and guide a secure setup
Go skills by samber
cc-skills-golang
Over forty Go skills: style, errors, concurrency, testing, security, performance and popular libraries
Three skills for TypeScript logging: review code and move to wide events, build an audit trail and analyze local logs
The official Payload CMS skill shipped inside the package: collections, fields, hooks, access control, queries and database adapters
Skills for Java projects: code review, Spring Boot, JPA, concurrency, Java version migration, Maven audits and security
README in short
The README is short: a table of eleven skills with one-line descriptions and links to a cross-model skill benchmarking workflow and its run history. There are no install instructions; skills follow the standard skills/<name>/SKILL.md layout. MIT licensed.
README badge
Original SKILL.md
--- name: documentation description: "Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing." metadata: tags: documentation, technical-writing, tutorials, guides, reference, diataxis --- ## When to use Use this skill when you need to create, review, or improve technical documentation following the Diátaxis framework. Examples include: - Creating user guides - API documentation - Tutorial content - Restructuring existing documentation to better serve different user needs and contexts ## Instructions Organize documentation into four distinct types — tutorials, how-to guides, reference material, and explanations — each serving different user needs and contexts. Always ask clarifying questions about the user's context, audience, and goals **before** creating documentation.