Tribe coordination — check sessions, send messages, view health/history. Use when user says /tribe.
From tribenpx claudepluginhub beorn/bearly --plugin tribeThis skill is limited to using the following tools:
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Designs KPI dashboards with metrics selection (MRR, churn, LTV/CAC), visualization best practices, real-time monitoring, and hierarchy for executives, operations, and product teams.
Transforms raw data into narratives with story structures, visuals, and frameworks for executive presentations, analytics reports, and stakeholder communications.
Cross-session coordination. Parse the subcommand from ARGUMENTS.
| User Says | Action |
|---|---|
/tribe | tribe_sessions() — show who's online |
/tribe status | tribe_sessions() + tribe_health() — full dashboard |
/tribe health | tribe_health() — warnings, silent members, unread counts |
/tribe sessions | tribe_sessions() — list active sessions |
/tribe sessions --all | tribe_sessions(all=true) — include dead sessions |
/tribe send <to> <message> | tribe_send(to, message) — send notify message |
/tribe assign <to> <message> | tribe_send(to, message, type="assign") — assign work |
/tribe query <to> <message> | tribe_send(to, message, type="query") — ask a question |
/tribe broadcast <message> | tribe_broadcast(message) — message everyone |
/tribe history | tribe_history(limit=20) — recent messages |
/tribe history <name> | tribe_history(with=name, limit=20) — messages with specific session |
/tribe rename <new_name> | tribe_rename(new_name) — rename this session |
/tribe whoami | Show this session's name, role, and domains |
/tribe db <sql> | sqlite3 <tribe-db-path> "<sql>" — raw query |
/tribe log | sqlite3 <tribe-db-path> "SELECT sender, recipient, type, substr(content,1,80), datetime(ts/1000,'unixepoch','localtime') FROM messages ORDER BY ts DESC LIMIT 20" |
/tribe events | sqlite3 <tribe-db-path> "SELECT type, session, datetime(ts/1000,'unixepoch','localtime') FROM events ORDER BY ts DESC LIMIT 20" |
/tribe sync | Broadcast asking all members to ensure their work is tracked (see below) |
/tribe rollcall | Broadcast asking all members to report name, status, and current work |
Keep output concise. For tribe_sessions, format as a table. For tribe_health, highlight warnings. For tribe_history, show as a chat log with timestamps.
/tribe sync ProtocolBroadcast this message to all members:
Sync check: report your current status.
1. Your session name (/rename) and Claude session ID (echo $CLAUDE_SESSION_ID)
2. What you're working on — beads/tasks created, updated, closed this session
3. BLOCKERS: anything you're blocked on, what's blocking, and what would unblock
4. NEEDS: anything another member could help with (review, info, shared resources)
5. INFRASTRUCTURE: active worktrees, in-flight refactors, running test suites, unpublished packages, or shared config changes
Reply to chief with your summary.
After responses come in:
/tribe rename to a domain name/tribe rollcall ProtocolBroadcast this message:
Roll call: please report your current session name (/rename), what you're working on, and your status (idle/busy/blocked). Reply with tribe_send to chief.
Collect responses and present as a table.
claude --dangerously-load-development-channels server:tribe/tribe whoami reads from the MCP server instructions (check if "chief" or "member" appears)~/.local/share/tribe/tribe.db (user-level default), or .beads/tribe.db if a .beads/ dir exists, or explicit via --db/TRIBE_DB