Claude Code skills, 8 of 26 clients, and hooks, 4 of 26 clients
51 skills.
Here is one running.
A list is still just a list. So one of them runs here. Paste an n8n expression and the rules out of n8n-expression-syntax tell you what is wrong with it, why, and what to write instead.
Anybody can say they use Claude Code skills. The count below was read off the filesystem by a script on 8 September 2026, along with 15,118 lines of rules across all of them.
What is in the skill it came from
1,485 lines across four files: the rules, a catalogue of mistakes, worked examples, and a short reference. Four of the rules, with what each one costs when it is broken.
webhook data lives under .body
the field is undefined rather than an error, so it fails silently, all the way to whoever received the email
node names go in brackets, in double quotes
it breaks on the first space, and node names almost always have one
a Code node takes no braces at all
the variable holds the literal characters and fails much later, somewhere else
$data was replaced by $json years ago
it is still the top answer on half the forum threads
Four decisions
The number is read off disk, never typed
These were once described as "8" in a proposal when the folder held fifty-one, because the number came from memory. Eight sounds like somebody who tried it. Fifty-one sounds like somebody who runs on it. So a script counts the directories now and writes the count down with the date it counted.
A skill is a rule plus the failure that caused it
The useful ones are not summaries of documentation. Every rule in them exists because something specific went wrong once, and the rule carries that story, so it survives being read by somebody who was not there. The n8n expression skill is mostly a catalogue of mistakes with the cost of each.
The big ones carry files, not just prose
34 of the 51 carry companion files and 18 carry scripts they call. A long prompt tells the model what to do. A skill hands it something to run.
A hook catches what a skill forgets
A skill has to be loaded to help. A hook fires whether it is wanted or not, and that is the point. One here matches any prompt mentioning a proposal or a cover letter, and refuses to hand over client copy until a checklist is ticked. It was written after a job posted six minutes earlier collected fifty proposals while a deck was being rebuilt.
All 51, longest first
Names and sizes only. Several of these are about client outreach, and what they say is not something to hand out.
What this page does not show
The count is a snapshot, committed to the repository, because a website cannot read a laptop. It says when it was taken and the script that takes it is in the repository too. If it is stale, the fix is to run it again.
The checker above is the skill's rules written as code, not the skill itself reading your text. That is the honest version: the rules are the valuable part, and rules that a machine can apply should be applied by a machine.
The endpoint takes the same input as JSON. The daily setup is the rest of it. The n8n estate is where these expressions actually run. The whole list is 41 requirements from 114 job posts.
Craft · Claude Code Skills · 8 of 26 clients asked for it
Need this on your own system?
Tell me what is broken. I will tell you what it takes, honestly, including when the answer is that it is not worth building. The code ends up in your account, not mine.