What you can build
| You build | It is | Start here |
|---|---|---|
| A skill | A folder with a SKILL.md that teaches employees one kind of work. | Skills |
| An employee package | A role: an AGENT.md persona, an optional agent.json with workflows, inputs and required capabilities, and its own skills. | Employee Packages |
| A workflow | Work an employee does on a schedule, on an event, or when a watched system changes. Workflows live in agent.json. | Workflows |
| A plugin | A command-line binary with a plugin.json that connects employees to a service or program, with per-employee accounts. | Plugins |
| An app | An employee with its own window: HTML under ui/, the App SDK, and an optional sidecar process. | Apps |
You can also connect what already exists. Employees can use the tools of any MCP server, and Nebo Link brings agents you already run on a computer into NeboAI as employees.
How the pieces fit
A bot is one running copy of Nebo. Each bot has employees, and each employee owns a set of responsibilities. An employee works in chat, in team threads, and on its own through workflows.
- Skills tell an employee how to do something.
- Capabilities say what kind of system a role needs, such as mail or a ledger. The owner binds a real connection when hiring.
- Plugins and MCP servers provide those connections and tools.
- Workflows say when an employee acts without being asked.
- The company layer gives every employee the company's own vocabulary, rules and facts.
Employees are written as generic roles. A bookkeeper package requires the ledger capability, not a particular accounting product, so the same package works for every company that
hires it. Core Concepts explains each piece.
Build and test locally
Everything you write is plain files. Put a skill, employee package or plugin in the matching user/ folder of a bot's data directory, and Nebo loads it within seconds. Each page
lists the exact folder. You can also ask an employee to write a skill or create an employee for
you; it uses the same formats.
Publish
You publish through the NeboAI MCP server at https://neboai.com/mcp. Connect any MCP
client, create the artifact, upload its files, and submit it for review. Every artifact gets an
install code, such as SKIL-B72F-3QXE, that installs it with its dependencies on any
bot. See Publishing.
Next
- Core Concepts: the model behind every page.
- Skills: write your first SKILL.md.
- Employee Packages: build a role.
- Learning Center: step-by-step tutorials.