# Agent skills Source: https://docs.fortrabbit.com/platform/automation/agent-skills Reviewed: 2026-08-24 > fortrabbit agent skills give a coding agent the platform workflows: setup, deployment, database sync, remote SSH and provisioning. The skills work with [Claude Code](/integrations/ai-coding/claude-code) and [OpenAI Codex](/integrations/ai-coding/codex). GitHub Copilot has basic support. - [github.com/fortrabbit/agent-skills](https://github.com/fortrabbit/agent-skills) - source code The skills are recommended but not required. An agent can work with fortrabbit through the [CLI](/platform/automation/cli) or the [MCP server](/platform/automation/mcp) alone. The package ships two skills: - `fortrabbit` - Deployment, SSH, database sync discovery, provisioning - `fortrabbit-api-access` - Connect to [MCP](/platform/automation/mcp) or [API](/platform/automation/api) ## Use cases - An agent should deploy, sync a database, or run remote commands - The agent keeps guessing at platform conventions - Onboarding a project should be guided, not looked up ## Install ### Via GitHub CLI Requires [GitHub CLI](https://cli.github.com/) v2.90.0 or later. Install globally — available across all projects: ```shell gh skill install fortrabbit/agent-skills fortrabbit --agent claude-code --scope user ``` One command installs one skill, so run it a second time for the access skill: ```shell gh skill install fortrabbit/agent-skills fortrabbit-api-access --agent claude-code --scope user ``` ### Install via curl This installs both skills in one go: ```shell curl -fsSL https://raw.githubusercontent.com/fortrabbit/agent-skills/main/install.sh | sh ``` See the [GitHub repo](https://github.com/fortrabbit/agent-skills) for per-project installs, other agents, and update options. ## Uninstall Ask the agent to remove the skills: ```shell /fortrabbit uninstall ``` That runs the `uninstall.sh` the installer placed next to the skill. The script lists what it will delete and asks before removing anything. Running it directly does the same: ```shell # global install ~/.claude/skills/fortrabbit/uninstall.sh # project install, from the project root .claude/skills/fortrabbit/uninstall.sh ``` One run covers both skills and both agents — `fortrabbit` and `fortrabbit-api-access` under `~/.claude/skills` and `~/.agents/skills`. A project install also drops the Copilot instructions at `.github/instructions/fortrabbit.instructions.md`. A skill installed with `gh skill install` arrives without that script, because the GitHub CLI has no remove command. Deleting the directory is enough: ```shell rm -rf ~/.claude/skills/fortrabbit ~/.claude/skills/fortrabbit-api-access ``` Removing the skills leaves an MCP connection untouched. That comes off separately, described under uninstall on the [MCP server](/platform/automation/mcp) page. ## Commands Invoke the skill from an agent with `/fortrabbit` followed by a command: | Command | Description | | -------------- | ------------------------------------------------------------------------------------------------------- | | `start` | Detect project state and guide to the next step | | `connect` | First-time setup: account, app, SSH key, connection test | | `mcp` | Discover, provision and diagnose apps through the MCP server | | `deploy` | Trigger a deployment via [deploy hook](/platform/deployment/deploy-hook) or Git push | | `sync up` | Rsync all project files to the remote environment | | `sync down` | Rsync all project files from the remote environment | | `db up` | Upload the local database to the remote environment | | `db down` | Download the remote database to the local environment | | `content up` | Rsync CMS content to the remote environment | | `content down` | Rsync CMS content from the remote environment | | `ssh` | Run a remote command via [SSH](/platform/code-access/ssh) (artisan, craft console, Composer) | | `update` | Check for and install the latest version | | `uninstall` | Remove the installed skill files | | `help` | Show all available commands | ## Connect the MCP server Connecting is optional — the skills work over SSH without it. With a connection the agent can list apps, create apps and environments, and read deployment logs without a shell. Setup is one command per client, then an approval in the browser; no token is copied or stored: :BlockLink{title="MCP setup instructions" path="/mcp" property="www"} The `fortrabbit-api-access` skill also walks through it when asked. Either way, the command only writes configuration — the browser approval follows on the first connection, which the [MCP server](/platform/automation/mcp) page covers along with the tools behind it. Ask the agent to list the apps on the account to confirm the connection works. ## Scripts and CI Where a browser flow does not fit — a CI job, a shell script, an MCP client without OAuth support — a public API token takes its place. The `fortrabbit-api-access` skill looks for one in `FORTRABBIT_API_TOKEN` or a git-ignored `.env` before asking, and never writes it to a file that gets committed. ## Requirements - `ssh` and `rsync` available locally - On Windows, WSL is required for rsync and the install script; SSH works natively on Windows 10+ --- - [Automation overview](/platform/automation/intro) - [AI coding assistants](/integrations/ai-coding/intro) - [Claude Code integration](/integrations/ai-coding/claude-code) - [Codex integration](/integrations/ai-coding/codex) - [Agentic engineering](/workflows/agentic-engineering)