Skip to main content
A Skill is a reusable instruction playbook that an agent invokes on its own. Define the method once (“when this kind of request comes in, handle it this way”), and the agent automatically loads and follows it whenever a request during a conversation matches the skill’s purpose.
The Skills tab is currently in preview and appears only in certain environments (development/staging hosts). If the Skills tab isn’t visible in production, contact your administrator. Document-generation skills (PPT, Word, Excel, HTML) are provided through the Marketplace.

​
What is a skill?

A skill is an imperative instruction set you hand to the agent. It has three parts.
ElementRole
NameSkill identifier (globally unique)
Description (when to use)The criteria the agent uses to decide when to invoke this skill
Body (SKILL.md)The step-by-step instructions the agent follows
You can also bundle files (scripts, reference documents, etc.) with it when needed.

​
Skill vs prompt

They are easy to confuse but are opposites.

Prompt

You type it yourself. In chat, a / command expands saved text.

Skill

The agent chooses it. You never call a skill — when a request matches the description, the agent invokes it on its own.
That’s why writing a good description (“when to use”) matters most. The agent decides whether to trigger a skill based solely on this description. Example: “Use when the user asks to organize meeting notes into the standard format.”

​
Skill list

Go to Workspace > Skills to see every skill you can access. Each card shows the name, description, author, and last-modified time. Use the search box at the top to search by name or description. The Generate with AI and New Skill buttons are at the top right (if you have skill write permission). Card actions:
ActionDescription
Click the cardOpen the edit screen (if you have write permission)
ExportDownload the skill as a JSON file
DeleteOwner or admin only
Export is a partial backup. It includes only the name, description, and body — not bundle files or access-control settings. Do not rely on it as a full backup.

​
Creating a skill

There are two ways to create a skill.
Click New Skill and enter the basic information first.
FieldDescription
What are you working on? (name)Skill name
When should the agent use this skill? (description)Trigger condition
PermissionPrivate / Public, per-group/org-unit read/write
After saving, you go straight to the editor to write the body (SKILL.md). A skill you create yourself is private (owner-only) by default.
A skill name must be unique across the whole workspace and is case-sensitive. Saving with a name that already exists produces an error.

​
Skill editor

The editor is a small IDE with a file tree on the left and an editing area on the right.

​
Entry point — SKILL.md

SKILL.md always appears at the top of the file tree with an Entry tag. Its contents are the skill body — the instructions the agent follows when the skill is triggered.
Write the body as imperative instructions to the agent. The more specific the steps, rules, and output format, the more consistently the agent follows it.

​
Adding bundle files

Use the Add file button in the file tree to add scripts or reference documents. Specify a path (e.g. scripts/lookup.py, references/style-guide.md) and they are organized by folder.
  • Markdown files support a formatting toolbar (bold/italic/code/list) and an Edit/Preview toggle
  • Code files (.py, .js, .sql, etc.) get syntax highlighting
  • Only relative paths are allowed, and SKILL.md cannot be a bundle file (it is the entry point)
When the body references a bundle file, the agent reads it only when needed. It does not load all files at once, so you can include large reference materials without concern.

​
Meta information

The meta area at the top of the editor shows two things.
ItemMeaning
Used by agentsList of agents using this skill (reverse dependency)
ImportedMarks skills brought in from the marketplace, a bundle, etc.
Check Used by agents before deleting or heavily changing a skill. Trying to delete a skill that’s in use triggers a confirmation step.

​
Attaching to an agent

A skill only works once it’s attached to an agent.
1

Open the agent edit screen

Open the agent to edit in Workspace > Agents.
2

Select in the Skills section

Add the skills to attach in the Skills section. Marketplace document-generator capabilities are also selected here.
3

Save

After saving, the agent can use those skills.
Skills have no separate on/off toggle. Attaching to an agent turns it on; detaching turns it off. There is no per-conversation toggle.

​
How it works in chat

Once skills are attached to an agent, the following happens during chat.
  1. The agent is always aware of the name + description list of attached skills
  2. When a user request matches a skill’s description, the agent loads that skill’s body
  3. It follows the instructions (reading bundle files or running scripts as needed)
  4. It reflects the result in the answer
Skill activation has no separate on-screen indicator. The agent simply follows the instructions quietly. However, when a skill produces a file (like the document generators), the result file appears above the answer as 📎 Download: [filename](link) first.

​
Executable skills and document generation

Some skills can actually run bundled scripts to produce files (PPT, Word, Excel, HTML, etc.). Such executable skills work only under these conditions.
  • The skill must be marked as executable (the marketplace document generators are the prime example)
  • An administrator must have configured a code execution engine (Jupyter)
If the code execution engine is not configured, an executable skill cannot run its scripts and only follows the instructions, so no file is generated. If document generation isn’t working, ask your administrator to check the code execution setup.
Skills you write yourself cannot become executable. If you need executable document generation, use the document generators in the Marketplace.

​
Access control

Skills follow the same permission model as other workspace resources.
OptionDescription
PublicAny logged-in user can read
PrivateOwner and admin only. Can grant read/write to specific groups/org units
When an agent uses a skill, it re-checks against the executing user’s read permission. Even if a private skill is attached to a shared agent, it is not exposed to or triggered for users who lack read access.
Administrators control per-group Skills Access permission (none/read/write) in Admin Settings > Users > Groups. The default is locked (none).

​
Troubleshooting

CauseSolution
Preview environment restrictionThe Skills tab appears only in certain environments. Contact your administrator
No permissionAsk an administrator to grant your group Skills Access permission
Skill names must be unique across the whole workspace. Use a different name. (Names are case-sensitive.)
Executable skills require an administrator to configure a code execution engine (Jupyter). Check Admin Settings > Marketplace or the Code Execution settings.
Deletion is blocked if agents are using it. Check the Used by agents list in the editor, and if you still want to delete it, confirm the force delete.

​
FAQ

A knowledge base (RAG) retrieves and provides factual information. A skill provides a method or procedure. They work together — for example, a skill instructs “organize it in this format,” and the knowledge base fills in the content.
We recommend under 500 lines. Don’t put long reference material in the body — split it into bundle files and reference them from the body. The agent reads them only when needed.
Yes. You can attach one skill to multiple agents. Check Used by agents in the editor to see which agents currently use it.
It’s a draft, so always review it. In particular it’s saved as Public by default, so if needed, change the access to Private and refine the body before using it.

​
Next steps

Marketplace

Set up the PPT/Word/Excel/HTML document generators and Google Workspace/Microsoft 365 integrations

Attach to an agent

Attach skills to agents to standardize how they work