Command Palette

Search conversations, projects, playbooks, and more

Agents

Configure specialized AI assistants for your team.

Agents are specialized AI assistants configured for your team's stack and standards. crewkit syncs agents to .claude/agents/ so every developer uses the same configuration.

Use role modifiers (coaching, collaborative, autonomous) to control how much guidance an agent provides based on the developer's experience level.

Create an agent

The fastest way to create an agent is through the dashboard.

  1. Go to Resources in the sidebar
  2. Click New Resource and select Agent
  3. Give it a name and slug (e.g., rails-expert)
  4. Write the agent prompt in markdown
  5. Click Create

The agent is now available at the organization level. Run crewkit code in any project to sync it.

Agent file format

Agents are markdown files with optional YAML frontmatter:

---
name: rails-expert
description: Expert Ruby on Rails developer
---

You are an expert Ruby on Rails developer working on a production application.

## Standards

MCP server

Expose your project's institutional memory to any MCP-capable agent with crewkit mcp serve.

Skills

Reusable task-specific capabilities for Claude Code.

On this page

Create an agentAgent file formatRole modifiersAgent tiersSync behaviorImport local agentsCLAUDE.mdNext steps
- Follow Rails conventions (RESTful routes, thin controllers, fat models)
- Use MiniTest for testing
- Extract business logic into services
## Project Context
This is a Rails API application using MySQL and Sidekiq.

The frontmatter is optional but helps with display and discovery in the dashboard.

Role modifiers

Each organization role can have a coaching mode that modifies agent behavior:

  • Coaching — Agent explains decisions, suggests alternatives, asks before acting. For junior developers.
  • Collaborative — Agent discusses trade-offs but acts with more autonomy. For mid-level developers.
  • Autonomous — Agent acts independently, only explains when asked. For senior developers.

Role modifiers are injected as a prefix to the agent prompt during sync. The agent file itself doesn't change.

Agent tiers

Agents can exist at three levels:

TierScopeExample
PlatformAll crewkit usersrails-expert (crewkit-provided)
OrganizationYour teamacme-rails-expert (team customizations)
ProjectOne projectcustomer-portal-agent (project-specific)

See Inheritance for how these tiers merge.

Sync behavior

When you run crewkit code, the CLI:

  1. Fetches effective agent configs from the API (platform + org + project merged)
  2. Writes them to .claude/agents/ in your project
  3. Uses SHA-256 checksums to avoid overwriting local changes
  4. Backs up modified files to .claude/.backups/

If you've edited an agent locally and the server has a newer version, crewkit preserves your local copy and writes the server version alongside it.

Import local agents

Already have agent files? Import them to crewkit:

crewkit resources import                # Interactive import
crewkit resources import --auto-import  # Import all without prompting
crewkit resources import --dry-run      # Preview what would import

CLAUDE.md

The CLAUDE.md file in your project root is not an agent — it's project-level instructions that Claude Code reads automatically. crewkit doesn't manage CLAUDE.md directly, but playbook conventions can inject content into it.

Next steps

  • Skills
  • Inheritance model
  • Role modifiers and team setup