Install Tilebox skills and the CLI
Many skill operations require the Tilebox CLI, which is why it’s recommended to use our installation wizard that sets up both Skills and the CLI on your system.Tilebox skills on GitHub
Browse the source repository for the Tilebox agent skills.
Included skills
Tilebox skills cover common agent workflows around the CLI, datasets, workflows, jobs, and automations.| Skill | What it covers |
|---|---|
using-tilebox-cli | Authentication, --json, jq, agent-context, and documentation search |
managing-tilebox-datasets | Creating schemas, updating metadata, and querying datasets |
managing-tilebox-jobs | Submitting jobs, monitoring status, reading logs, and inspecting spans |
working-with-tilebox-automations | Working with triggers, automations, and storage locations |
writing-tilebox-workflows | Writing workflow task classes, task graphs, runner definitions, caches, logs, and spans |
releasing-tilebox-workflows | Initializing workflow projects, configuring tilebox.workflow.toml, building releases, publishing releases, deploying to clusters, and running release runners |
How to use skills with agents
Ask your agent to load the most specific Tilebox skill for the task. For example, usemanaging-tilebox-datasets for schema work and managing-tilebox-jobs for workflow execution or observability tasks.
Skills work best with the Tilebox CLI. The CLI gives the agent repeatable terminal commands, and skills tell it how to combine those commands safely. Use MCP as an alternative when the agent runs in a web or chat environment without practical terminal access.
For Python workflow release work, ask the agent to use both writing-tilebox-workflows and releasing-tilebox-workflows. For a new project, the typical loop starts with tilebox workflow init. After that, the agent edits tasks, builds a release, publishes it, deploys it to a development cluster, runs tilebox runner start, submits a test job, and inspects logs or spans before iterating.