hire

AI Community

Skill notes

When to Use

User says something like: "I want to hire a new agent" "I need help with X" (where X implies a new agent role) "Let's add someone to the team" /hire

3 core questions, asked one at a time:

Q1: "What do you need help with?" Let them describe the problem, not a job title. "I'm drowning in code reviews" beats "I need a code reviewer." Listen for: scope, implied autonomy level, implied tools needed Q2: "What's their personality? Formal, casual, blunt, cautious, creative?" Or frame it as: "If this were a human colleague, what would they be like?"

Q4: Dynamic (optional)

After Q1-Q3, assess whether anything is ambiguous or needs clarification. If so, ask ONE follow-up question tailored to what's unclear. Examples: "You mentioned monitoring - should they alert you immediately or batch updates?" "They'll need access to your codebase - any repos that are off-limits?" "You said 'casual' - are we talking friendly-professional or meme-level casual?" If Q1-Q3 were clear enough, skip Q4 entirely.

Summary Card

After the interview, present a summary: Then ask: "Want to tweak anything, or are we good?"

Model Selection

Before finalizing, select an appropriate model for the agent.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@diegosouzapw · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Discover available models

Run `openclaw models list` or check the gateway config to see what's configured.

02
Step 2: Categorize by tier

Map discovered models to capability tiers: Tier · Models (examples) · Best for reasoning · claude-opus-*, gpt-5*, gpt-4o, deepseek-r1 · Strategy, advisory, complex analysis, architecture balanced · claude-sonnet-*, gpt-4-turbo, gpt-4o-mini · Research, writing, general tasks fast · claude-haiku-*, gpt-3.5*, local/ollama · High volume, simple tasks, drafts

03
Step 3: Match role to tier

Based on the interview: Heavy reasoning/advisory/strategy → reasoning tier Research/writing/creative → balanced tier Code-focused → code tier (or balanced if not available) High-volume/monitoring → fast tier

04
Step 4: Select and confirm

Pick the best available model for the role. In the summary card, add: If multiple good options exist or you're unsure, ask: "For a [role type] role, I'd suggest [model] (good balance of capability and cost). Or [alternative] if you want [deeper reasoning / faster responses / lower cost]. Preference?"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.