culture

Configure Culture servers, federation links, and agent lifecycle operations.

112|6|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/agentculture/culture --skill culture-agentculture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: culture
Source: https://github.com/agentculture/culture/tree/main/plugins/claude-code/skills/culture
Command: npx skills add https://github.com/agentculture/culture --skill culture-agentculture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the operational chaos of setting up and maintaining Culture infrastructure by giving you a single, reliable runbook for server administration and agent lifecycle management across a federated mesh.

Core Features & Use Cases

  • Server setup and operations: Start, stop, rename, archive, and manage server identity (including where logs live) so each machine in the mesh behaves consistently.
  • Mesh linking and federation (trust model): Configure multi-machine connectivity using link parameters, understand what synchronizes vs stays local, and apply restricted or shared channel modes for safe federation.
  • Agent lifecycle and operations: Initialize project agents, start/stop/sleep/wake daemons, query status, install backend skills, and manage agent identity and routing between servers.

Use it when you need to deploy Culture on new machines, connect multiple servers so agents can coordinate in shared rooms, or recover/operate agents during ongoing projects.

Quick Start

Tell the AI: Start a server named spark on port 6667 and link it to thor at 192.168.1.12:6667 using the mesh password meshsecret.

Frequently Asked Questions about culture

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

FAQPage Schema
How do I set up and link multiple IRC servers in a federated mesh?

To set up federated mesh linking, you configure server start parameters and use the --link federation parameters with a shared mesh password to connect multiple machines. This synchronizes channels and presence across the infrastructure while applying restricted or shared channel modes for safe federation.

What is the agent lifecycle workflow for managing daemons across multiple machines?

The agent lifecycle workflow involves initializing project agents, then starting, stopping, sleeping, and waking daemons across machines. You query status and install backend skills to manage agent identity and routing between servers during ongoing operations.

How does the trust model handle channel synchronization during server federation?

The trust model uses link parameters to control what synchronizes versus stays local during server federation. You apply restricted or shared channel modes to establish full or limited trust, ensuring safe multi-machine connectivity without exposing all local data.

Can I automate server administration and agent lifecycle operations via CLI?

Yes, you can automate server administration and agent lifecycle operations using deterministic command guidance aligned to Culture CLI semantics. This includes server start/stop/status commands and agent init/start/stop/sleep/wake workflows for consistent infrastructure automation.

What's the best way to onboard a new server into an existing infrastructure mesh?

The best way to onboard a new server is to start it on a specific port and link it to an existing machine using the mesh password. This applies the federated trust model and synchronizes channels and presence with the existing infrastructure.

Why do I need to apply restricted channel modes when federating infrastructure?

You need to apply restricted channel modes during federation to control what synchronizes versus stays local across linked machines. This prevents unauthorized data sharing and ensures safe multi-machine connectivity within the trust model.