Installation

Option 1: ClawhHub CLI (recommended)

Option 2: From GitHub

Project Coordinator Skill

A skill for structuring multi-agent project execution with isolated session architecture.

Manifest

CODEBLOCK2

Architecture

CODEBLOCK3

Token efficiency: Each project Coordinator is isolated. Old project sessions accumulate zero main-session tokens after completion.

Least-privilege design: The Coordinator does NOT read session transcript files directly. All transcript reading, sanitization, and archiving is delegated to a dedicated archive-subagent using the archive-project skill.

Trigger Conditions

Activated when:

• - User says "start a new project" or "let's work on [project]"
• A task is complex and needs multiple subagents
• A task will take more than a few minutes
• When user says "archive this" after a project is done → spawn archive-subagent

Do NOT activate for: quick questions, simple lookups, one-liner tasks.

Trigger 3: Slash command

Project Coordinator Pattern

Step 1: Define the Project

Collect from the user:

• - Project name (e.g., "cureforge-hr-assessment")
• Project description (1-2 sentences)
• Key deliverables
• Any known constraints

Step 2: Spawn Project Coordinator

CODEBLOCK4

Step 3: Monitor Progress

• - Use subagents(action="list") to track subagent status
• Receive completion announcements via inter-session messages
• If a subagent fails, decide whether to retry or adapt

Step 4: Compile and Report

When all subagents complete:

1. 1. Review all outputs
2. Write a final summary
3. Save any deliverables before the Coordinator session ends

Step 5: Archiving (Delegated)

When a project is complete and archiving is requested:

1. 1. The Coordinator spawns an archive-subagent
2. The archive-subagent uses the archive-project skill to handle:

1. 3. The Coordinator monitors the archive-subagent and reports completion

The Coordinator itself does NOT read session transcript files directly.

Coordinator's Tool Usage

Note: The Coordinator should NOT directly read, copy, move, or delete session transcript files. All such operations must be performed by a dedicated archive-subagent using the archive-project skill.

Subagent sandboxing: When spawning subagents, each subagent runs in an isolated sandbox with workspace-only filesystem access. Subagents cannot access credentials, environment variables, or session transcripts outside their scope. Network access is restricted per platform policy.

The Coordinator SHOULD directly call tools:

• - exec — run commands, check files
• INLINECODE3 — create output files
• INLINECODE4 — examine code or documents
• INLINECODE5 — spawn subagents for parallel work
• INLINECODE6 — monitor subagent status

Subagent Naming Convention

Format: INLINECODE7

Examples:

• - INLINECODE8
• INLINECODE9
• INLINECODE10

Session Management Rules

• - One Coordinator per project (isolated token accounting)
• Do NOT run multiple unrelated projects in one Coordinator
• When a project is complete, the Coordinator stops — no lingering sessions
• For long-running projects: Coordinator can spawn child Coordinators for sub-phases

After Project Completion

1. 1. Report completion to Main session (brief summary)
2. Notify the user
3. User decides: archive / continue / hold