Agent skill

Octo Messaging

by Mininglamp-OSS in Mininglamp-OSS/octo-cli

Messaging domain — send/edit/sync messages, read receipts, message search (search/all/files/media/around/groups, in-channel or cross-channel), groups and threads (User Bot), and event polling.

Apache-2.0Auto-check passedBackend & APIs

Install Octo Messaging

skills CLI

$ npx skills add Mininglamp-OSS/octo-cli --skill octo-messaging -a claude-code

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

GitHub CLI

$ gh skill install Mininglamp-OSS/octo-cli octo-messaging --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/Mininglamp-OSS/octo-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/octo-messaging .claude/skills/octo-messaging && 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/

Paste into Claude Code

Install the "octo-messaging" agent skill from https://github.com/Mininglamp-OSS/octo-cli/tree/main/skills/octo-messaging into .claude/skills/octo-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octo-messaging", 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.

$skill-installer

$skill-installer install https://github.com/Mininglamp-OSS/octo-cli/tree/main/skills/octo-messaging

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 Mininglamp-OSS/octo-cli --skill octo-messaging -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Mininglamp-OSS/octo-cli octo-messaging --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Mininglamp-OSS/octo-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/octo-messaging .agents/skills/octo-messaging && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "octo-messaging" agent skill from https://github.com/Mininglamp-OSS/octo-cli/tree/main/skills/octo-messaging into .agents/skills/octo-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octo-messaging", 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 Mininglamp-OSS/octo-cli --skill octo-messaging -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Mininglamp-OSS/octo-cli octo-messaging --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Mininglamp-OSS/octo-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/octo-messaging .cursor/skills/octo-messaging && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "octo-messaging" agent skill from https://github.com/Mininglamp-OSS/octo-cli/tree/main/skills/octo-messaging into .cursor/skills/octo-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octo-messaging", 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.

gemini skills install

$ gemini skills install https://github.com/Mininglamp-OSS/octo-cli.git --path skills/octo-messaging

--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 Mininglamp-OSS/octo-cli --skill octo-messaging -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Mininglamp-OSS/octo-cli octo-messaging --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Mininglamp-OSS/octo-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/octo-messaging .gemini/skills/octo-messaging && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "octo-messaging" agent skill from https://github.com/Mininglamp-OSS/octo-cli/tree/main/skills/octo-messaging into .gemini/skills/octo-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octo-messaging", 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 Mininglamp-OSS/octo-cli octo-messaging

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 Mininglamp-OSS/octo-cli --skill octo-messaging -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Mininglamp-OSS/octo-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/octo-messaging .github/skills/octo-messaging && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "octo-messaging" agent skill from https://github.com/Mininglamp-OSS/octo-cli/tree/main/skills/octo-messaging into .github/skills/octo-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octo-messaging", 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 Mininglamp-OSS/octo-cli --skill octo-messaging -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Mininglamp-OSS/octo-cli octo-messaging --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Mininglamp-OSS/octo-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/octo-messaging .opencode/skills/octo-messaging && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "octo-messaging" agent skill from https://github.com/Mininglamp-OSS/octo-cli/tree/main/skills/octo-messaging into .opencode/skills/octo-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octo-messaging", 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: octo-messaging
GitHub stars: 918
Token cost: ~2.9k tokens
SKILL.md length: 808 words
Files: 1
Skills in repo: 11
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Messaging domain — send/edit/sync messages, read receipts, message search (search/all/files/media/around/groups, in-channel or cross-channel), groups and threads (User Bot), and event polling.

