example
Print a working example of a component file, for the CLI version you're running.
npx @elizon/cli example [kind] [--json]
npx @elizon/cli example workflow --node <type> [--json]
npx @elizon/cli example workflow --pattern <name> [--json]Prints a complete, working project that uses the kind of file you asked about: the manifest that wires it in, and the definition files themselves. It needs no project, no manifest, no account and no network, so it works in an empty folder as a quick lookup. It writes nothing.
schema describes elizon.yaml only. The files the
manifest points at (ref: ./teams/triage.yaml) have their own formats, and example is how you see
one.
- Without a kind: lists the kinds that have an example, and what each shows.
- With a kind: prints every file of the example project, each under a
# ===== path =====line. The comment lines at the top say which file to read for that kind. - With
--json: the same in the document'sdata:kind,lookAt, andfiles, a list of{ path, contents }.
| Kind | Read this file | What it shows |
|---|---|---|
agent | agents/*.yaml | An Agent: its instructions and model Slot, MCP and OpenAPI operations, a Knowledge Base and Data Table reads |
team | teams/*.yaml | A Team: a lead that decides which member answers, and its member Agents |
workflow | workflows/*.yaml | A Workflow graph, the Agent it calls and the Data Table it writes to |
knowledge-base | knowledge/*.yaml | A Knowledge Base: search mode, embedding Slot, index settings and data mode |
data-table | tables/*.yaml | A Data Table: its columns, and the Data Table node, Code node and Agent bindings that use it |
voice | voice.yaml | A voice Agent and its voice configuration |
skill | skills/*/SKILL.md | A Skill folder: SKILL.md, a reference file and a script the Agent runs |
tool | tools/*.yaml | MCP and OpenAPI Tools with their credential Slots, and the Agent that binds their operations |
sip | sip/inbound.yaml | A phone line: the SIP routing template, its sip-trunk Slot, the voice configuration, Agent and inbound-call trigger |
One Workflow node, or a pattern
example workflow --node <type> prints a small Workflow built around one node type, wired from a
trigger, with its data filled in, inside a complete project (the manifest and every Agent, Team,
Tool, Knowledge Base, Data Table and Slot the node references). It works for all 27 node types, from
trigger_manual to note; an unknown type is refused, and the hint lists them all. --node=loop and
--node loop are the same.
example workflow --pattern <name> prints several nodes working together:
| Pattern | What it shows |
|---|---|
if-else | An If/Else node with two branches and a default, each wired by its sourceHandle |
loop-send-email | A Data Table read, a Loop over the rows with a Send Email in its body, and a step after the loop |
human-review-upsert | A single and a batch Human Review, each followed by a Data Table upsert with its key condition |
code-bulk-upsert | A Code node that writes a file of rows, and a Data Table bulkUpsert that reads it by key |
With --json, data holds node (or pattern) instead of starter. Every field of every node type,
with what travels and what validate and build refuse, is on
Workflow nodes; its examples are
the ones --node prints.
Every field of an Agent file, its tool bindings and its config are described on
Agents. The Skill format is described in full on
Skills, and the Tool format, with
what validate and build refuse, on Tools, and every way a Package uses a Data Table on
Data Tables. The team example uses
the handoff (Route) mode; every coordination mode, status and lead option is on
Teams. Every value of the SIP routing template, and how the
sip-trunk Slot binds at install, is on
Voice and SIP.
The examples are valid by construction
Each kind's example is the corresponding init starter,
printed instead of written, so there is no separate copy to drift. The --node and --pattern
examples have one copy too, which the Workflow nodes page shows. The CLI's own tests write every
example into a project and run validate on it.
Copy the shape, then replace the text, names and Slots with your own.
$ npx @elizon/cli example team
# Example: team
# A Team: a lead that decides which member answers, and the Agents that are its members.
# The files below are a complete, valid project (the `team` starter).
# For a team file, read teams/*.yaml; the manifest shows how it is wired in
# (the `ref:` entry, and the Slots that bind to it).
# ===== elizon.yaml =====
…
# ===== teams/triage.yaml =====
name: Triage
coordinationMode: handoff
leadType: managed
…For coding agents
The files init writes for Claude Code, Codex, Cursor and others tell the agent to run example
before writing a component file, and not to search the disk for one or guess its shape. See
Author with a coding agent.