6.1 Choose a development path
Teloa offers development paths for resource authors, tool integrators, and source contributors. Start with the path that matches what you want to accomplish.
| Goal | Start here | Smallest useful result |
|---|---|---|
| Reuse a working method | Write a skill | A valid SKILL.md file |
| Share a complete business configuration | Business resource packages | A package that can be previewed and imported |
| Connect an external reference service | Read-only MCP | One successful read and one rejected out-of-scope request |
| Change product behavior | Architecture, Local development | A change that passes the relevant tests |
Read the core boundaries first
Business capabilities and execution engines defines object ownership, package provenance, configuration, and authorization. Read it before integrating an engine or exposing a native feature in the product.
Integration does not grant permission
Skills, MCP configuration, resource relationships, and role permissions are separate layers. Writing “ignore approvals” in a skill does not grant permission. Do not call internal services directly to bypass execution checks.
Current interface status
Business systems call employees through the employee work API, SDK and MCP Server. Internal RPC and TypeScript contracts continue to evolve and are not the public integration contract. Teloa integrates pinned DSH, Codex and Claude Code / Claude Agent execution paths. Additional third-party harnesses or npm plugins require adaptation for identity, authorization, lifecycle and result delivery.
The native npm installer manages the stable release. It installs and manages the Web service; it is not a terminal chat product or development SDK. See the installation guide for startup workflows and execution limits.
Before developing, set up an isolated data environment and record your version and reproducible inputs. See Testing and contributing for contribution requirements.