What is a skill for Claude and what is it for?
A skill is a text file that says how a certain task should be done: the steps, the tone and the known pitfalls. Claude reads it by itself as soon as the task comes up, so the way of working only has to be explained once.
SCHILLER sets up skills together with clients: 30 minutes of getting to know each other for free, then 60 minutes on a real task.
Together we write the instruction your AI tool follows by itself on your task. After that you explain nothing, cut nothing, rewrite nothing. First conversation 30 minutes, free.
Three sentences from people who live this every day. You may recognise yourself in one of them.
I have to get out of word copy and paste into a browser, the section that I want to change and have it done through the browser. Then copy it go back to my Word document. Very inefficient and wasteful of my time.
We take what should be a few bullet points, turn it into some overly wordy bullshit with AI, then the recipient uses AI to turn that wordy bullshit back into a few bullet points.
Often what it produces sounds very AI regardless of the tone you request.
This is not user error. The tool does not know how you work, and you tell it from scratch every time.
66 %
of developers
spend more time correcting AI results that are almost right than they save.
Stack Overflow Developer Survey 2025, over 49,000 respondents
10 %
use AI daily
while 45 percent use it at all. Mostly for summarising and finding ideas, rarely for the actual work.
95 %
of AI projects
in companies deliver nothing measurable. Not because the models are bad, but because they do not adapt to how people actually work.
You write down once how you want a certain task done: in which steps, in which tone, with which pitfalls. A text file, nothing more.
Your AI tool reads it by itself as soon as the task comes up. You no longer add anything.
If a result is not good once, you change the file. From then on it is better every time.
The same notes, plus: as a protocol, please. Back comes a letter full of filler, an invented year and a decision that was none. So: shorter. No filler. Split it. Tomorrow the same again.
You pick the Protokoll instruction and paste the notes. Structure, tone and the rule to invent nothing live in the file. Right the first time, and the mail straight after.
This is not a sample file. This is what the instruction says that I write my own meeting minutes with:
No added year either. If the note says "07.09.", you write "07.09." and ask about the year. A quietly added year is the kind of mistake nobody notices for years.
Rules like that do not come from a desk. They come from something having gone wrong once. That is exactly what we write down for your task, in your hour.
Texts, protocols, reports. Everything that ends up on your desk again anyway.
Whichever you pick: the conversation is the same. You only choose what we talk about.
Step 1 of 3
You pick a time. In the conversation we find the one task where the effort pays off fastest.
Step 2 of 3
One hour after the conversation you get a mail with the offer for the hour together. Exactly one mail. If it does not fit, you do not have to do anything.
Step 3 of 3
We set up your instruction together, on your real task. At the end it works, and you know how to develop it further yourself. For companies and the self-employed.
Step 1 of 3
You pick a time. In the conversation we find the one task where the effort pays off fastest.
Step 2 of 3
One hour after the conversation you get a mail with the offer for the hour together. Exactly one mail. If it does not fit, you do not have to do anything.
Step 3 of 3
We set up your instruction together, on your real task. At the end it works, and you know how to develop it further yourself. For companies and the self-employed.
The format has been an open standard since December 2025. Claude Code, GitHub Copilot, Cursor, OpenAI Codex and Google Gemini CLI read the same file. One limitation you should know beforehand: it works in tools with file access. The plain ChatGPT chat interface in a browser has no such file format, there you only get one general instruction that applies to everything at once.
The file stays with you, not with me. It holds how you work, and that stays in your hands. If personal data is involved in your case, we talk about what that means for you during the free conversation. How we handle data ourselves is in our privacy policy.
The 290 euros are the price for one hour together on one task. For a team it does not add up per head: an instruction that exists once applies to everyone who works with it. What makes sense in your case we clarify in the free conversation, before anyone books anything.
For a single task, often yes, and then you should do that. The difference shows when it becomes several tasks: a snippet has to be pasted by you, and most tools allow only one general instruction that then applies to everything. An instruction file only applies to the task it was written for. Whether that is worth it in your case we will tell you honestly during the free conversation, even when the answer is no.
Then I say so in the free conversation and we stop there. I do not sell an hour I believe will not help you.
Rather write or talk first? To the contact form
