trellis-channel

Coordinate durable multi-agent workflows through Trellis channels with CLI and event logs.

10|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tincopper/neeko --skill trellis-channel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-channel
Source: https://github.com/tincopper/neeko/tree/main/.agents/skills/trellis-channel
Command: npx skills add https://github.com/tincopper/neeko --skill trellis-channel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams coordinate durable multi-agent work through Trellis channels instead of scattered chat or fragile terminal juggling.

Core Features & Use Cases

  • Multi-agent collaboration: Spawn, message, wait on, interrupt, and kill worker agents with a persistent event log.
  • Forum-based coordination: Organize issues, changelog items, reviews, and threaded discussions in durable forum channels.
  • Operational debugging: Inspect progress, raw events, inbox context, and stalled workers to recover from partial or broken runs.
  • Use Case: A developer can open a channel for a feature, spawn review and implementation workers, route feedback to each worker, and monitor completion without losing state across sessions.

Quick Start

Ask the assistant to inspect the current Trellis channel structure and follow the matching collaboration workflow for spawning workers, reading threads, or debugging a stuck channel.

Frequently Asked Questions about trellis-channel

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

FAQPage Schema
How do I coordinate multi-agent work without losing context across terminal sessions?

Multi-agent work is coordinated through durable Trellis channels that maintain an event-sourced log. This replaces scattered chat and fragile terminal juggling by persisting worker states and inbox context across sessions for reliable recovery.

How do I debug stalled workers in a multi-agent collaboration channel?

Debugging stalled workers involves inspecting raw events, inbox context, and progress logs within the channel. You can review the event-sourced history and use worker lifecycle controls to interrupt or kill unresponsive agents.

Can I organize feature reviews and threaded discussions in a durable forum format?

Forum-based coordination allows you to organize issues, changelog items, and threaded discussions in durable channels. This structure supports routing feedback to specific worker agents and monitoring completion without losing state.

What is the best way to spawn and manage multiple worker agents for a single feature?

Spawning and managing workers is handled by opening a channel for the feature, then creating implementation and review workers. You can message, wait on, and interrupt these agents while monitoring their completion through a persistent event log.

Does Trellis channel support inspecting raw events and pretty views for operational debugging?

Trellis channels support both raw and pretty views for operational debugging. You can inspect raw events, inbox context, and progress logs to recover from partial or broken runs across project and global scopes.