AI Employees
Review external AI employee profiles, compare them, and decide what to shortlist or adapt for Unujual.
Current state
External AI employee catalog
What you can do today
Review, compare, and shortlist candidates manually
What this is not
Not a live Unujual agent runtime
Next milestone
Identify high-fit employees for adaptation
Review framing
These profiles are sourced from AI-tools_OS/agency-agents/. They are candidate AI employees reviewed inside Unujual, not official employees, not live, and not deployable.
Treat this page as a curation surface for comparison and judgment. The goal is to understand fit before any adaptation workflow exists.
What to do here
Use this surface to review external AI employee profiles with enough context to compare them quickly.
- 1Browse or search AI employee profiles.
- 2Compare fit by domain, category, and summary.
- 3Decide which profiles are worth shortlisting or adapting later.
Done means
- you identify promising AI employees for future adaptation
- or clearly reject low-fit profiles without confusing them with official Unujual agents
Status meaning
Workflow statuses are conceptual in this MVP. They explain review intent, not live product state.
Observed
Discovered and reviewed as source material.
Shortlisted
Promising for future internal adaptation.
Adapted
Intended to become a Unujual-shaped internal employee later.
Reference only
Not official, not deployable, and not live.
Why this matters
This page exists to make external agent material usable inside Unujual without pretending it is already productized.
- discover promising AI employee patterns faster
- compare external agent roles before adaptation
- build future internal hires from reviewed source material
Explore the catalog
Find candidate AI employees
Search and filter external profiles to compare fit, review their framing, and narrow the set worth discussing for future adaptation.
Employee Catalog
Candidate profiles sourced from external reference material.
Employee Profile
Review what this profile is, why it may matter, and the source it came from.
🔌 Integrations
This entry is an external AI employee profile reviewed inside Unujual as source material. It is useful for comparison and future adaptation decisions, but it is not an official Unujual employee and it is not wired to execution.
Domain
Integrations
Category
README
Source tool
agency-agents
Why this profile may matter
This directory contains The Agency integrations and converted formats for supported agentic coding tools.
Workflow status meaning
Current review state is conceptual only. This MVP defaults every profile to Observed, while Shortlisted and Adapted remain future states for a later workflow.
This profile has been discovered and reviewed as source material.
Reserved for promising profiles worth future adaptation.
Reserved for future Unujual-shaped internal employees.
Source reference
Escaped source markdown is shown here for reference only. It stays secondary to the profile summary and is not rendered as live content.
AI-tools_OS/agency-agents/integrations/README.md
# 🔌 Integrations
This directory contains The Agency integrations and converted formats for
supported agentic coding tools.
## Supported Tools
- **[Claude Code](#claude-code)** — `.md` agents, use the repo directly
- **[GitHub Copilot](#github-copilot)** — `.md` agents, use the repo directly
- **[Antigravity](#antigravity)** — `SKILL.md` per agent in `antigravity/`
- **[Gemini CLI](#gemini-cli)** — extension + `SKILL.md` files in `gemini-cli/`
- **[OpenCode](#opencode)** — `.md` agent files in `opencode/`
- **[OpenClaw](#openclaw)** — `SOUL.md` + `AGENTS.md` + `IDENTITY.md` workspaces
- **[Cursor](#cursor)** — `.mdc` rule files in `cursor/`
- **[Aider](#aider)** — `CONVENTIONS.md` in `aider/`
- **[Windsurf](#windsurf)** — `.windsurfrules` in `windsurf/`
- **[Kimi Code](#kimi-code)** — YAML agent specs in `kimi/`
## Quick Install
```bash
# Install for all detected tools automatically
./scripts/install.sh
# Install a specific home-scoped tool
./scripts/install.sh --tool antigravity
./scripts/install.sh --tool copilot
./scripts/install.sh --tool openclaw
./scripts/install.sh --tool claude-code
# Gemini CLI needs generated integration files on a fresh clone
./scripts/convert.sh --tool gemini-cli
./scripts/install.sh --tool gemini-cli
```
For project-scoped tools such as OpenCode, Cursor, Aider, and Windsurf, run
the installer from your target project root as shown in the tool-specific
sections below.
## Regenerating Integration Files
If you add or modify agents, regenerate all integration files:
```bash
./scripts/convert.sh
```
---
## Claude Code
The Agency was originally designed for Claude Code. Agents work natively
without conversion.
```bash
cp -r <category>/*.md ~/.claude/agents/
# or install everything at once:
./scripts/install.sh --tool claude-code
```
See [claude-code/README.md](claude-code/README.md) for details.
---
## GitHub Copilot
The Agency also works natively with GitHub Copilot. Agents can be copied
directly into `~/.github/agents/` and `~/.copilot/agents/` without conversion.
```bash
./scripts/install.sh --tool copilot
```
See [github-copilot/README.md](github-copilot/README.md) for details.
---
## Antigravity
Skills are installed to `~/.gemini/antigravity/skills/`. Each agent becomes
a separate skill prefixed with `agency-` to avoid naming conflicts.
```bash
./scripts/install.sh --tool antigravity
```
See [antigravity/README.md](antigravity/README.md) for details.
---
## Gemini CLI
Agents are packaged as a Gemini CLI extension with individual skill files.
The extension is installed to `~/.gemini/extensions/agency-agents/`.
Because the Gemini manifest and skill folders are generated artifacts, run
`./scripts/convert.sh --tool gemini-cli` before installing from a fresh clone.
```bash
./scripts/convert.sh --tool gemini-cli
./scripts/install.sh --tool gemini-cli
```
See [gemini-cli/README.md](gemini-cli/README.md) for details.
---
## OpenCode
Each agent becomes a project-scoped `.md` file in `.opencode/agents/`.
```bash
cd /your/project && /path/to/agency-agents/scripts/install.sh --tool opencode
```
See [opencode/README.md](opencode/README.md) for details.
---
## OpenClaw
Each agent becomes an OpenClaw workspace containing `SOUL.md`, `AGENTS.md`,
and `IDENTITY.md`.
Before installing, generate the OpenClaw workspaces:
```bash
./scripts/convert.sh --tool openclaw
```
Then install them:
```bash
./scripts/install.sh --tool openclaw
```
See [openclaw/README.md](openclaw/README.md) for details.
---
## Cursor
Each agent becomes a `.mdc` rule file. Rules are project-scoped — run the
installer from your project root.
```bash
cd /your/project && /path/to/agency-agents/scripts/install.sh --tool cursor
```
See [cursor/README.md](cursor/README.md) for details.
---
## Aider
All agents are consolidated into a single `CONVENTIONS.md` file that Aider
reads automatically when present in your project root.
```bash
cd /your/project && /path/to/agency-agents/scripts/install.sh --tool aider
```
See [aider/README.md](aider/README.md) for details.
---
## Windsurf
All agents are consolidated into a single `.windsurfrules` file for your
project root.
```bash
cd /your/project && /path/to/agency-agents/scripts/install.sh --tool windsurf
```
See [windsurf/README.md](windsurf/README.md) for details.
---
## Kimi Code
Each agent is converted to a Kimi Code CLI agent specification (YAML format with
separate system prompt files). Agents are installed to `~/.config/kimi/agents/`.
Because the Kimi agent files are generated from the source Markdown, run
`./scripts/convert.sh --tool kimi` before installing from a fresh clone.
```bash
./scripts/convert.sh --tool kimi
./scripts/install.sh --tool kimi
```
### Usage
After installation, use an agent with the `--agent-file` flag:
```bash
kimi --agent-file ~/.config/kimi/agents/frontend-developer/agent.yaml
```
Or in a specific project:
```bash
cd /your/project
kimi --agent-file ~/.config/kimi/agents/frontend-developer/agent.yaml \
--work-dir /your/project
```
See [kimi/README.md](kimi/README.md) for details.