agent-hiring

Automates hiring specialist agents with permanent contracts for task execution.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jota-batuta/batuta-dots --skill agent-hiring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-hiring
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/agent-hiring
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill agent-hiring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The main agent never executes tasks directly. For every task, it "hires" a specialist agent. Agents are .md files in .claude/agents/ -- PERMANENT contracts that persist across projects. This skill defines the contract-based hiring system.

Core Features & Use Cases

  • Detect need: Analyze tasks to determine required expertise and map to capabilities.
  • Check existing agents: Search both project-local and global agent libraries, read frontmatter, verify skills are current.
  • Propose hire: Require explicit user approval before creating a new contract file under .claude/agents/.
  • Create agent file: Write a dedicated .md contract with name, description, tools, model, skills, maxTurns, and file-ownership guidelines.
  • Invoke: Spawn the hired agent with a defined file ownership scope for task execution.

Quick Start

When a task arises, trigger the agent-hiring workflow to select or create a specialized contract and assign explicit file ownership.

Frequently Asked Questions about agent-hiring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create persistent agent contracts in Claude for task automation?

To create persistent agent contracts, you write a dedicated .md file under the .claude/agents/ directory with frontmatter defining the name, description, tools, model, skills, and maxTurns. This contract persists across projects and is invoked when the main agent hires a specialist.

How does the agent hiring workflow execute tasks in Claude?

The agent hiring workflow executes tasks by having the main agent analyze the task, search local and global agent libraries for existing specialists, and require explicit user approval before creating a new contract file and spawning the hired agent with defined file ownership.

What do I need to define in a Claude agent frontmatter contract?

A Claude agent frontmatter contract requires defining the agent's name, description, tools, model, skills, and maxTurns. It must also enforce explicit file ownership guidelines to scope the hired agent's execution permissions.

Can I reuse specialist agents across different projects with persistent contracts?

Yes, specialist agents are saved as .md files in .claude/agents/ and function as permanent contracts that persist across projects. The workflow searches both project-local and global agent libraries to verify existing skills before proposing a new hire.

Why does the main agent not execute tasks directly in this automation workflow?

The main agent does not execute tasks directly because the system uses a contract-based hiring model where every task is delegated to a specialist agent. This requires explicit user approval and file ownership scoping to ensure controlled, specialized task execution.

Best way to scale agent automation across multiple projects using contracts?

The best way to scale agent automation is using permanent .md contract files in .claude/agents/. The system searches local and global libraries, verifies skills are current, and prompts for approval before creating new contracts, ensuring consistent specialist invocation across projects.