Skills
Teach compatible AI agents when and how to use Jio for bounded remote compute.
Jio Core includes the repository-owned jio-compute agent skill. It teaches an AI coding assistant to keep reasoning local, inspect policy before allocating compute, and operate Jio through its structured CLI.
Use the skill when work needs heavier compilation, extra CPU or memory, isolated execution, build artifacts, or a private long-running backend.
Trust remains explicit
The skill never treats trusted-host as confidential. That mode is unattested, and the host operator can read workspace and tool plaintext. Jio must never fall back from confidential to trusted-host after a failed trust check.
Install the skill
The skill lives with Jio Core at skills/jio-compute. Install the complete directory in the skills location supported by your agent:
cp -R ../jio-core/skills/jio-compute /path/to/agent-skills/Keep SKILL.md together with its agents/ metadata. If your client supports loading a local skill by path, point it at:
../jio-core/skills/jio-compute/SKILL.mdThen invoke it explicitly:
Use $jio-compute to run this compute-heavy task in a private remote session.Here, private means the work runs in a separate remote workspace. The selected trust mode still determines who can observe plaintext.
What the skill does
Establish local authority
Reuse an existing .jio/identity.json. If no identity exists, the skill offers jio identity init and waits for explicit approval before creating one.
Validate without allocating
Run jio doctor and handle typed errors locally before any workspace bytes, commands, declarations, or secrets are sent.
Plan before starting
Run jio plan and report the environment, toolchains, compute profile, TTL, trust posture, egress, cost metadata, and required approvals.
Start only when work is ready
Create the remote session lazily, execute bounded commands, and use explicit renewals instead of treating traffic as lease renewal.
Review and close
Inspect diffs before syncing, pull only explicit artifacts, and stop the session when its ephemeral state is no longer needed.
Good fits
Compute-heavy builds
Compile or test projects without consuming the developer machine's CPU and memory.
Isolated experiments
Run unfamiliar commands away from everyday projects and personal files.
Build artifacts
Produce bounded, content-addressed outputs and pull only the paths you intend to keep.
Private services
Start a named no-egress backend with bounded logs and an explicit lifecycle.
Safety behavior
| Area | Skill behavior |
|---|---|
| Policy | Prefers a reviewed .jio/jio.toml; direct flags require an explicit endpoint, workspace, and trust choice |
| Trusted host | Requires --allow-unattested and reports the operator-readable posture |
| Confidential mode | Requires a policy file and stops on attestation or trust failure |
| Secrets | Uses interactive jio secret set; values never enter prompts, arguments, files, or MCP calls |
| Artifacts and sync | Reviews conflicts before overwrite or local synchronization |
| MCP | Offers project installation only after successful CLI use and only with an existing policy file |
Continue with the CLI workflow, then add Jio to a compatible client through MCP.