Skip to main content
Keel ships agent skills — SKILL.md documents in the Agent Skills format that AI coding agents load on demand. With them installed, an agent asked to “make this project deployable with Keel” knows the keel.yaml schema, the validation rules, how steps run, which Dockerfile patterns work, and how the CLI behaves, instead of guessing from training data.

​
Operate Keel Cloud through MCP

To let an agent configure targets, deploy, inspect logs, and manage your existing Keel Cloud portal, connect it to your deployment’s MCP server. OAuth grants it your current portal permissions. The skills below help agents author deployment files in a repository.

​
Install

From the repository you want the agent to work in:
The command detects the agents installed on your machine and writes the skills into each one’s project-level skills directory. Agents that share the .agents/skills convention get one copy. Commit the directories: the skills then travel with the repository, and every collaborator’s agent picks them up.
Install once for every repository on the machine:
This writes to the agents’ user-wide directories — ~/.claude/skills, ~/.codex/skills, ~/.cursor/skills, and so on.
When no supported agent is detected, the skills go into .agents/skills, which most agents read.

​
The skills

keel skills list prints the same list with each skill’s files.

​
Supported agents

The full table with the exact paths is keel skills agents. Detection looks for the agent’s configuration directory in your home directory.

​
Updating and removing

Running keel skills install again replaces the skill directories Keel wrote with the current version’s content — do it after upgrading keel. A directory with the same name that Keel did not write is left alone unless you pass --force.

​
Using the skills

Skills load when the agent decides they are relevant, so plain requests work:
  • “Add a Keel deployment that runs our Terraform in infra/ against GCP, with plan and apply modes.”
  • “Fix the keel validate errors.”
  • “Write a deploy/aws.Dockerfile for the aws-production deployment.”
  • “Export the variable manifest for client-acme.”
The skills tell the agent to run keel validate after editing and to read the deployment’s existing scripts before writing steps. They also point at this documentation site for anything not covered.
The skills are part of the keel source tree under skills/, so tools that install skills straight from a repository can use them without the CLI.