Skip to content

Agent Skills

Install Tilebox skills that teach AI agents how to work with Tilebox tools and workflows.

Tilebox skills are task-level instructions for AI agents. They explain how to use the Tilebox CLI, which command patterns to prefer, and how to approach common workflows such as dataset management and job monitoring.

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.

Terminal window
curl -fsSL https://install.tilebox.com/wizard.sh | sh

If you want to customize the skill installation directory, or select just a subset of the skills to install, you can use

Terminal window
npx skills add tilebox/skills

After installation, your agent can load the relevant skill before working on a Tilebox task.

Tilebox skills cover common agent workflows around the CLI, datasets, workflows, jobs, and automations.

SkillWhat it covers
using-tilebox-cliAuthentication, --json, jq, agent-context, and documentation search
managing-tilebox-datasetsCreating schemas, updating metadata, and querying datasets
managing-tilebox-jobsSubmitting jobs, monitoring status, reading logs, and inspecting spans
working-with-tilebox-automationsWorking with triggers, automations, and storage locations
writing-tilebox-workflowsWriting workflow task classes, task graphs, runner definitions, caches, logs, and spans
releasing-tilebox-workflowsInitializing workflow projects, configuring tilebox.workflow.toml, building releases, publishing releases, deploying to clusters, and running release runners

Ask your agent to load the most specific Tilebox skill for the task. For example, use managing-tilebox-datasets for schema work and managing-tilebox-jobs for workflow execution or observability tasks.

You

Load the relevant Tilebox skills. Use the Tilebox CLI to submit a Sentinel-2 mosaic job, then monitor it until it completes.

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.