← All notes
Active November 2026

Skills and plugins

Skills are packaged instructions Claude loads when a task calls for them. Which ones I use, which I do not, and what my usage report suggested.

Claude CodeSkillsPlugins

What a skill is

A skill is a folder with a markdown file of instructions, and sometimes scripts and reference material. Claude sees only the short description of each one, and loads the full text when the task matches. It is the right tool for “here is how we do this, every time”.

What I actually use

Plugins

Plugins bundle skills, commands and agents, and there is a catalogue to browse from the app. I look at it, but my daily work does not depend on any of them.

The ones I wrote

My home network used to be described in a single instruction file loaded in every session, even when it was not needed. On 19 November I split it into skills, one per topic (the container server, mail, the main NAS, the router, the PC with local AI, the remote house network): the global file keeps a short map and the detail loads only when the work calls for it. There are also skills for repeated procedures, such as updating one of my projects on the server, renewing a certificate or adding a device to monitoring, and one with my rules for building websites. One rule still has a fixed place in the global file: the one on the safety of the shared server, because it must hold even if the skill is not loaded.

What I have not done yet

The rituals I ask for most, update the memory and commit and push, are still only words; the release procedures, on the other hand, are already skills in some of my published projects.