Skip to content

How to read the reference

This is the document you refer to when creating skills in /agent_skills.
The @zio_skill function written here becomes the skillFunction node of the agent builder, and the batch and debugger invoke it unchanged.

30‑Second Quick Start — All Tasks Follow These Four Steps

Section titled “30‑Second Quick Start — All Tasks Follow These Four Steps”
  1. Folder: Create /agent_skills/<folder_name>/. One folder represents one deployment unit (virtual environment).

  2. Code: Inside it, write a <any_name>.py file containing an @zio_skill function. Data is read and written using Zio.code (base code) · Zio.node (knowledge graph · ABox) · Zio.ontology (ontology · TBox) · Zio.entity (usr table) · Zio.view (virtual view). The only way to touch data is through this SDK, and SQL·Cypher via Zio.raw() is blocked.

  3. Library (only when needed): List package names in requirements.txt. If you later change it, run a single restart below — the server will reload with the updated packages.

  4. Run — After making changes, this one line remains. No need to restart manually; the server detects file changes and automatically loads the new code.

    Terminal window
    curl -s -X POST http://api:8002/api/artifacts/skills/call/<폴더명>/execute/<함수명> \
    -H 'Content-Type: application/json' -H "X-Zio-Who: $ZIO_WHO" \
    -d '{"인자":"값"}'

    X-Zio-Who is the line that records “who” for auditing. $ZIO_WHO is already populated at login, so use it as is.

    If it doesn’t appear, check why:

    Terminal window
    curl -s "http://api:8002/api/artifacts/skills/logs?skill_name=<폴더명>"

    There’s no way to verify whether import works, and there’s no need to — this environment lacks python·pip, and the code runs in a runner. Whether it succeeds is answered by the call above.

The place where you write code differs from where it runs. This location has no python·pip; execution is handled by the skill runner container that receives the call above. .venv/ and main.py are created by the runner, so do not modify them. Engine source or database connection information is also absent here.

Calling out to the outside world with curl is allowed — weather data, public datasets, any external REST API. The same applies inside a skill (requirements.txt can include requests). What’s blocked is the path back to us — you cannot reach https://<platform_address>.

Only these three endpoints are callable from here into our engine. The port is always 8002.

POST /api/artifacts/skills/call/<폴더명>/execute/<함수명> 부르기 (고쳤으면 서버가 알아서 다시 띄움)
GET /api/artifacts/skills/logs?skill_name=<폴더명> 안 뜬 까닭
POST /api/artifacts/skills/restart 다시 띄우기 — requirements.txt 를 고쳤을 때 · 프로세스가 꼬였을 때 {"skill_name":"<폴더명>"}

External addresses cannot be called from here (403). Data is read within the skill using the SDK.

Use only the necessary parts. Reading everything will overwhelm you with manual context. If you’re new, start with Creating a Skill (@zio_skill) and then explore the rest of the documentation.

  • What is this?
  • Zero‑Trust security and isolation design guidelines
  • Zio SDK call API specification
  • Automatic handling of node display names (_display)
  • Main component ecosystem
  • Three forms of a skill
  • Folder structure
  • Using it in Agent Builder
  • Intelligent parameter mapping
  • Sample code for real‑world implementation
  • Build and run
  • Run inside SSH
  • Handling the handler’s words with the SDK — how to write a skill
  • Adding libraries later
  • What an entry point can do
  • One per entry point
  • Basic code API
  • Create and edit ontology
  • Set up according to ontology
  • Knowledge graph traversal API
  • Custom table API
  • MongoDB queries
  • What can be queried
  • Fluent CRUD API for collected data
  • Creating tools — external REST API, remote MCP registration
  • Fill in — render
  • Authoring — create · info · update
  • Overview at a glance
  • Sequence
  • Execution — call an already running agent and receive the result
  • Data collection pipeline
  • $TableName.FieldName
  • #OntologyNodeName.FieldName
  • Appendix 1. How to obtain a Google Spreadsheet service account key
  • There are eight ways to find
  • The label is the entirety of this set
  • Overview
  • 🚀 Core features and characteristics
  • Implementation example
  • Overview
  • Connection and usage instructions
  • When multiple people use it together
  • 🪟 Windows user self‑diagnosis
  • Troubleshooting

This folder is read‑only. Even if you edit it, it will revert on the next deployment.
If something is wrong or missing, tell the engine responsible person.

(주)지오유 · 경기 용인시 처인구 유림로154번길(유방동 673-2) 20-13

CEO 신달수·Business no. 142-81-36612·E-commerce no. 용인처인-0118호·Privacy officer 신달수·Email shindalsoo@gmail.com·Tel 1833-3623·Fax 02-6918-4006