Works in 6 steps: message — 4 core commands (+ 6 search… → group — 9 commands (both 5 / User Bot… → thread — 8 commands, User Bot only → …
Backend & APIs work in your project
SKILL.md covers 1. message — 4 core commands…, message search — 6 subcommands, 2. group — 9 commands (both 5… and 3. thread — 8 commands, User…, plus 3 more sections
Calls jq

What it does

Octo Messaging is an agent skill from Mininglamp-OSS/octo-cli. Messaging domain — send/edit/sync messages, read receipts, message search (search/all/files/media/around/groups, in-channel or cross-channel), groups and threads (User Bot), and event polling. Covers App Bot DM-only constraints. Load after octo-shared.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs. The repository describes itself as: Metadata-driven CLI for AI Agent Bots — 48 operations across 7 domains, structured JSON envelope I/O, zero interactive prompts. The licence is Apache-2.0.

When your agent uses it

Backend & APIs work in your project

Example prompts

“/octo-messaging”

Workflow steps

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

message — 4 core commands (+ 6 search subcommands, see below)
group — 9 commands (both 5 / User Bot only 4)
thread — 8 commands, User Bot only
event — polling for inbound events
Error recovery cheatsheet
Schema lookup

What it can do on your machine

Read from SKILL.md and the folder at commit 6d21f11. 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
Shell commands in SKILL.md call:
- jq
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

Octo Messaging loads about 2.9k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 808 words of instructions outside code blocks.

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

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.

SKILL.md

The full file from Mininglamp-OSS/octo-cli at commit 6d21f11, republished under its Apache-2.0 licence (© Mininglamp-OSS). 808 words, ~2,946 tokens.

Download SKILL.mdSave it as .claude/skills/octo-messaging/SKILL.md (or your agent's skills folder).

name: octo-messaging
description: Messaging domain — send/edit/sync messages, read receipts, message search (search/all/files/media/around/groups, in-channel or cross-channel), groups and threads (User Bot), and event polling. Covers App Bot DM-only constraints. Load after octo-shared.
version: 0.4.1

octo-messaging — messages, groups, threads, events

Three related domains live here. They all call $OCTO_API_BASE_URL/v1/bot/* — except the message search family under a uk_ (user API key) token, which the CLI routes to /v1/user/* (real-person mount; see the message search section).

Domain	App Bot	User Bot
`message`	yes (DM only)	yes (DM + group + thread)
`group`	read-only	full
`thread`	blocked	full
`event`	yes	yes

Search capability (the message search family) is a separate axis by token kind:

Token	Can search?	Notes
`app_*`	no	CLI rejects locally with a `validation` error (not a server `FORBIDDEN`).
`bf_*`	yes	Searches as the bot; add `--on-behalf-of <uid>` for a real-person (OBO) view.
`uk_*`	yes	Real-person identity; routed to `/v1/user/*`.

Before attempting a write, confirm the token type with octo-cli config show — App Bot writes outside DM get FORBIDDEN from the server ("app bot does not support group operations").

1. `message` — 4 core commands (+ 6 search subcommands, see below)

bash

# Send a message. payload is a JSON object (not a flag) — pass it inside --data.
# payload.type is an INTEGER code (1=text); see the payload table below.
octo-cli message send --channel-id <cid> --channel-type 1 \
  --data '{"payload":{"type":1,"content":"hello"}}' \
  [--stream-no <n>] [--on-behalf-of <uid>]

# Edit by (message-id, channel-id, channel-type). content-edit is the new
# content, stored opaquely server-side — carry the new payload, same shape as send.
octo-cli message edit --message-id <mid> --message-seq <seq> \
  --channel-id <cid> --channel-type <t> \
  --content-edit '{"type":1,"content":"updated"}'

# Pull history for a channel. Use --data for non-trivial filters.
octo-cli message sync --data '{"channel_id":"ch_abc","channel_type":1,"limit":50}'

# Mark messages read.
octo-cli message read-receipt --channel-id <cid> --channel-type 1 \
  --message-ids m1 --message-ids m2

`channel-type` values

1 = direct (DM), 2 = group, 5 = thread.

App Bot restrictions (enforced server-side)

send accepts only channel-type=1; group/thread are rejected, and even for DM the bot must have a friend relationship with the recipient.
sync explicitly blocks channel-type=2.
edit and read-receipt work in DM; other scopes follow bot-kind rules.

`payload` shape

payload is an object (never auto-promoted to a flag). Wrap it under the top-level payload key and pass the whole body via --data '{"channel_id":"…","channel_type":1,"payload":{…}}' (or --data @file.json, --data @-).

payload.type is an integer code (NOT a string like "text"). Authoritative source: common.ContentType in octo-lib/common/msg.go (the server reads it as an int).

Chat content types:

type	meaning	common payload fields
1	Text	`content`
2	Image	`url, width, height`
3	GIF	`url, width, height`
4	Voice	`url, duration`
5	Video	`url, width, height, duration`
6	Location	`latitude, longitude`
7	Card	`uid, name`
8	File	`url, name, size`
11	MultipleForward	(merged-forward)
12	VectorSticker	(sticker)
13	EmojiSticker	(emoji sticker)
14	RichText	(rich text)
16	InviteJoinOrg	(org invite)

(System/notification types — 1000+ for group events, 2000 Tip — are server-generated, not sent by bots.) Text example: {"type":1,"content":"hello"}.

--on-behalf-of <uid> makes send/typing act as a user persona (OBO) — requires an active OBO grant + channel scope, else the server returns OBO not authorized.

message search — 6 subcommands

Full-text search over messages and files. Registered as message search, message search all|files|media|around|groups.

bash

# In-channel message search (payload.type in [1,11,14]).
octo-cli message search --chat-id <cid> --keyword "quarterly report" [--sort time_desc]

# Cross-channel message search (omit --chat-id). NOTE: without --chat-id the CLI
# routes to the cross-channel _search_global_messages endpoint, which is a MIXED
# feed (messages + files), so results may include file hits.
octo-cli message search --keyword "quarterly report"

# Messages + files (mixed feed) — in-channel or (no --chat-id) cross-channel.
octo-cli message search all --chat-id <cid> --keyword invoice

# Files only (payload.type=8), by filename / caption.
octo-cli message search files --chat-id <cid> --keyword "*.pdf"

# Images + videos (payload.type in [2,5]) — IN-CHANNEL ONLY, keyword NOT allowed.
octo-cli message search media --chat-id <cid> [--sort time_desc]

# Context window around an anchor message — IN-CHANNEL ONLY.
octo-cli message search around --chat-id <cid> --anchor-message-id <mid>

# Cross-channel aggregated overview (which channels matched) — CROSS-CHANNEL ONLY.
# Use it as level 1 of a two-step search: find matching channels, then pull
# messages per channel with `message search` / `message search all`.
octo-cli message search groups --keyword "quarterly report"

`--chat-id` decides in-channel vs cross-channel

With --chat-id → scoped to that channel.
Without --chat-id → search / search all / search files route to their cross-channel _search_global_* endpoints (CLI-side, in internal/client/search_route.go — not backend dispatch). Plain search cross-channel degrades to the mixed messages+files feed.
media and around require --chat-id (no cross-channel endpoint; the backend rejects a request without a channel_id). around also requires --anchor-message-id; media does not accept --keyword.
groups is cross-channel only and does not accept --chat-id.

Token subjects

bf_ (User Bot) — searches as the bot.
bf_ + --on-behalf-of <uid> — OBO: searches with that real person's visibility; requires an active OBO grant.
uk_ (user API key) — real-person identity; the CLI rewrites the path to /v1/user/*.
app_ (App Bot) — cannot search. The CLI rejects this locally (validation), before any request — distinct from a server-side FORBIDDEN.

Show full SKILL.md (306 more words)Show less

Filters and pagination

Rich filters (sender_ids, member_uids, content_types, sent_at_from/sent_at_to, file_exts, …) go through --data '{"filters":{…}}'. All families except around and groups paginate; the cursor travels in the request body (--page-all handles this).

2. `group` — 9 commands (both 5 / User Bot only 4)

Available to both bot types (5):

bash

octo-cli group list      [--space-id <sid>]               # groups the bot is a member of
octo-cli group get       <group_no>
octo-cli group members   <group_no>                        # paginated
octo-cli group md-get    <group_no>                        # group markdown description
octo-cli group md-update <group_no> --content "# Updated description"  # write, but bot_admin gate — not App-Bot-blocked

User Bot only (4):

bash

octo-cli group create        --members u1 --members u2 --name "eng" --creator u0
octo-cli group update        <group_no> --data '{"name":"new name"}'
octo-cli group member-add    <group_no> --members u3 --members u4
octo-cli group member-remove <group_no> --members u3

App Bot attempting any of the four write operations gets FORBIDDEN with message "app bot does not support group operations".

3. `thread` — 8 commands, User Bot only

Every thread operation calls validateBotGroupAccess() on the backend and rejects App Bot unconditionally. Don't attempt these with an app_* token.

bash

octo-cli thread create    <group_no> --name "Incident #42"
octo-cli thread list      <group_no>                          # paginated
octo-cli thread get       <group_no> <short_id>
octo-cli thread members   <group_no> <short_id>
octo-cli thread join      <group_no> <short_id>
octo-cli thread leave     <group_no> <short_id>
octo-cli thread md-get    <group_no> <short_id>
octo-cli thread md-update <group_no> <short_id> --content "# …"

The User Bot must be a member of the parent group.

4. `event` — polling for inbound events

bash

octo-cli event list                          # newest page
octo-cli event list --event-id 1234 --limit 50   # cursor = highest event-id seen
octo-cli event ack  <event_id>

Important: `event list` is a POST

Even though the semantics are "list", the handler is POST /v1/bot/events — the cursor travels in the body, not the query string. The CLI handles this; agents calling octo-cli api must use POST.

Standard poll loop

bash

cursor=0
while :; do
  batch=$(octo-cli event list --event-id "$cursor" --limit 100)
  # response shape: {ok, data:{status, results:[{event_id, event_type, message{...}}]}}
  echo "$batch" | jq -c '.data.results[]' | while read -r ev; do
    id=$(jq -r '.event_id' <<<"$ev")
    process "$ev"
    octo-cli event ack "$id"
    cursor=$id
  done
  sleep 2
done

--limit defaults to 20, caps at 100.

5. Error recovery cheatsheet

Symptom	Likely cause / fix
`FORBIDDEN` + `app bot does not support group…`	Switch to a User Bot (`bf_*`) or fall back to DM.
`send` → `permission` on DM	No friend relationship; add the bot as a friend first.
`sync` rejected with `channel-type=2`	App Bot cannot sync groups — use User Bot.
`VALIDATION_ERROR` on `send`	`payload` must be an object, not a string.
`event list` returns `data.results: []`	No events since the cursor; keep the cursor and poll again.
`validation` on any `message search` with an `app_*` token	App Bots cannot search — use `bf_` or `uk_`. (CLI-side reject, before the request.)
`media` search rejected with a non-empty keyword	`search media` does not accept `--keyword`; drop it.
`sort=relevance` rejected	`relevance` requires a non-empty `--keyword`.
`OBO not authorized` on `search --on-behalf-of`	No active OBO grant for that uid; grant it or drop `--on-behalf-of`.

6. Schema lookup

bash

octo-cli schema message.send
octo-cli schema message.search
octo-cli schema message.search.all
octo-cli schema group.members
octo-cli schema thread.create
octo-cli schema event.list

Files

Just SKILL.md in skills/octo-messaging of Mininglamp-OSS/octo-cli.

Open the folder on GitHubat commit 6d21f11

Compare with similar skills

Octo Messaging 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.

Octo Messaging compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Octo Messaging this skillMininglamp-OSS/octo-cli	918	—	~2.9k	Automated safety check: Pass	Apache-2.0	yesterday
Configuring Horizoncoollabsio/coolify	63k	4 repos	~898	Automated safety check: Pass	MIT	yesterday
Nestjs Best Practicesrolling-scopes/rsschool-app	10k	6 repos	~1.2k	Automated safety check: Pass	MIT	6 days ago
Sub2API AdminWei-Shaw/sub2api	44k	1 repos	~717	Automated safety check: Pass	LGPL-3.0	yesterday
Firecrawl Build Onboardingfirecrawl/firecrawl	190k	1 repos	~1.4k	Automated safety check: Notes	ISC	today
Obsidian BasesAtmosphere/atmosphere	3.8k	22 repos	~3.2k	Automated safety check: Pass	Apache-2.0	2 days ago

Similar skills

Configuring Horizon
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
63k GitHub starsUsed in 4 repos~898 tokens
Backend & APIsAuto-check passed
Nestjs Best Practices
rolling-scopes/rsschool-app
NestJS best practices and architecture patterns for building production-ready applications.
10k GitHub starsUsed in 6 repos~1.2k tokens
Backend & APIsAuto-check passed
Sub2API Admin
Wei-Shaw/sub2api
Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.
44k GitHub starsUsed in 1 repo~717 tokens
Backend & APIsAuto-check passed
Firecrawl Build Onboarding
firecrawl/firecrawl
Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.
190k GitHub starsUsed in 1 repo~1.4k tokens
Backend & APIsAuto-check: notes
Obsidian Bases
Atmosphere/atmosphere
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.
3.8k GitHub starsUsed in 22 repos~3.2k tokens
Backend & APIsAuto-check passed
Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
63k GitHub starsUsed in 4 repos~1.9k tokens
Backend & APIsAuto-check passed

Questions about Octo Messaging

What does Octo Messaging do?

Messaging domain — send/edit/sync messages, read receipts, message search (search/all/files/media/around/groups, in-channel or cross-channel), groups and threads (User Bot), and event polling. Octo Messaging is an agent skill from Mininglamp-OSS/octo-cli. Messaging domain — send/edit/sync messages, read receipts, message search (search/all/files/media/around/groups, in-channel or cross-channel), groups and threads (User Bot), and event polling.

When should I use Octo Messaging?

Octo Messaging fits situations like: backend & APIs work in your project.

How do I install Octo Messaging in Claude Code?

Run `npx skills add Mininglamp-OSS/octo-cli --skill octo-messaging -a claude-code`. Or copy the skill folder (skills/octo-messaging in Mininglamp-OSS/octo-cli) into .claude/skills/octo-messaging in your project. Claude Code loads it when a task matches its description.

How do I install Octo Messaging in Codex?

Run `npx skills add Mininglamp-OSS/octo-cli --skill octo-messaging -a codex`. Or copy the skill folder (skills/octo-messaging in Mininglamp-OSS/octo-cli) into .agents/skills/octo-messaging in your project. Codex loads it when a task matches its description.

Can I use Octo Messaging 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 Mininglamp-OSS/octo-cli --skill octo-messaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/octo-messaging, .gemini/skills/octo-messaging, .github/skills/octo-messaging and .opencode/skills/octo-messaging in your project.

What does Octo Messaging need to run?

Going by SKILL.md and its folder, Octo Messaging needs the command-line tools its instructions call (jq).

Does Octo Messaging 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 Octo Messaging 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 Octo Messaging use?

Octo Messaging 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 Octo Messaging use?

About 2.9k tokens (SKILL.md is roughly 12k 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 Octo Messaging?

Skills that share tags, products or a category with Octo Messaging: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 44k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Octo Messaging?

Mininglamp-OSS (a GitHub organization) maintains it in Mininglamp-OSS/octo-cli, which has 918 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 10, 2026.

Source: Mininglamp-OSS/octo-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Octo Messaging

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

octo-messaging — messages, groups, threads, events

1. message — 4 core commands (+ 6 search subcommands, see below)

channel-type values

App Bot restrictions (enforced server-side)

payload shape

message search — 6 subcommands

--chat-id decides in-channel vs cross-channel

Token subjects

Filters and pagination

2. group — 9 commands (both 5 / User Bot only 4)

3. thread — 8 commands, User Bot only

4. event — polling for inbound events

Important: event list is a POST

Standard poll loop

5. Error recovery cheatsheet

6. Schema lookup

Files

Compare with similar skills

Similar skills

More from Mininglamp-OSS/octo-cli

Related

Questions about Octo Messaging

1. `message` — 4 core commands (+ 6 search subcommands, see below)

`channel-type` values

`payload` shape

`--chat-id` decides in-channel vs cross-channel

2. `group` — 9 commands (both 5 / User Bot only 4)

3. `thread` — 8 commands, User Bot only

4. `event` — polling for inbound events

Important: `event list` is a POST