Agent skills¶
IOLake ships skills for coding agents (Claude Code, Codex, opencode,
pi and others that read SKILL.md files). A skill tells the agent how a
job is done on IOLake, in what order, and what not to do, so that
"deploy this", "give this app its own bucket" or "why is this PG not
clean" get the right commands the first time.
| Skill | For | What it covers |
|---|---|---|
iolake-deploy |
operators | Installing, sizing, upgrading, monitoring and troubleshooting: iolake-aio, the binaries, the Helm chart; the choices that are hard to change later; what is lost if |
iolake-admin |
operators | Running a cluster with iolakectl: tenants, users and keys, policies, roles and STS, buckets and provisioning, pools, placement groups, drain, upgrades, KMS, audit, replication |
iolake-sdk |
application developers | Connecting S3 clients (addressing, region, SigV4), credentials (scoped keys, STS, environment), which S3 features exist and which are refused, the Python and Go SDKs, the data lake APIs |
Installing them¶
iolakectl carries them, so they match the release you run:
iolakectl skills list
iolakectl skills install # every agent found under $HOME, and ~/.agents/skills
iolakectl skills install --audience ops # only the operators' skills (or dev)
iolakectl skills install --agent claude # one agent; repeatable
iolakectl skills install --dir ./.claude/skills # one project
iolakectl skills install --force # replace older copies after upgrading iolakectl
install needs no endpoint or credentials. It writes to each agent whose
home directory exists (Claude Code ~/.claude/skills, Codex
~/.codex/skills, opencode ~/.config/opencode/skills, pi
~/.pi/agent/skills) and always to ~/.agents/skills. A copy that
differs from the one carried is left alone unless --force is given.
In Claude Code, without iolakectl, the repository is a plugin marketplace:
/plugin marketplace add io-lake/iolake
/plugin install iolake-ops@iolake # iolake-deploy, iolake-admin
/plugin install iolake-dev@iolake # iolake-sdk
Contributors¶
For an agent working on IOLake's own code, the repository has two more
skills in .claude/skills/, which Claude Code loads in a checkout:
iolake-contribute (from the issue to the merge) and
iolake-testing (unit, end-to-end, s3-tests, the upgrade test). The
rules they follow are in
CONTRIBUTING.md.