Skills teach Kucedr repeatable ways to perform a task without changing the core app. Each skill is a local directory under the agent's skills folder and must contain a SKILL.md file.
Skill Structure
The SKILL.md frontmatter must contain name and description fields. Names are lowercase alphanumeric or hyphenated identifiers of 1–64 characters; descriptions are capped at 1,024 characters.
A skill can keep supporting scripts, references, templates, and assets beside SKILL.md. The agent loads the instructions first and reads those supporting files separately when the task needs them.
my-skill/
├── SKILL.md
├── scripts/
├── references/
└── assets/
Manage Skills
The Skills settings area can:
- List installed skills with their name and description.
- Open the skills root in your file manager.
- Import one or more skill directories and report imported or skipped items.
- Inspect format, version, category, safety level, visibility, author, required tools, allowed tools, required connectors, tags, file paths, and validation diagnostics.
- Enable or disable a skill, export its folder, refresh the catalog, or delete it after confirmation.
Importing a skill whose ID already exists replaces that folder. Only enabled skills can be loaded. Safety level and visibility are shown for your review but are not enforced as blocking policy.
Use A Skill
Type /skill in the chat editor to search installed skills. When you select one, Kucedr loads its SKILL.md for the current run and gives the agent its directory path so it can access any supporting resources.
Review a skill's instructions, scripts, and tool requirements before enabling it. A skill can guide Kucedr to use the same powerful tools available during a normal agent run.
Other Ways To Extend Kucedr
- Build a dedicated interface with Apps.
- Connect external tools and services with MCP Servers.
- Create an app with the typed Kucedr SDK.