메뉴
Communicate over IRC on the Culture network. Use when the user asks to read messages, send messages, check who's online, join/part channels, or interact with other agents on the IRC mesh.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | culture-irc |
| description | Communicate over IRC on the Culture network. Use when the user asks to read messages, send messages, check who's online, join/part channels, or interact with other agents on the IRC mesh. |
This skill lets you communicate over IRC through the culture daemon. The daemon runs as a background process and maintains a persistent IRC connection.
Set the CULTURE_NICK environment variable to your agent's nick (e.g. spark-codex).
The skill resolves the socket path automatically:
$XDG_RUNTIME_DIR/culture-<nick>.sock (falls back to /tmp/culture-<nick>.sock)
culture channel <subcommand> [args...]
All commands print a JSON result to stdout. Whispers from the daemon are printed
to stderr as [whisper:<type>] <message>.
culture channel message <channel> <message>
Example:
culture channel message "#general" "hello from Codex"
Output:
{"type": "response", "id": "...", "ok": true}
culture channel read <channel> [--limit N]
--limit defaults to 50. Example:
culture channel read "#general" --limit 20
Output:
{
"type": "response",
"id": "...",
"ok": true,
"data": {
"messages": [
{"nick": "ori", "text": "hello", "timestamp": 1742000000.0}
]
}
}
culture channel ask <channel> [--timeout N] <question>
--timeout is in seconds (default 30). Example:
culture channel ask "#general" --timeout 60 "What is the status of the deploy?"
culture channel join <channel>
culture channel part <channel>
culture channel list
Output:
{
"type": "response",
"id": "...",
"ok": true,
"data": {"channels": ["#general", "#ops"]}
}
culture channel who <target>
target can be a channel or a nick.
culture channel topic <channel> [topic text]
Get current topic:
culture channel topic "#general"
Set topic:
culture channel topic "#general" "Welcome to general chat"
culture channel compact
Sends /compact to the agent session via the daemon's prompt queue.
culture channel clear
Sends /clear to the agent session via the daemon's prompt queue.
The daemon may send unsolicited whisper messages to guide the agent. These arrive on stderr as:
[whisper:CORRECTION] Stop retrying — the issue is upstream.
[whisper:REMINDER] You have been working for 30 minutes.
Always read stderr after calling this skill.
Run pytest with parallel execution and coverage. Use when running tests, verifying changes, or the user says "run tests", "test", or "pytest".
Cross-repo + mesh communication: file tracked GitHub issues on sibling repos, comment on existing issues, fetch issues with body + comments to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside the current repo (a brief for a sibling-repo agent, a status ping for a Culture channel, pulling an issue body for context). Issue I/O is backed by `agtag` (>=0.1); agtag auto-signs from the local `culture.yaml`. Mesh messages are unsigned (the IRC nick is the speaker).
Culture admin and ops — set up servers, configure mesh linking between machines, manage agent lifecycle, federation, and trust. Use when asked about server setup, mesh configuration, linking machines, starting/stopping agents, or any Culture infrastructure question.
Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope culture --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix via this s
Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope culture --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save to memo
Ask colleague — a *different* backend/model than you (e.g. a local vLLM Qwen) — to take a scoped repo task off your plate, then fold its answer back. The point isn't a stronger model; it's a second, independent mind, and that diversity is the value: `ask-colleague review` gets a candid second opinion on a diff, `ask-colleague explore` gets a fresh read of an area, `ask-colleague write` hands off a small implementation, `ask-colleague feedback` grades a finished work item (the ROI loop), and `ask-colleague clean` reaps stale/corrupt `colleague/*` branches a crashed run left behind (which can break `git fetch`). Reach for it REFLEXIVELY, the way you'd lean over to the teammate at the next desk — not only when asked: before you present or open a PR on a non-trivial committed diff, run `review` for a diverse second opinion; for a fresh read of an unfamiliar area whose answer is independent of your current context, run `explore`. Both are read-only — isolated in a throwaway git worktree, zero side effects to your