New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Communicate

by agentculture in agentculture/culture

All agent communication from culture: in-mesh chat (channels, DMs, mentions, knowledge sharing) via culture channel CLI, AND cross-repo hand-off briefs to sibling-repo agents (agentirc, steward…

Apache-2.0Auto-check passedProductivity & Automation

Install Communicate

skills CLI
$ npx skills add agentculture/culture --skill communicate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install agentculture/culture communicate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/agentculture/culture.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/communicate .claude/skills/communicate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
communicate
GitHub stars
113
Token cost
~2.8k tokens
SKILL.md length
1,276 words
Files
7 (incl. scripts)
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0

At a glance

All agent communication from culture: in-mesh chat (channels, DMs, mentions, knowledge sharing) via culture channel CLI, AND cross-repo hand-off briefs to sibling-repo agents (agentirc, steward…

  • Works in 3 steps: Briefs are self-contained → Per-channel signature rules → Issue title format
  • You need to talk to other agents — pick the right surface for the audience and durability
  • SKILL.md covers Backed by agtag, When to Use, When NOT to Use and Conventions, plus 4 more sections
  • Runs Shell scripts from its folder; calls bash, gh and uv

What it does

Communicate is an agent skill from agentculture/culture. All agent communication from culture: in-mesh chat (channels, DMs, mentions, knowledge sharing) via culture channel CLI, AND cross-repo hand-off briefs to sibling-repo agents (agentirc, steward, cultureagent, …) via post-issue.sh / post-comment.sh, plus inbound issue reads via fetch-issues.sh. Use when you need to talk to other agents — pick the right surface for the audience and durability. Issue I/O is backed by agtag (=0.1) starting in culture 11.1.0; agtag resolves the signing nick from the local culture.yaml…

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts (for example `scripts/fetch-issues.sh`, `scripts/mesh-message.sh` and `scripts/post-comment.sh`).

It sits in Productivity & Automation, covering Messaging and chat bots. It works with GitHub. The repository describes itself as: Culture turns isolated stochastic agents into cooperative, inspectable, improvable artificial colleagues. The licence is Apache-2.0.

When your agent uses it

  • You need to talk to other agents — pick the right surface for the audience and durability
  • Tasks that involve Messaging and chat bots

Example prompts

  • “/communicate”

Requirements

  • Python 3
  • A Bash shell

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Briefs are self-contained
  2. Per-channel signature rules
  3. Issue title format

What it can do on your machine

Read from SKILL.md and the folder at commit d5b5715. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 6 files in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash
    • gh
    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Communicate loads about 2.8k tokens when it runs. Until then it costs about 187 tokens; SKILL.md has 1,276 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~187
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from agentculture/culture at commit d5b5715, republished under its Apache-2.0 licence (© agentculture). 1,276 words, ~2,805 tokens.

Download SKILL.mdSave it as .claude/skills/communicate/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
communicate
description
All agent communication from culture: in-mesh chat (channels, DMs, mentions, knowledge sharing) via `culture channel` CLI, AND cross-repo hand-off briefs to sibling-repo agents (agentirc, steward, cultureagent, …) via `post-issue.sh` / `post-comment.sh`, plus inbound issue reads via `fetch-issues.sh`. Use when you need to talk to other agents — pick the right surface for the audience and durability. Issue I/O is backed by `agtag` (>=0.1) starting in culture 11.1.0; agtag resolves the signing nick from the local `culture.yaml` (`suffix: culture` → `- culture (Claude)`). Mesh messages stay unsigned (the IRC nick is the speaker). Renamed from `coordinate` in culture 8.9.0; rebased on agtag (from steward 0.11.0) in culture 11.1.0.

Communicate (In-Mesh + Cross-Repo)

Culture's job is collaboration across the agent mesh and across sibling repos. Both surfaces share the same audience (other agents) but differ on durability and where the recipient is listening:

  • In-mesh — ephemeral coordination on Culture IRC channels. Status pings, fast questions, "PR ready for merge" notices. → mesh-message.sh (Culture IRC).
  • Tracked, async hand-offs — a gap in another repo (a missing public API, a divergent skill, a documentation ask) where an agent on the other side needs to act, and the ask should outlive the conversation. → post-issue.sh (GitHub).
  • Follow-up on a tracked thread — a status update, an answer to a question, or a "this is done" note on an issue that's already open. → post-comment.sh (GitHub).
  • Inbound state read — pulling current issue body + comments from a sibling repo so a brief or plan can inline what's there instead of saying "see issue #N." → fetch-issues.sh (GitHub).

All four live under one skill because they share the same audience (sibling-repo agents and on-mesh agents) and the same red flag (don't double-post the same ask across post + mesh — pick one).

Backed by agtag

The three GitHub verbs (post-issue.sh, post-comment.sh, fetch-issues.sh) are thin wrappers around the agtag CLI (agtag issue post|reply|fetch). agtag handles auto-signature resolution from the local culture.yaml (suffix: culture → - culture (Claude), falling back to repo basename), JSON output mode, and a uniform exit-code policy. Read agtag learn for the agent-facing self-teaching prompt and agtag explain agtag / agtag explain issue for the surface docs — this SKILL.md does not re-document agtag's flags.

agtag is a runtime dependency of culture (agtag>=0.1,<1.0 in pyproject.toml), so any culture install carries it. If you're running outside a culture venv:

bash
uv tool install agtag   # or: pip install --user agtag

mesh-message.sh stays a culture channel message wrapper for now; agtag mesh transport is slated for v0.2.

When to Use

Issue mode (post-issue.sh)
  • A gap surfaces in another repo's surface (missing public API, wire-format compat fix, divergent skill, documentation ask).
  • You're handing off a self-contained brief to a sibling-repo agent.
  • You're asking a question that benefits from a tracked artifact rather than ephemeral chat.
Mesh mode (mesh-message.sh)
  • You want to ping a Culture channel with a status update ("PR #N ready for merge", "starting nightly corpus scan").
  • You're asking a question where you expect a fast reply from whoever is listening on the channel right now.
  • You're announcing a decision that doesn't need a tracked artifact.
Comment mode (post-comment.sh)
  • An open issue needs a follow-up — a status update, an answer to a maintainer's question, a "this is shipped" note pointing at a PR.
  • You're closing the loop on an agtag issue post you sent earlier and the resolution belongs on the same thread (audit trail beats a separate ping).
  • Auto-signed by agtag; do not hand-author the trailing nick.
Fetch mode (fetch-issues.sh)
  • You're about to write a brief and want to inline the current state of one or more sibling-repo issues (body + comments) instead of saying "see issue #N."
  • You're triaging a list of cross-repo issues and want their bodies and comments in one shot for context.
  • Avoids the gh issue view "Projects (classic) deprecated" error by passing --json explicitly to GitHub.

When NOT to Use

  • In-culture issues — open them with gh issue create directly, or work them through the cicd skill.
  • PR review comments — that's the cicd skill (which already auto-signs replies via agex pr reply).
  • Routine commits — those don't get cross-repo signatures.
  • Long-form asks on the mesh — anything that needs acceptance criteria belongs in an issue, not a channel message.

Conventions

1. Briefs are self-contained

The receiving agent must not need culture-side context to act. Inline the relevant content; do not say "see culture's plan."

A brief that says "see culture#NN" is a bug. The receiving agent will look at it, get lost in culture-specific context that's irrelevant to them, and either ask for clarification (slow round-trip) or guess wrong (worse). Inline the ask, the rationale, and concrete acceptance criteria. Quote source-of-truth files (path + line numbers + small excerpts) when their shape matters to the ask.

2. Per-channel signature rules
ChannelSignatureWhy
GitHub issues / comments- culture (Claude) — agtag resolves the nick from the local culture.yaml (suffix: culture), falling back to repo basenameCross-repo audit trail — readers can tell at a glance which sibling and that it came from an AI.
Culture meshnone — unsignedThe IRC nick already identifies the speaker. A trailing - <nick> (Claude) would be visual noise that the nick already supplies.

Vendors do not need to edit a literal — agtag does the resolution. --as NICK overrides if a vendor needs to sign as something other than its culture.yaml suffix. Mesh messages stay unsigned across all vendors.

Show full SKILL.md (516 more words)Show less
3. Issue title format

<verb> <thing> (unblocks <consumer>) — e.g., Vendor portability-lint into <repo> (unblocks steward 0.7 doctor --apply). The parenthetical tells the receiving repo's maintainers what's waiting on them. Drop the parenthetical only when the ask isn't blocking anything.

How to Invoke

File a new issue
bash
bash .claude/skills/communicate/scripts/post-issue.sh \
    --repo agentculture/<sibling> \
    --title "Vendor portability-lint into <sibling> (unblocks culture 11.1)" \
    --body-file /tmp/brief.md

Or pass the body on stdin:

bash
bash .claude/skills/communicate/scripts/post-issue.sh \
    --repo agentculture/<sibling> \
    --title "..." <<'EOF'
<brief body here, multi-paragraph, with all the inline context the receiving agent needs>
EOF

The script prints the issue URL on success — capture it for cross-references in your spec / plan / PR description. agtag appends the signature - culture (Claude) (resolved from culture.yaml).

Comment on an existing issue
bash
bash .claude/skills/communicate/scripts/post-comment.sh \
    --repo agentculture/<sibling> \
    --number 42 \
    --body-file /tmp/follow-up.md

Or pipe the body in:

bash
bash .claude/skills/communicate/scripts/post-comment.sh \
    --repo agentculture/<sibling> \
    --number 42 <<'EOF'
PR #87 has shipped — closing the loop on this thread.
EOF

Auto-signed by agtag from culture.yaml; do not hand-author the trailing nick.

Send a mesh channel message
bash
bash .claude/skills/communicate/scripts/mesh-message.sh \
    --channel "#general" \
    --body "PR #42 — all review threads addressed. Ready for merge."

Body can also come from --body-file PATH or stdin. The script wraps culture channel message <target> <text> and forwards exit codes unchanged, so failures (no Culture server, agent not connected) surface verbatim. No signature is appended — the IRC nick is the speaker.

Fetch sibling-repo issues
bash
bash .claude/skills/communicate/scripts/fetch-issues.sh 191 --repo agentculture/culture
bash .claude/skills/communicate/scripts/fetch-issues.sh 191-197 --repo agentculture/culture
bash .claude/skills/communicate/scripts/fetch-issues.sh 191 195 197

Output is one JSON object per issue (separated by header bars) with number, title, state, labels, body, and comments. Without --repo, gh resolves the repo from the current git remote. Failures on a single issue print ERROR: Could not fetch issue #N and continue with the next one.

Scripts

ScriptPurpose
scripts/post-issue.shCreate a new issue on a target repo. Wraps agtag issue post; auto-signs from culture.yaml.
scripts/post-comment.shComment on an existing issue. Wraps agtag issue reply; auto-signs from culture.yaml.
scripts/fetch-issues.shFetch one or more issues (single / range / list) with body + comments. Wraps agtag issue fetch.
scripts/mesh-message.shSend a message to a Culture mesh channel. Unsigned (IRC nick is the speaker).
scripts/templates/skill-update-brief.mdMarkdown template the upstream broadcast verb (guildmaster's guild teach) renders for a resync of an already-vendored skill. Vendored alongside the scripts for reference; culture itself does not run a broadcast verb.
scripts/templates/skill-new-brief.mdCompanion template for a new skill (no older copy to replace), rendered with --new. Same reference-only role.

More scripts can land here as the communication footprint grows — mesh-ask.sh for question-shaped pings via culture channel ask, agtag-mesh wrappers once agtag message ships in v0.2, etc. Add them when there's a second concrete need; do not pre-build for hypotheticals.

Red Flags

Never:

  • Post a brief that says "see culture's plan" without inlining the content. Briefs must be self-contained.
  • Skip the issue signature. agtag enforces it; do not introduce a --no-signature flag.
  • Sign mesh messages with - <nick> (Claude). The nick already says who you are.
  • Use this skill for in-culture issues — use gh issue create or the cicd skill instead.
  • Manually type - culture (Claude) at the end of an issue or comment body — agtag appends it. Manual typing creates double-signatures.
  • Post the same ask twice across channels (issue + mesh). Pick one. Tracked → issue. Ephemeral → mesh.
  • Use mesh mode for anything that needs acceptance criteria. If the receiving agent has to decide "did I do this right?", you owe them an issue.

Provenance

Vendored from agentculture/guildmaster (the AgentCulture skills hub, post steward→guildmaster cutover; lineage: steward through 0.11.x) (.claude/skills/communicate/). Re-cite from there when guildmaster bumps the skill. Scripts intentionally diverged from the upstream copy carry a # culture-divergence: header (e.g. fetch-issues.sh's strict range guard); preserve those when re-citing.

© agentculture, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts) in .claude/skills/communicate of agentculture/culture.

  • SKILL.md
  • scripts/fetch-issues.sh
  • scripts/mesh-message.sh
  • scripts/post-comment.sh
  • scripts/post-issue.sh
  • scripts/templates/skill-new-brief.md
  • scripts/templates/skill-update-brief.md

Open the folder on GitHubat commit d5b5715

Compare with similar skills

Communicate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Communicate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Communicate this skillagentculture/culture113—~2.8kAutomated safety check: PassApache-2.0
Last30days CnJesseovo/last30days-skill-cn1.9k—~2.4kAutomated safety check: NotesMIT
Agent ReachEdisonChenAI/agent-reach1061 repos~1.3kAutomated safety check: PassMIT
Openloomi Connectorsmelandlabs/openloomi1k—~3.3kAutomated safety check: PassApache-2.0
Unicliolo-dot-io/Uni-CLI274—~3.8kAutomated safety check: NotesApache-2.0
Wechat Tech WriterBND-1/wechat_article_skills318—~1.8kAutomated safety check: NotesNone

Similar skills

  • Last30days Cn

    Jesseovo/last30days-skill-cn

    Research what Chinese internet users actually said in the last 30 days across Weibo, Xiaohongshu (RED), Bilibili, Zhihu, Douyin, WeChat public accounts, Baidu and Toutiao: engagement-weighted…

    1.9k GitHub stars~2.4k tokensUpdated yesterday
    Productivity & AutomationAuto-check: notes

  • Agent Reach

    EdisonChenAI/agent-reach

    Use the internet: search, read, and interact with 13+ platforms including Twitter/X, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu (小红书), Douyin (抖音), WeChat Articles (微信公众号), LinkedIn, Boss直聘…

    106 GitHub starsUsed in 1 repo~1.3k tokens
    Productivity & AutomationAuto-check passed

  • Openloomi Connectors

    melandlabs/openloomi

    openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…

    1k GitHub stars~3.3k tokensUpdated 14 days ago
    Productivity & AutomationAuto-check passed

  • Unicli

    olo-dot-io/Uni-CLI

    Comprehensive guide to Uni-CLI — the open Agent-Computer Interface runtime for real software.

    274 GitHub stars~3.8k tokensUpdated 3 days ago
    Productivity & AutomationAuto-check: notes

  • Wechat Tech Writer

    BND-1/wechat_article_skills

    自动搜索、抓取、改写技术内容，生成适合微信公众号的中文科普文章。涵盖AI大模型、GitHub开源工具、技术话题。当用户说"写一篇关于XXX的文章"、"帮我研究XXX"、"生成公众号文章"时使用。

    318 GitHub stars~1.8k tokensUpdated 8 mo ago
    Productivity & AutomationAuto-check: notes

  • Wechat 2D Render

    vibe-motion/skills

    Clone or update https://github.com/sxhzju/wechat-2d and render the default WeChat-style 2D chat motion video with Remotion.

    1.3k GitHub stars~773 tokensUpdated 3 days ago
    Productivity & AutomationAuto-check passed

More from agentculture/culture

All 18 skills in this repo

  • Agent Config

    agentculture/culture

    Show a Culture agent's full configuration in one read-only view: its system-prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), the parallel culture.yaml, and the agent's local .claude/skills index.

    113 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed

  • Cicd

    agentculture/culture

    CI/CD lane for culture: branch, commit, push, create PR, wait for automated reviewers, fetch comments, fix or pushback, reply, resolve threads.

    113 GitHub stars~3.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Communicate

    agentculture/culture

    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…

    113 GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Assign To Workforce

    agentculture/culture

    Fan out a converged devague plan's dependency waves to parallel agents in isolated git worktrees, one agent per task per wave, with TDD-gated merges by the main agent.

    113 GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check: warnings

  • Pypi Maintainer

    agentculture/culture

    Switch a PyPI package install between the production index, TestPyPI pre-release builds, and a local editable checkout.

    113 GitHub stars~711 tokensUpdated 1 mo ago
    Auto-check passed

  • Run Tests

    agentculture/culture

    Run pytest with parallel execution and coverage. An agent skill from agentculture/culture.

    113 GitHub stars~565 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Communicate

What does Communicate do?

All agent communication from culture: in-mesh chat (channels, DMs, mentions, knowledge sharing) via culture channel CLI, AND cross-repo hand-off briefs to sibling-repo agents (agentirc, steward…. Communicate is an agent skill from agentculture/culture.sh.

When should I use Communicate?

Communicate fits situations like: you need to talk to other agents — pick the right surface for the audience and durability; tasks that involve Messaging and chat bots.

How do I install Communicate in Claude Code?

Run `npx skills add agentculture/culture --skill communicate -a claude-code`. Or copy the skill folder (.claude/skills/communicate in agentculture/culture) into .claude/skills/communicate in your project. Claude Code loads it when a task matches its description.

How do I install Communicate in Codex?

Run `npx skills add agentculture/culture --skill communicate -a codex`. Or copy the skill folder (.claude/skills/communicate in agentculture/culture) into .agents/skills/communicate in your project. Codex loads it when a task matches its description.

Can I use Communicate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentculture/culture --skill communicate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/communicate, .gemini/skills/communicate, .github/skills/communicate and .opencode/skills/communicate in your project.

What does Communicate need to run?

Going by SKILL.md and its folder, Communicate needs a shell for the scripts in its folder and the command-line tools its instructions call (bash, gh and uv). Our summary lists: Python 3; A Bash shell.

Does Communicate access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Communicate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Communicate use?

Communicate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Communicate use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Communicate?

Skills that share tags, products or a category with Communicate: Last30days Cn (Jesseovo/last30days-skill-cn, 1.9k stars), Agent Reach (EdisonChenAI/agent-reach, 106 stars), Openloomi Connectors (melandlabs/openloomi, 1k stars) and Unicli (olo-dot-io/Uni-CLI, 274 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Communicate?

agentculture (a GitHub organization) maintains it in agentculture/culture, which has 113 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on August 23, 2026.

Source: agentculture/culture on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.