moai-cc-agents

Create and manage Claude Code sub-agents with structured agent files.

1|Updated Jul 28, 2025
One-click install
npx skills add https://github.com/kivo360/quickhooks --skill moai-cc-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-cc-agents
Source: https://github.com/kivo360/quickhooks/tree/main/.claude/skills/moai-cc-agents
Command: npx skills add https://github.com/kivo360/quickhooks --skill moai-cc-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides creating and orchestrating sub-agents for specialized tasks within Claude Code.

Core Features & Use Cases

  • Agent Personas: Design specialist agent roles.
  • Proactive Triggers: Define triggers for autonomous work.
  • Security & Handoffs: Structured handoffs and permissions.

Quick Start

Define a new code-review agent and set a trigger for automatic code quality checks.

Frequently Asked Questions about moai-cc-agents

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

FAQPage Schema
How do I create sub-agents to automate specialized tasks in Claude Code?

Sub-agents are specialized Claude Code instances designed for focused tasks like code review or debugging. Create them by defining agent personas, setting proactive triggers, and configuring tool permissions in standardized agent files stored under .claude/agents. This enables autonomous task execution with structured handoffs.

What's the best way to orchestrate multiple agents for different coding tasks?

Orchestrate agents by designing distinct personas for each task domain, establishing trigger patterns that activate agents autonomously, and implementing least-privilege tool access controls. Use standardized agent-file structures to coordinate handoffs between agents and maintain governance over execution modes and permissions.

How do I set up proactive triggers for autonomous agent work?

Proactive triggers activate agents automatically based on defined conditions. Configure trigger patterns in your agent configuration to specify when agents execute for code quality checks, debugging, or architecture tasks. Combine triggers with autonomy rules and collaboration guidelines to balance automated execution with controlled handoffs.

Can I control what tools and permissions each sub-agent has access to?

Yes. Apply least-privilege tool access by explicitly defining which tools each agent can use in its configuration. This security model ensures agents operate only within their intended scope, with structured handoffs to other agents when tasks require elevated permissions or cross-domain expertise.

What governance and functional requirements apply to agent design?

Agent design requires specifying functional and technical requirements including agent templates, trigger patterns, autonomy levels, collaboration rules, and tool-permission controls. Follow governance checklists to document execution modes, handoff protocols, and security boundaries for each agent in your .claude/agents directory.

Do I need prior orchestration experience to build agents in Claude Code?

This Skill targets users building specialized agents and assumes familiarity with Claude Code. While not prerequisite, understanding your automation goals—such as code review, debugging, or domain-specific work—helps frame agent personas and triggers effectively from the start.