Skills

Install the Kode skills that teach an AI agent the concepts, the tools, and the team rules, and give tasks to workspaces.

Last updated 14 Nov 2026

On this page

Overview
The Claude Code plugin
Tasks
Install the Claude Code plugin
Install the skills in another agent
Give a task to a workspace
Troubleshooting

Overview

A skill is a folder with a SKILL.md file. It tells an AI agent what the Kode words mean, which tool does which job, and which rules to obey. The agent reads the description of each skill and loads a skill when a task matches it. A skill holds no credential and calls nothing. The agent does the work with the tools of kode mcp. See Connectors — MCP.

The skills are the folders of skills/ in https://github.com/kloudlite/harness. These skills are for your agent.

Skill	Loaded when	What it gives the agent
`kode`	Every Kode task, and the Kode tools are present. Load it first. Also for status, logs, stop, start, delete, and quota questions, and when a tool answers `not logged in`.	The nine components, the rules for picking the shape of workspaces, environments, and desks, ids and states, the tool groups, the safety rules, and the set-up steps when the tools are missing. Its `references/` folder holds the tool list, a catalogue of common services with their ports and data mounts, and the errors with their actions.
`kode-develop`	A project is set up, or code is changed or run against real services.	18 scenarios: set up a workspace, an environment, and a desk; run code against the services; intercept one or several services; debug with real traffic; work in parallel; copy an environment; change a service; set and rotate variables and secrets; take and restore snapshots; publish an image; stop a desk.
`kloudlite-verify`	A check or a test runs one time.	7 scenarios: a quick check in a workspace, a clean run in a capsule against the environment, a one-off script, the record of a capsule, a pull request tested against a copy of an environment, two changes tested together, and capsule cleanup.
`kode-automate`	Work runs without a person, or repeats.	17 scenarios: write, save, and version a pipeline; start it by hand, on a schedule, from a webhook, or after another pipeline; inputs, order and conditions, and matrices; secrets, code, registry pushes, and volumes in a job; debug, cancel, and clean up. Its `references/` folder holds the definition keys and the `needs` and `if` table.

Only kode holds the definitions. The other three give steps and refer to it.

The skills use the tools of kode mcp for capsules, pipelines, secrets, and desk lifecycle too. Two things have no tool: connecting a code host or a registry (the web console), and the kode env tunnel to your computer. For these the agent gives you the command.

The harness and the plugin load the other folders of skills/ themselves (orchestrate and develop are part of the plugin; the rest are for the Kode harness). Do not install them by hand.

The kode skill gives the agent these safety rules:

Before a delete, a restore in place, or a stop, the agent lists the targets by name. It asks you first, unless you named the targets in the same turn.
The agent intercepts a service of the shared team environment, and stops the intercept when it is done. It makes a copy of an environment only for a task that needs one, or when you ask.
The agent takes a snapshot only when you ask. It builds and pushes an image only when you ask.
The agent never shows a secret value. It passes the value you give to secret_set and does not repeat it.
When a call fails or you refuse it, the agent tells you. It does not go around the failure through another workspace, desk, or tool.

When the agent has no Kode tool, the kode skill tells you how to install kode, sign in, and connect the agent. The agent does not run the installer without your consent.

The Claude Code plugin

The plugin gives Claude Code the server kd and the skills. It needs no kode program. It works for one desk, and reaches a workspace only through that desk.

Part	Function
Tool server `kd`	The remote server `https://dev.kloudlite.io/mcp`. It sends each call through the desk.
Skills	`kode`, `kode-develop`, `kloudlite-verify`, and `kode-automate`.

You choose the owner and the desk on the consent page of the first sign-in. The remote server withholds web_fetch and web_search; Claude Code has its own.

Tasks

Install the Claude Code plugin

Reason for the task

Give Claude Code on your computer the Kode skills and tools.

Job set-up

Access: you. For a team desk, a team member.
Agent tool: none; an agent uses the SDK.
Conditions: Claude Code is installed, and a desk exists. See Create a desk.
References: Remote server.

NOTE

Update the plugin with claude plugin marketplace update kode.

Procedure

Add the marketplace and install the plugin.

CLI

claude plugin marketplace add kloudlite/harnessclaude plugin install kode@kode

Start Claude Code and call a Kode tool. The browser opens for the sign-in.

Close-out

Type /mcp in Claude Code. Make sure that the server plugin:kode:kd shows as connected.

Install the skills in another agent

Reason for the task

Teach an agent other than Claude Code with the plugin to use the Kode tools.

Job set-up

Access: you.
Agent tool: none; an agent uses the SDK.
Conditions: the agent reads skill folders, and has the tools of kode mcp. See Add the server to an MCP client.
References: https://github.com/kloudlite/harness.

Procedure

Add the four skills to your agent with the skills installer.
CLI
```
npx skills add kloudlite/harness
```
Select kode, kode-develop, kloudlite-verify, and kode-automate if the installer asks.
Start the agent again.

Close-out

Make sure that the agent lists kode among its skills.
Make sure that it lists kode-develop, kloudlite-verify, and kode-automate.

Give a task to a workspace

Reason for the task

Make an agent change code in a workspace.

Job set-up

Access: you, or your agent. For a team workspace, a team member whose access is not paused.
Agent tool: none; an agent uses the SDK.
Conditions: Claude Code runs with the plugin, and the workspace exists.
References: Start a workspace.

Procedure

Type the task in Claude Code. Name the workspace and say what to change.
text
```
In the workspace api, add a /healthz route to the web server and run its tests.
```
Give an answer when Claude Code asks, for example to start a stopped workspace or to confirm a delete.
Wait for the answer of Claude Code.

Close-out

Read the answer of Claude Code.

Troubleshooting

Symptom	Possible cause	Corrective action
The agent does not use the Kode words or tools	The skill is not installed, or the agent did not load it.	Install the skills, and name Kode in the task.
`403` with `your access to acme is paused`	A team admin paused your access.	Ask a team admin to unpause it.
`409` with a limit name, for example `workspaces: 5 of 5 in use; request more under Quota`	The owner has no quota left.	Delete an unused item, or see Quota and requests.