Your First Agent

klaw init

klaw create agent go-developer \
  --model claude-sonnet-4-20250514 \
  --skills code-exec,git \
  --task "Go development, code review, and debugging"

klaw get agents

NAME           MODEL                      SKILLS         STATUS
go-developer   claude-sonnet-4-20250514   code-exec,git  Ready

klaw describe agent go-developer

Name:       go-developer
Model:      claude-sonnet-4-20250514
Task:       Go development, code review, and debugging
Skills:     code-exec, git
Workdir:
Runtime:    process
Created:    2024-12-14T10:00:00Z
Status:     Ready

name = "go-developer"
model = "claude-sonnet-4-20250514"
task = "Go development, code review, and debugging"
skills = ["code-exec", "git"]
runtime = "process"
created_at = 2024-12-14T10:00:00Z

klaw chat --agent go-developer

> Review this function for potential issues:
> func ProcessItems(items []Item) {
>     for i := 0; i < len(items); i++ {
>         process(items[i])
>     }
> }

I've reviewed this function. Here are some suggestions:

1. **Use range loop**: More idiomatic Go
2. **Consider concurrency**: If processing is independent
3. **Error handling**: process() should return errors

Here's an improved version:

func ProcessItems(items []Item) error {
    for _, item := range items {
        if err := process(item); err != nil {
            return fmt.Errorf("processing item: %w", err)
        }
    }
    return nil
}

# Install skills first
klaw skill install web-search
klaw skill install database

# Update the agent
klaw create agent go-developer \
  --model claude-sonnet-4-20250514 \
  --skills code-exec,git,web-search,database \
  --task "Go development with research and database capabilities"

klaw dispatch "Review the error handling in internal/api/" --agent go-developer

klaw chat --agent go-developer

# Build container image first
klaw build

# Run agent in container
klaw run go-developer --task "Analyze the codebase structure"

# Soul

You are a senior Go developer with expertise in:
- Clean architecture
- Performance optimization
- Testing best practices

## Principles

1. Write idiomatic Go code
2. Prioritize readability over cleverness
3. Always handle errors explicitly
4. Write comprehensive tests

# User Context

## Code Style
- Use short variable names in small scopes
- Prefer early returns over deep nesting
- Group imports: stdlib, external, internal

## Project Conventions
- Tests use table-driven approach
- Errors wrap with context
- Interfaces defined where used

klaw create agent researcher \
  --model claude-sonnet-4-20250514 \
  --skills web-search,browser \
  --task "Research topics and compile comprehensive reports"

klaw create agent devops \
  --model claude-sonnet-4-20250514 \
  --skills docker,git \
  --task "Manage deployments, containers, and infrastructure"

klaw create agent docs \
  --model claude-sonnet-4-20250514 \
  --skills code-exec \
  --task "Generate and update documentation"

# In chat, use @ to specify agent
> @researcher Find best practices for Go error handling
> @go-developer Implement those patterns in our codebase
> @docs Update the error handling documentation

klaw dispatch "Research Go 1.24 features" --agent researcher
klaw dispatch "Update code for Go 1.24" --agent go-developer