The Agent Skill That Ships with Your Okibi CLI
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
The Agent Skill That Ships with Your Okibi CLI
Agents find a CLI through its skill file: a short SKILL.md that says what the CLI is, which commands exist and how to call them. Okibi installs one with every CLI. This guide installs acme-orders, shows where the skill lands, reads what an agent will see, and confirms it matches the version you published.
What you will build
A check of the installed skill's location, front matter and content, tied back to the release you published.
install -> ~/.agents/skills/acme-orders (link) -> SKILL.md -> name, description, allowed-tools, commands
AI Prompt
Using the Okibi CLI, install acme-orders into a temporary HOME and inspect the agent skill it installs. Requirements: - Install with `CODEX_HOME` and `CLAUDE_CONFIG_DIR` unset and a temporary HOME. - Report where `~/.agents/skills/acme-orders` points. - Print the first lines of SKILL.md and report `name`, `description` and `allowed-tools`. - Count the lines and check that the "Known gotchas" section from the published skill is present. - Run the verification step below before finishing.
Prerequisites
- A generated CLI named
acme-orderswhose official release includes the "Known gotchas" skill edit (added withokibi clis skill set --fileand published withokibi clis skill publish). - Okibi CLI
0.2.11, logged in.
1. Install
T=$(mktemp -d) CMD=$(okibi clis hosting status acme-orders --json | python3 -c "import json,sys;print(json.load(sys.stdin)['workspaceInstallCommand']['command'])") env -u CODEX_HOME -u CLAUDE_CONFIG_DIR HOME=$T ACME_ORDERS_NO_KEYRING=1 sh -c "$CMD"
The installer prints install: installed Agent Skill to <home>/.agents/skills/acme-orders (every installer line starts with install: ). It ends with a note that $T/.local/bin is not on your PATH, which you can ignore here. Keep using the same terminal so $T stays set.
2. See where the skill lives
readlink $T/.agents/skills/acme-orders SKILLDIR=$(readlink $T/.agents/skills/acme-orders) ls -A "$SKILLDIR"
<home>/.local/share/okibi/clis/acme-orders/versions/<n>/skills/acme-orders .okibi-managed .okibi-owner SKILL.md
~/.agents/skills/acme-orders is a link to the skill folder inside the installed version. The <n> in versions/<n> is the Okibi version number of the release you installed, so do not type it: the commands above read the folder from the link. (On the test CLI it was 3 for release 1.0.2 and 5 for 1.0.4.) .okibi-owner held the id of the CLI project.
3. Read what an agent sees
sed -n 1,12p $T/.agents/skills/acme-orders/SKILL.md
---
name: acme-orders
description: "Okibi CLI for Acme Orders. A small orders API used as the example target in the Okibi guides. Authenticate with the X-API-Key header."
author: "acme-orders CLI authors"
license: "Apache-2.0"
argument-hint: "<command> [args] | install cli|mcp"
allowed-tools: "Read Bash"
metadata:
openclaw:
requires:
bins:
- acme-orders
nameanddescriptionare what an agent matches a task against. The description is taken from the API's spec.allowed-tools: "Read Bash"is the skill's request for which tools the agent may use. Whether it is enforced depends on the agent host that loads the skill. Treat it as a declaration, not a guarantee.requires: bins: acme-orderssays the binary must be on the path. Theopenclawblock is metadata for hosts that read it. Other hosts ignore it.
The body has a command reference, pagination and auth notes, agent-mode flags, exit codes and instructions to install the MCP server with claude mcp add acme-orders -- acme-orders mcp --tools full.
Verify the result
wc -l < $T/.agents/skills/acme-orders/SKILL.md grep -c 'Known gotchas' $T/.agents/skills/acme-orders/SKILL.md ACME_ORDERS_NO_KEYRING=1 HOME=$T $T/.local/bin/acme-orders --version
Expected: about 200 lines (201 in the first test, 199 in a second run on another CLI, so your count depends on the skill's history), a grep count of 1, and acme-orders 1.0.2 (the official release when this was tested). A count of 0 means you installed a release from before the skill edit.
How it works
The skill is part of each release, so installing a release installs the skill that was published with it. Publishing a new skill with okibi clis skill publish makes a new release, and a fresh install carries it.
Common issues
A temporary HOME does not isolate the system keyring
The installer and the generated CLI store credentials in the operating system's keyring under one service name that every copy of acme-orders on the machine shares. Pointing HOME at a temporary folder does not change that. acme-orders uninstall deletes those keyring entries as well as files. Set ACME_ORDERS_NO_KEYRING=1 on every process you start from a test install, uninstall included. This guide's commands do. Keep CODEX_HOME and CLAUDE_CONFIG_DIR unset too, as above.
The description comes from your spec
An agent chooses the skill by its description. If the spec's info.description is vague, so is the skill. Improve the spec and regenerate, or edit the skill with okibi clis skill set.
Older installs keep the older skill
A CLI installed earlier keeps the skill of that release. Reinstall to pick up a newer one. The copy installed with the signed command printed Error: this installation has no update channel; request a newer release from the CLI owner for acme-orders self-update --check. That is the install channel this guide uses. Other channels were not tried.
The skill names a command in one place and another elsewhere
Compare the skill's command list with okibi clis docs acme-orders --json to find commands the skill leaves out.
verification: status: verified tested_at: "2026-11-02" product_version: "okibi 0.2.11; acme-orders 1.0.2" command: "grep -c 'Known gotchas' $T/.agents/skills/acme-orders/SKILL.md" expected_result: "1, in a 201-line SKILL.md, from the 1.0.2 release"
