Agent skills
Reviewed
🤖 🤖
Let your AI agent figure the details.
fortrabbit agent skills extend coding agents with domain knowledge: Guided setup, deployment, database sync, remote SSH commands, and MCP-based provisioning.
The skills work with Claude Code and OpenAI Codex. GitHub Copilot has basic support.
- github.com/fortrabbit/agent-skills - source code
The skills are recommended but not required. An agent can work with fortrabbit through the CLI or the MCP server alone.
The package ships two skills:
fortrabbit- Deployment, SSH, database sync discovery, provisioningfortrabbit-api-access- Connect to MCP or 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 v2.90.0 or later. Install globally — available across all projects:
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:
gh skill install fortrabbit/agent-skills fortrabbit-api-access --agent claude-code --scope user
Install via curl
This installs both skills in one go:
curl -fsSL https://raw.githubusercontent.com/fortrabbit/agent-skills/main/install.sh | sh
See the GitHub repo for per-project installs, other agents, and update options.
Uninstall
Ask the agent to remove the skills:
/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:
# 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:
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 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 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 (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:
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 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
sshandrsyncavailable locally- On Windows, WSL is required for rsync and the install script; SSH works natively on Windows 10+