Skip to main content
Skills, agents and automations are plain files in a business’s memory, so you can read and write them like code. On Emplio’s computer the company files are at /work/company/ and each person’s at /work/me/. Emplio saves what it changes there to git at the end of each reply.

A skill

How to do one kind of job. A folder with a SKILL.md, plus any scripts it uses. Business skills go in company/skills/<name>/ (owner or admins); one person’s go in me/skills/<name>/.
company/skills/gst-invoice/SKILL.md
name is the folder name, lowercase with dashes. description says when to use it, under 100 characters. Emplio reads one with emplio skills use <name>, and people can start one by typing /name in the chat.

An agent

A saved specialist that work is handed to. company/agents/<slug>/AGENT.md holds its settings and instructions:
company/agents/invoice-chaser/AGENT.md
level is light or strong and picks the model. archived: true hides it. Next to it, LESSONS.md keeps dated lines like - 2026-11-07: <lesson>, the last 40, shown to it as notes from past work, never as instructions.

An automation

company/automations/<name>.md: settings between --- lines, then the prompt.
company/automations/chase-invoices.md
A run is a new chat, as whoever last saved the file, who must be the owner or an admin. Emplio writes these with emplio automations add, which checks the file.

An MCP server

Remote servers only, over Streamable HTTP or SSE. Add one in Integrations, or have Emplio run:
A header value of {{NAME}} is each person’s own saved key, so tokens never enter the computer. --key asks each person for their own token. A server that wants its own sign-in gets one per person, through a Sign in button in the chat. Tools not marked read-only ask for an OK first.

The emplio command

What Emplio can run.

Add an app or channel

Go deeper, in the code.