6.1 Choose a development path
Choose what you want to deliver, then open its tutorial. Template and skill authors do not need to read the source architecture first.
Develop four resource types
| Goal | Start here | Expected deliverable |
|---|---|---|
| Define a role with clear responsibilities | AI employee | An importable template and a real task result |
| Organize employees to work together | AI team | Member responsibilities, handoffs and a team template |
| Add methods or connect a business system | App | An addable method app or a working MCP service |
| Reuse a specific way of working | SKILL | A complete SKILL.md and an output that meets its requirements |
You can start in Teloa without writing files: create an AI employee, AI team, app or SKILL. Each tutorial starts with a copyable natural-language request, confirmation steps and a test input, followed by complete file examples. Finish a small example without external accounts before adding real material and connections. Distribute it using offline files or online links.
Integrate existing systems
| Direction | Tutorial |
|---|---|
| Your system or another Agent calls a Teloa employee | Employee API / SDK / MCP |
| A Teloa employee reads your service | Read-only MCP tools; start an HTTP service with the app example |
Configure credentials and permissions separately for each direction. Calling an employee does not add tools to its grants.
Change Teloa itself
Use architecture to locate the package, local development to prepare the environment, and testing and contributing to validate the change. Read execution engine boundaries when adapting runtime components.
See resource packaging and distribution to combine resources in an importable file, and format reference for fields, format versions and internal interfaces. These are shared technical references, not a fifth product category.
Before running examples
Resource examples contain fictional material. Employee-call examples require your configured model and a scoped integration key and incur model usage. Use a dedicated test employee and business area before connecting real systems.