Skills
A skill captures a work procedure that recurs in the field so the agent remembers it. Define it once and you no longer have to explain the same task in later sessions.
Listing and registration
| Method | Path | Purpose |
|---|---|---|
GET | /api/skills | List skills |
POST | /api/skills | Create a skill |
PATCH | /api/skills/{id} | Update (send only the fields to change) |
DELETE | /api/skills/{id} | Delete |
Registration body:
{
"name": "설비 일일점검 리포트",
"description": "라인별 가동률과 알람 건수를 표로 정리한다",
"content": "..."
}
description matters. The agent reads this description to decide whether the skill fits the task at hand — describing when to use it, rather than what it does, gets it matched more reliably.
Extracting a skill from a task
POST /api/session/{sessionId}/extract-skill
This turns the work you just completed in a session into a skill. When you want to reuse a job that went well, it is actually easier to build first and extract afterwards than to start from a skill.
Export and import
| Method | Path | Purpose |
|---|---|---|
GET | /api/skills/export | Download everything as a skill pack |
POST | /api/skills/import | Import a skill pack (skills array in the body) |
When you run a separate Studio per site, use this to distribute a skill set curated at headquarters to each site. On an air-gapped network, importing the file is all that is required.