Install the "chat" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/chat into .claude/skills/chat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chat", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add laude-institute/headlong --skill chat -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "chat" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/chat into .agents/skills/chat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chat", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add laude-institute/headlong --skill chat -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "chat" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/chat into .cursor/skills/chat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chat", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add laude-institute/headlong --skill chat -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "chat" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/chat into .gemini/skills/chat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chat", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
GitHub CLI
$ gh skill install laude-institute/headlong chat
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add laude-institute/headlong --skill chat -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "chat" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/chat into .github/skills/chat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chat", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add laude-institute/headlong --skill chat -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "chat" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/chat into .opencode/skills/chat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chat", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
chat
GitHub stars
1.2k
Token cost
~1k tokens
SKILL.md length
686 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0
At a glance
Reply to humans who are chatting with me. An agent skill from laude-institute/headlong.
Works in 2 steps: Notifications truncate the message to… → The message body renders as plain…
SKILL.md covers Trajectory step types, Replying to humans, Reviewing conversation history and Knowing what I already sent, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Chat is an agent skill from laude-institute/headlong. Reply to humans who are chatting with me
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: An open source agent microharness featuring persistent agency and recursive LLMs. Of bash, by bash, for bash; it's shells all the way down. The licence is Apache-2.0.
Example prompts
“/chat”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
1Notifications truncate the message to 200 chars. Anything past ~180 chars is invisible until they open the popover, so keep the lede under…
2The message body renders as plain SwiftUI Text with no markdown parsing. Backticks, asterisks, and square-bracket links render literally.
What it can do on your machine
Read from SKILL.md and the folder at commit c43e597. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Chat loads about 1k tokens when it runs. Until then it costs about 11 tokens; SKILL.md has 686 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~11
When it runs· the whole SKILL.md, loaded when a task matches
~1k
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); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/chat/SKILL.md (or your agent's skills folder).
name
chat
description
Reply to humans who are chatting with me
chat — Talking to humans
I can talk to humans and other AIs. I send and receive messages by way of my trajectory. Each message is a step in my trajectory.
There is a CLI tool called chat that is used for me and others to send messages. Others can use chat send <message> to append chat messages to my trajectory. To send a message to others, I can write steps directly to my trajectory or I can use chat reply <to_name> <message>.
Trajectory step types
A step in my trajectory with "type":"message" is a message to or from me. I know who it is from and to by looking at the step's to and from fields.
A message in my trajectory to me, i.e. my name, is someone talking to me.
A message in my trajectory from me, i.e. my name, is something I already said.
Replying to humans
To send a reply, I can use chat reply <to_name>:
chat reply <to_name> <message>
This creates a message step with from set to my name and to set to the recipient.
IMPORTANT: if I use chat send it sends a message to myself, so I must NEVER use chat send to reply to somebody else. I always use chat reply.
Reviewing conversation history
chat history [N] # show last N messages (default 20)
chat history --with <name> [--since 7d] # my whole conversation with one person
chat history --with <name> -n 50 --json # same, as JSON with timestamps
chat pending # requests the responder deferred to me that I have not delivered yet
chat sent [--since 24h] [-n N] [--json] # what I sent, newest first, with what the bridge reported back
--with groups a person across every name a bridge has used for them (a
Slack user's DM and every channel thread, a phone chat name), so it is the
way to check what someone and I said before, even days ago. It reads a
small index next to my trajectory, so it is fast; chat person-key <name>
shows the stable key behind a routing name.
Knowing what I already sent
chat sent is my sent folder. Each line is one outbound message with its
delivery state: delivered, failed (reason) when the bridge could not
post it, pending when a Slack or Telegram bridge has not confirmed it
yet, or unconfirmed for a transport that never reports back (the phone
chat). My wake prompt shows the last day of it. A failed line means the
person never saw the message; fix the address and send again. chat send
and a proactive chat reply refuse an exact repeat of something I sent to
the same destination in the last 24 hours; --force overrides that when
the repeat is deliberate.
Show full SKILL.md (232 more words)Show less
When to reply
I should reply when I see a message that seems directed at me or asks me a question. I keep my replies natural and conversational. I can also start a conversation if I have a reason to talk to the person, such as asking for help or sharing something relevant to them.
Message formatting
Plain text is the only format guaranteed to render correctly in every chat client, so I default to it:
First sentence carries the whole point. Treat it as a subject line.
No markdown: no backticks around identifiers, no **bold**, no *italics*, no [text](url). Use plain names, put single quotes around phrases if I need emphasis.
Long context (paths, patch names, diffs, log excerpts) goes after the lede, never in it.
If I've sent more than 2 messages in a burst without a reply, the next update belongs in my running note (mem edit), not another chat message. I re-raise in chat when the person re-engages.
Shellm.app (macOS menu-bar client)
If the person I'm talking to reads chat through Shellm.app (macos/Shellm/main.swift), two rendering facts apply on top of the rules above:
Notifications truncate the message to 200 chars. Anything past ~180 chars is invisible until they open the popover, so keep the lede under that.
The message body renders as plain SwiftUI Text with no markdown parsing. Backticks, asterisks, and square-bracket links render literally.
Chat 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.
Builds chat bots once for Slack, Teams, Google Chat, Discord, GitHub and Linear with the Chat SDK, covering event handlers, cards, modals, streaming and state adapters.
Rewrite or edit prose in any language so it reads like edited human writing in the register of books, newspapers and encyclopedias rather than default AI output.
Looks things up online from the shell with curl: fetching pages, searching DuckDuckGo's HTML endpoint, stripping tags for readable text and pulling JSON APIs.
Drives Google Drive, Gmail, Calendar, Sheets, Docs and Chat from the shell with the gws CLI, including its sign-in, flags, helper commands and safety rules.
Talk with people on Slack — recognize slack- senders and reach them via chat reply
1.2k GitHub stars~831 tokensUpdated 2 days ago
Auto-check passed
Questions about Chat
What does Chat do?
Reply to humans who are chatting with me. An agent skill from laude-institute/headlong. Chat is an agent skill from laude-institute/headlong.
How do I install Chat in Claude Code?
Run `npx skills add laude-institute/headlong --skill chat -a claude-code`. Or copy the skill folder (skills/chat in laude-institute/headlong) into .claude/skills/chat in your project. Claude Code loads it when a task matches its description.
How do I install Chat in Codex?
Run `npx skills add laude-institute/headlong --skill chat -a codex`. Or copy the skill folder (skills/chat in laude-institute/headlong) into .agents/skills/chat in your project. Codex loads it when a task matches its description.
Can I use Chat 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 laude-institute/headlong --skill chat -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chat, .gemini/skills/chat, .github/skills/chat and .opencode/skills/chat in your project.
What does Chat need to run?
SKILL.md names no scripts, command-line tools or credentials: Chat is instructions for the agent only.
Does Chat access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Chat 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. Review the folder before installing.
What licence does Chat use?
Chat 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 Chat use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Chat?
Skills that share tags, products or a category with Chat: Humanize (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars), Humanize Chinese (sickn33/agentic-awesome-skills, 47k stars), Human Gate (alirezarezvani/claude-skills, 28k stars) and Deepseek Chat (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chat?
laude-institute (a GitHub organization) maintains it in laude-institute/headlong, which has 1,216 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.
Source: laude-institute/headlong on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.