Skills

A skill is a ready-made instruction for one kind of work. It turns "build me a knowledge base" from improvisation into a tested process: which questions to ask, in what order to work, which files to create, how to check the result.

#How the agent uses skills

Every skill has a short description: what it does and when it is needed. The agent sees the descriptions of all skills in the current project (or the orchestrator) and, when a task fits, opens the full instruction and follows it. You do not have to call a skill specially.

To launch a skill explicitly, write /skill:skill-name in the chat, for example /skill:doc-templates.

#Ready-made skills and cards

The new-chat screen shows quick-start cards. Each card is a ready-made skill: press it and the agent starts the work right away, asking a couple of questions if it needs to. Most cards create a project of their own; "Business AI system" and "Your own Telegram bot" work in the orchestrator.

All ready-made skills are in Settings → Skills → Bundled Skills Catalog: install them into the orchestrator or any project with Install. Each one is described in Skill catalog.

Installed ready-made skills update themselves when we improve them — unless you have changed them by hand. Eggent leaves an edited copy alone.

#Uploading a skill from a file

If you already have a skill as a file — one you wrote yourself, got from a colleague or downloaded — put it into the workspace without the agent: Settings → Skills → Upload skill. Choose the orchestrator or a project at the top right (the skill is installed wherever the selector points), then drag files onto the dashed area, or press it and pick them. Several files can go at once; each gets its own answer.

What can be uploaded:

• a .md file — a SKILL.md that starts with a YAML header holding name and description;
• a .zip or .skill archive — the skill's folder, with SKILL.md at the top of the archive or inside one folder, and whatever else the skill needs: scripts/, references/, assets/ or any other folders. (A .skill file is the same ZIP archive under another name.)

The file is checked before anything is saved. If a check fails, nothing is installed and nothing stays on disk, and the answer says what is wrong and where — that SKILL.md is not found (and where it was found instead), that the header is not valid YAML on line 3, that the name is not allowed, that an entry in the archive is a link or climbs out of the skill's folder. What is checked:

• SKILL.md exists, is UTF-8 text and starts with a YAML header; name is lowercase letters, digits and single hyphens (up to 64 characters), and description is not empty (up to 1024);
• file names stay inside the skill's folder, there are no links or special files, and the archive has no password;
• the upload is at most 30 MB, and the skill at most 600 files and 30 MB unpacked.

The check is about structure. What a script does is not checked, and the agent can run a skill's scripts, so upload only skills you trust.

If a skill with that name is already installed, it is not overwritten: the answer says so and offers Replace. Replacing puts the new skill in place and moves the old folder to skills/.replaced/ instead of deleting it, so what you added to it by hand is not lost. To get rid of the old one instead, delete it first (see Installed skills).

A skill the agent wrote itself carries the line origin: learned in its header. When you upload such a skill — say, one downloaded from another workspace — the line is removed and you are told: from then on the skill is yours, and the agent will not change it.

#Installed skills

Settings → Skills lists the skills installed in the selected scope (orchestrator or project). Click a skill to read its instruction.

A skill works only where it is installed. An orchestrator skill is not visible in projects, and the other way round — except skills the agent wrote itself, which are available everywhere (see Skills the agent writes itself).

To remove a skill, press the trash icon at the end of its row and confirm. The skill's folder is deleted with everything in it, together with any earlier versions kept when a replacement put them aside (skills/.replaced/). This cannot be undone: a skill that exists only here is gone for good. A skill from the catalog can be installed again, and one you uploaded can be uploaded again. Deleting also frees the name, which is the way out when an upload says that a skill with that name is already installed and you do not want to replace it.

#Skills the agent writes itself

After a job that took real work — an error it got past, a procedure you corrected — the agent may save the procedure as a skill, without being asked. It shows under the answer ("Learned a new skill: …"), carries the mark "Written by the agent" in Settings → Skills, and lives in the orchestrator's skills/ like any other. Details and safeguards: Memory.

The agent improves only the skills it wrote itself. A skill you made or installed is never changed by it. To keep one of the agent's skills as your own, edit it by hand and delete the line origin: learned from its header — from then on the agent leaves it alone.

A learned skill that stays unused for a long time is marked "Not used for a while", and later moved to skills/.archive/; move the folder back to bring it back. You can also delete a learned skill from the list like any other; the agent may write it again if the same kind of work comes up.

#Writing your own skill

The easiest way is to ask the agent:

"Make a skill for the weekly sales report: take the export from sales/, total revenue by category, compare with last week and write a three-paragraph summary plus a table."

The agent creates the skill in the current project. A good moment for this is right after you have done the job properly together once: ask "turn what we just did into a skill".

#What a skill is made of

A skill is a folder in the project's (or the orchestrator's) skills/:

skills/
└── weekly-sales-report/
    ├── SKILL.md          # the instruction
    ├── scripts/          # scripts, if needed
    └── references/       # samples and reference material

SKILL.md starts with a YAML header:

---
name: weekly-sales-report
description: Weekly sales report from the export in sales/. Use when asked for a sales report for the week.
---

# Weekly sales report

1. Find the latest export in `sales/`.
2. …

• name — the skill's name, lowercase with hyphens, same as the folder name.
• description — what the skill does and when to use it. The agent decides whether the skill fits from this description, so make it specific.

#Tips

• One skill, one kind of work. A skill "for everything" gets applied where it does not belong.
• Write steps and a definition of done in the skill, not general wishes.
• If the skill relies on samples, put them in the skill's folder, not in the context.