Skills

Level	Purpose	Host path	Runtime path inside sandbox
Workspace-level (global skills)	Shared tools available to all conversations in a workspace	<workspace>/skills/<skill-name>/	/workspace/skills/<skill-name>/
Conversation-level (local skills)	Tools for one conversation / channel / DM only	<workspace>/<conversationId>/skills/<skill-name>/	/workspace/<conversationId>/skills/<skill-name>/

Note

mikan loads workspace-level skills first, then conversation-level skills. If both sides define the same name, the conversation-level skill overrides the workspace-level skill.

Directory structure

<workspace>/
├── skills/
│   └── my-global-tool/
│       ├── SKILL.md
│       └── run.sh
└── <conversationId>/
    └── skills/
        └── my-local-tool/
            ├── SKILL.md
            └── run.sh

A directory containing SKILL.md is treated as one skill root and is not searched recursively. mikan also discovers standalone .md files directly under a configured skills directory.

A directory-based skill uses SKILL.md:

---
name: my-tool
description: Does something useful
---

Usage: {baseDir}/run.sh <args>

name and description are required. Use paths relative to the skill directory, or write the runtime-visible absolute path shown in the table above. {baseDir} is not expanded automatically.

Which level to use

Workspace-level skills are good for shared tools: company APIs, common scripts, release helpers, reporting tools, or any capability used by multiple conversations.

Conversation-level skills are good for local tools: a specific channel workflow, a temporary helper, or tools that should not appear in other conversations.