Skills
These are the agent skills I actually use. They live in EddyVinck/skills and this page is generated from that repo, so what you read here is what you install.
Not sure where to start?
/ask-eddy is the router over everything else. Describe the situation you are in and it names the one skill that fits, and why. It changes nothing in your repo, which is what makes it cheap enough to run whenever you are unsure.
User-invoked and model-invoked
Every skill below sits on one side of a single axis, and it is worth knowing which before you install anything.
- User-invoked
- Reachable only when you type them. The agent will not pick one up on its own. Their job is to orchestrate — to decide what happens next and in what order.
- Model-invoked
- You can type them too, but the agent can also reach for them by itself when the task fits. These hold the reusable discipline — the part you want applied consistently whether or not you remembered to ask.
Two ways to install
Both work. They differ in who owns the copy you end up with, so pick on that basis rather than convenience.
Copy them into your project
npx skills@latest add EddyVinck/skills The skills land in your repo as ordinary files. Nothing stops you editing them, and nothing will overwrite your edits — they are yours from the moment you add them.
Install them as a managed bundle
/plugin marketplace add EddyVinck/skills /plugin install eddyvinck-skills@eddyvinck The skills stay read-only and outside your repo, and they update when I ship. You trade the ability to hack on them for never having to re-sync them by hand.
Engineering
Daily code work.
User-invoked
-
ask-eddy
Ask which skill or flow fits your situation. A router over the skills in this repo.