There are things that are asked of the chat almost every day and almost always in the same way: replying to an email with the house tone, chasing an invoice that is twenty days overdue, turning meeting notes into minutes with assignees and dates. Every time it is requested, you have to explain how you want it all over again. And every time it comes out slightly different.
Skills is the NAiOS module that solves this. A skill is a well-explained task: when it is used, how it is done, and with what rules. It is installed once and the chat applies it when needed, without having to repeat it.
What is a skill
Technically, it is a text file called SKILL.md: a short description that says when to activate it and instructions in plain language that say how to do the task. There is no code. There is nothing to execute. They are the same instructions a team member would give to a newcomer, written once and always available.
This format is open and is the same one used by Claude, ChatGPT or Gemini skills. A skill written for NAiOS can be downloaded and taken to another tool, and a folder of skills from another tool can be uploaded to NAiOS as is. We felt it was important not to invent our own format for something that the user should be able to take with them.
What the user finds
Upon entering Skills, there is a catalogue with 52 NAiOS skills in ten categories: writing and tone, documents and presentations, sales and CRM, invoicing and accounting, meetings, legal and GDPR, human resources, training, data and spreadsheets, and support.
Two come active from day one. My company's tone ensures that everything the chat writes comes out with the style, words and signature of the company; the first time, it asks how things are written in-house and remembers it. Reply to emails drafts the reply to an email according to the situation: follow-up, claim, thank you, bad news.
The rest are recommended based on the modules each person uses. Anyone with Invoicing will see Chase an overdue invoice, which does not invent amounts: it consults the actual outstanding invoices in the ERP and escalates the tone based on the days overdue. Anyone with CRM will see Follow-up after a meeting. Anyone who provides training will see Lesson from a document and Exam from content.
How it is used in the chat
Most of the time, you do not have to do anything. The chat knows the list of active skills and, when the request matches one, it loads its instructions before replying. The reply carries a tag saying which skill has been applied, with a link to its card, so you always know why it turned out that way.
When you want to force one, simply type a slash at the beginning of the message. The list of active ones appears, ordered by those most used; typing a few letters filters it, and if what you are looking for is not active but exists in the catalogue, it is offered right there with a button to activate it and keep typing.
Company skills
Here, for us, is the most useful part. Anyone can create their own skill in three ways: by answering four questions (what task, with what phrases it is activated, what output format, what rules) so that the AI drafts the draft; with a three-field editor; or by uploading a folder or a zip with the SKILL.md file. Prompts that someone already had saved are converted into skills with a click.
And a company manager can publish skills for their entire team. An accounting firm or advisory firm that explains once how to chase an invoice from its clients, with its tone and deadlines, has the entire office chasing them the same way from that moment on. A sales department that sets how a proposal is written no longer depends on who writes it. When someone improves a skill, the new version is registered and previous ones can be consulted.
If a company skill is good, it can be proposed to NAiOS. The team reviews it and, if it enters the catalogue, it does so under its author's name.
Some use cases
- Accounting firm or advisory firm: chase overdue invoices with ERP data, prepare the quarterly closing, explain an entry to a client who is not an accountant, register a complete new client.
- Sales team: proposal with the house format, follow-up after each meeting, reactivation of clients who haven't ordered for months, answers to frequent objections.
- Human resources: job offer, onboarding plan for a person, internal communication, performance evaluation with a fixed structure.
- Training: lesson and exam from a document, evaluation rubric, script for a training video.
- Support and operations: reply to a ticket, process checklist, incident to a supplier, FAQs from documentation.
- Agents: an agent can be assigned skills. An agent that drafts emails or chases invoices does so the way the company wants, not how the model sees fit.
In the six languages
The 52 NAiOS skills are in Spanish, English, Catalan, French, Portuguese and German. The catalogue, the card and the chat use the language of each person, and the download includes all versions. The skills created by a user or a company remain in the language in which they are written. The audio guide for the module, for the moment, is only in Spanish.
How it was made: a module in a day
Skills was developed by NAiOS Labs at the request of the CEO of NAiOS, who arrived with a simple question from a colleague: ChatGPT, Claude and Gemini already have installable skills, is it very complicated to have them in NAiOS? The first complete version was ready in four hours of work. Not because it was written quickly, but because the process was thought out before writing a line. We are sharing this because it is the same process we apply when we build for a client, and because it is more like a kitchen than a factory.
- Receiving the order. First of all, understanding what is really being asked for: skills for general users, not for developers; with a catalogue, categories and an initial assortment comparable to the competition.
- Conceptualisation. A phased plan with what goes in and what stays out, a visual sketch of how a skill is installed and a comparison with screenshots of the three platforms to decide on names, tabs and gestures.
- HarnessHarnessThe infrastructure around the model that turns it into an agent: loop, tools, context, permissions and traces. Before cooking, defining how the dish will be tested: automatic tests for each phase, a driver that runs the application and takes real screenshots, a judge that scores each skill in the catalogue and language guards that prevent untranslated text from entering.
- Construction. The phases, one after the other, with tests passing in green before starting the next one.
- Testing. Everything together locally, with screenshots of each screen and the conversation, before thinking about uploading it.
- Plating. A single delivery, with backup and rollback prepared, to one platform first. The rest, when that first one has served for a few days.
This way of working is what we described in the agent multiplies what you already know: the agent provides the speed and the person provides the direction and the final check. An entire module in a day is possible when the harness is in place before the code.
What remains to be done
Skills is available from today in NAiOS. The 52 factory skills have been written by the team and passed by an automatic judge, but the business review, by the people who chase invoices or provide training every day, is what will truly fine-tune them. If you use NAiOS and miss one, create it, test it and propose it: that is how the catalogue will grow.
