gclaw-conventions

Implement gCLaW agent hierarchy, tool wrapping, and board-mediated communication rules.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Skobyn/g.c.l.a.w --skill gclaw-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gclaw-conventions
Source: https://github.com/Skobyn/g.c.l.a.w/tree/main/skills/gclaw-conventions
Command: npx skills add https://github.com/Skobyn/g.c.l.a.w --skill gclaw-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gclaw-conventions codify the standard patterns that wrap and orchestrate a fleet of agents on top of ADK, including the management hierarchy, tool integration, and board-mediated communication rules, plus soul overlays and the registration path for agent configurations.

Core Features & Use Cases

  • Defines a uniform three-tier agent hierarchy: Root Orchestrator, Managers (Workspace, Dev, Home, Comms, Research, Profile, Content), and dynamic Specialists.
  • Enforces architectural rules: Agents communicate via the kanban board, Managers act as routers while Specialists perform work, and agents are wired through a centralized factory and override system.
  • Provides a consistent file-based and runtime agent model: agents.md, soul.md, heartbeat, and wiring to the orchestrator for runtime changes.

Quick Start

Follow the three-tier patterns and file structure to add or modify agents in gclaw, referencing the underlying ADK API patterns for implementation.

Frequently Asked Questions about gclaw-conventions

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

FAQPage Schema
How do I structure a multi-tier agent hierarchy for scalable orchestration?

A scalable agent hierarchy uses three tiers: a Root Orchestrator, static Managers acting as routers, and dynamic Specialists performing the work. This structure prevents bottlenecks by delegating execution downward while maintaining centralized control.

How does board-mediated communication work in an agent orchestration system?

Board-mediated communication enforces a rule where agents interact exclusively through a kanban board rather than direct messaging. This decouples agents, ensuring Managers route tasks and Specialists execute work without tight runtime dependencies.

What is the best way to define agent configurations at runtime?

The best way to define agent configurations is using file-backed definitions like agents.md and soul.md. These files specify heartbeat configurations and soul overlays, wired through a centralized factory to the orchestrator for runtime overrides.

Do I need a centralized factory to wire agents into the orchestrator?

Yes, a centralized factory is required to wire agents into the orchestrator. It manages the instantiation of the hierarchy, applies soul overlays, and handles runtime override behavior, ensuring consistent tool wrapping and messaging patterns.

When should I use dynamic Specialists instead of static Managers in an agent fleet?

Use dynamic Specialists for executing specific tasks and static Managers for routing work across domains like Dev, Research, or Comms. Specialists handle the workload while Managers maintain board communication and task delegation.

What are soul overlays and how do they affect agent behavior?

Soul overlays are configurations defined in soul.md that customize an agent's behavioral patterns within the orchestrator. They allow runtime modifications to agent personas and operational rules without altering the underlying factory wiring.