Garden Inbox
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
OPS on-demand: This skill should be used when the user asks to "check inbox", "inbox zero"…
Install Ops Inbox
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-inbox --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-ops/skills/ops-inbox .claude/skills/ops-inbox && rm -rf skills-srcUse ~/.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/
Install the "ops-inbox" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-inbox into .claude/skills/ops-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-inbox", 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 install https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-inboxType 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.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-inbox --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-ops/skills/ops-inbox .agents/skills/ops-inbox && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ops-inbox" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-inbox into .agents/skills/ops-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-inbox", 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.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-inbox --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-ops/skills/ops-inbox .cursor/skills/ops-inbox && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ops-inbox" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-inbox into .cursor/skills/ops-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-inbox", 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 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git --path claude-ops/skills/ops-inbox--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-inbox --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-ops/skills/ops-inbox .gemini/skills/ops-inbox && rm -rf skills-srcUse ~/.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/
Install the "ops-inbox" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-inbox into .gemini/skills/ops-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-inbox", 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.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-inboxInstalls 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).
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-ops/skills/ops-inbox .github/skills/ops-inbox && rm -rf skills-srcUse ~/.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/
Install the "ops-inbox" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-inbox into .github/skills/ops-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-inbox", 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.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-inbox --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-ops/skills/ops-inbox .opencode/skills/ops-inbox && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ops-inbox" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-inbox into .opencode/skills/ops-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-inbox", 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
ops-inbox- GitHub stars
- 542
- Token cost
- ~2.1k tokens
- SKILL.md length
- 851 words
- Files
- 6 (incl. references)
- Skills in repo
- 67
- Repo updated
- First seen
- Licence
- MIT
At a glance
OPS on-demand: This skill should be used when the user asks to "check inbox", "inbox zero"…
- Works in 8 steps: Check existing ownership and reusable… → Use an existing fresh report or the… → Run independent read-only source/thread… → …
- Asks to check inbox
- SKILL.md covers AUTO-START DRAFTING: validate…, Coverage is not unread state, What the owner sees and Finish honestly, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ops Inbox is an agent skill from Lifecycle-Innovations-Limited/claude-ops. OPS on-demand: This skill should be used when the user asks to "check inbox", "inbox zero"…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `CHANNELS.md`, `references/cli.md` and `references/details.md`).
It sits in Productivity & Automation, covering Email management. The repository describes itself as: Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue… The licence is MIT.
When your agent uses it
- Asks to check inbox
- Tasks that involve Email management
Example prompts
- “check inbox”
- “inbox zero”
- “/ops-inbox”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpdate, TaskList, CronList, mcp__gog__gmail_search, mcp__gog__gmail_read_thread, mcp__gog__gmail_labels, mcp__claude_ai_Slack__slack_search_public_and_private, mcp__claude_ai_Slack__slack_read_channel, mcp__claude_ai_Slack__slack_list_channels, mcp__claude_ai_Slack__channels_list, mcp__claude_ai_Notion__notion-search, mcp__claude_ai_Notion__notion-fetch, mcp__claude_ai_Notion__notion-query-data-sources, mcp__claude_ai_Notion__notion-get-comments, mcp__claude_ai_Notion__notion-create-comment, mcp__claude_ai_Notion__notion-update-page, mcp__claude_ai_Notion__notion-create-pages, mcp__whatsapp__list_chats, mcp__whatsapp__list_messages, mcp__whatsapp__search_contacts, mcp__whatsapp__get_chat, mcp__whatsapp__get_message_context, mcp__whatsapp__archive_chat, mcp__whatsapp__resync_app_state, mcp__plugin_imessage_imessage__chat_messages
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Check existing ownership and reusable evidence before launching readers.
- Use an existing fresh report or the authorized read-only scan path. The bundled
- Run independent read-only source/thread readers in parallel, within the
- Validate full person/topic context per candidate, including sent history
- Surface the first validated draft immediately. Do not wait for unrelated
- One draft → one explicit approval → one send. Use the installed approved
- After sent=false, show the gate-returned full draft and end that presentation
- In the interactive authorized phase, complete answered/resolved items by
What it can do on your machine
Read from SKILL.md and the folder at commit ee9c784. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGrepGlobSkillAgentAskUserQuestionTeamCreateSendMessageTaskCreate
…and 25 more on the same allowed-tools line.
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
Ops Inbox loads about 2.1k tokens when it runs, and up to ~9.5k if it reads all its reference files. Until then it costs about 25 tokens; SKILL.md has 851 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpda
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 Lifecycle-Innovations-Limited/claude-ops at commit ee9c784, republished under its MIT licence (© Lifecycle-Innovations-Limited). 851 words, ~2,086 tokens.
Download SKILL.mdSave it as
.claude/skills/ops-inbox/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- ops-inbox
- description
- OPS on-demand: This skill should be used when the user asks to "check inbox", "inbox zero"…
- allowed-tools
- Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpdate, TaskList, CronList, mcp__gog__gmail_search, mcp__gog__gmail_read_thread, mcp__gog__gmail_labels, mcp__claude_ai_Slack__slack_search_public_and_private, mcp__claude_ai_Slack__slack_read_channel, mcp__claude_ai_Slack__slack_list_channels, mcp__claude_ai_Slack__channels_list, mcp__claude_ai_Notion__notion-search, mcp__claude_ai_Notion__notion-fetch, mcp__claude_ai_Notion__notion-query-data-sources, mcp__claude_ai_Notion__notion-get-comments, mcp__claude_ai_Notion__notion-create-comment, mcp__claude_ai_Notion__notion-update-page, mcp__claude_ai_Notion__notion-create-pages, mcp__whatsapp__list_chats, mcp__whatsapp__list_messages, mcp__whatsapp__search_contacts, mcp__whatsapp__get_chat, mcp__whatsapp__get_message_context, mcp__whatsapp__archive_chat, mcp__whatsapp__resync_app_state, mcp__plugin_imessage_imessage__chat_messages
- argument-hint
- [channel: whatsapp|imessage|email|slack|telegram|discord|notion|all]
- effort
- high
- maxTurns
- 60
OPS ► INBOX
Load ops-rules before acting. Public repo: no personal data. Run in the parent
session: readers return evidence; the parent owns draft presentation and sends.
AUTO-START DRAFTING: validate per reply
Always report to the main agent by default. Never set context: fork for this
skill: the parent owns the visible queue. Do not wait for "continue drafting".
The invocation starts the selected channels (default: all configured channels).
No continuation menu, channel picker, or second "start drafting" prompt.
- Check existing ownership and reusable evidence before launching readers. Enumerate accounts/workspaces once; record each source's actual read status.
- Use an existing fresh report or the authorized read-only scan path. The bundled
scanner is a candidate pre-filter, not proof that a request is unanswered.
Do not run a second overlapping whole-inbox sweep. See
references/runtime.md. - Run independent read-only source/thread readers in parallel, within the executing machine's concurrency limit. Keep the quickest useful candidate in the parent; do not leave the parent waiting for an aggregate report.
- Validate full person/topic context per candidate, including sent history
on every configured account. See
references/details.md. A KEEP row alone is not a ready draft. Missing load-bearing context stays unknown. - Surface the first validated draft immediately. Do not wait for unrelated sources or the rest of the inbox. Recheck its live thread before showing it. Every later ready candidate joins the parent's queue as evidence arrives.
- One draft → one explicit approval → one send. Use the installed approved outbound gate; email, WhatsApp and Slack go only through the host's approved outbound gate. Populate its real session/thread/recipient metadata on the first call. Go is not approval. No self-created approval proof or alternate send route.
- After sent=false, show the gate-returned full draft and end that presentation turn. Only the next native user event can advance its decision and the next draft. A transport hold may retain separately approved records for later gate-only drain; never show another draft in the same wait turn. Different threads/intents stay separate; unsupported queue states are not ready.
- In the interactive authorized phase, complete answered/resolved items by verifying then archiving Gmail and every owned WhatsApp JID on its account. No extra menu for the expressly authorized completed set; protect open tasks, labels and unknown media. Mark-read is separate. Cron scans remain read-only.
Readers never send, archive, mark-read, modify integrations, or ask the owner
questions. They send evidence packets to the parent as soon as ready; an idle
worker without a report is not completion. See references/fan-out.md.
Coverage is not unread state
- Email: every mailbox, including sent history, All Mail and discovered action/follow-up labels. Inbox, read/unread, archived, categories and drafts are not evidence that an ask was handled.
- WhatsApp: every connected WhatsApp account, labelled separately. Connected but agent-disabled accounts stay explicit not-checked gaps; do not enable or access them. Derive coverage from complete discovery, not a fixed count. Prove phone/JID/LID identity before merging aliases; reconcile incoming and outgoing across authorized accounts. A generic MCP name does not prove coverage.
- Slack: every Slack workspace, scoped human DMs/group DMs (
im,mpim), allowedpublic_channelandprivate_channelhistory, mentions and replies. Read-state is not the filter; inspect thread replies, not just channel tails. - Other configured sources: allowlisted iMessage/SMS, user-auth Telegram, scoped Discord, Notion comments/tasks, contact memory and open commitments.
- Dates/availability: every configured calendar plus the show/travel source of truth for the candidate's relevant dates. Never infer timezone from a number.
Paginate and disclose the lookback and retention limits. Record not checked, partial, failed, or not configured explicitly; unknown is never a clean zero. Older known open asks stay in the queue even outside the scan window.
Show full SKILL.md (251 more words)Show less
What the owner sees
One compact context block: who, the two-sentence thread arc, the actual latest ask, why this answer helps, and any source gap. Then the gate shows the exact recipient/account/thread, reply-all recipients, subject, full body and attachments. The gate's latest delivered full-draft proof binds approval to those bytes.
After a native, proven yes to that shown draft, send when the gate permits without a second approval menu. A typed yes followed by a refused/cancelled physical gate is not approval. On failure keep the intent and exact diagnostic owned. Continue independent read-only research, but advance another presentation only after the next native user event. Never claim "sent" from a preview or pending-proof record.
Finish honestly
Recheck source changes since each reader's cutoff before claiming complete. Account for queued, shown, approved, sent, skipped, unresolved and unknown items. Inbox zero is always the goal: all configured sources have completed dispositions, no unhandled obligations, and authorized resolved items are verified archived. Unknown coverage, pending proof or archive failure means NOT zero, regardless of unread count. A real approval wait is not completion; preserve the queue for the next user event. Status heartbeats follow the host's cadence, contain actual results, and stop at a final result or real wait.
References (load only the relevant one)
references/details.md— per-candidate context, preflight, approval and verificationreferences/runtime.md— ownership, account discovery, freshness and source gapsreferences/fan-out.md— progressive read-only workers and evidence packetreferences/cli.md— supported read paths and authorized archive verificationvip,relations— priority, verified contact identity and open commitments
© Lifecycle-Innovations-Limited, MIT. 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 5 other files (references) in claude-ops/skills/ops-inbox of Lifecycle-Innovations-Limited/claude-ops.
- SKILL.md
- CHANNELS.md
- references/cli.md
- references/details.md
- references/fan-out.md
- references/runtime.md
Open the folder on GitHubat commit ee9c784
Compare with similar skills
Ops Inbox 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ops Inbox this skillLifecycle-Innovations-Limited/claude-ops | 542 | — | ~2.1k | Automated safety check: Notes | MIT | |
| Garden Inboxpaperclipai/paperclip | 99k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Continuetelegramdesktop/tdesktop | 33k | 2 repos | ~9.4k | Automated safety check: Pass | GPL-3.0 | |
| Process Inboxtelegramdesktop/tdesktop | 33k | 1 repos | ~5.4k | Automated safety check: Pass | GPL-3.0 | |
| Process InboxTDesktop-x64/tdesktop | 3k | — | ~4.3k | Automated safety check: Pass | GPL-3.0 | |
| Career-Ops Gmail Lead Plugincareer-ops-hq/career-ops | 74k | — | ~233 | Automated safety check: Notes | MIT |
Similar skills
Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
Process Inbox
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
Process Inbox
TDesktop-x64/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
Career-Ops Gmail Lead Plugin
career-ops-hq/career-ops
Pulls job leads from a Gmail label into the career-ops pipeline, extracting job URLs from DMARC-passing emails and de-duplicating against existing leads.
Atomicmail
Atomic-Mail/atomic-mail-agentic
Read and write email through the Atomic Mail from an AI agent.
More from Lifecycle-Innovations-Limited/claude-ops
All 67 skills in this repoOps Dash
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "ops dashboard", "pixel HQ", or…
Ops Gtm
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "go to market", "GTM plan", or…
Ops Marketing
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "klaviyo", "ads spend", or…
Ops Socials
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "tweet", "post to linkedin", or…
Ops Yolo
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "yolo mode", "run the business today"…
Ops Monitor
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "datadog", "APM alerts", or…
Related
Categories
Questions about Ops Inbox
What does Ops Inbox do?
OPS on-demand: This skill should be used when the user asks to "check inbox", "inbox zero"…. Ops Inbox is an agent skill from Lifecycle-Innovations-Limited/claude-ops.
When should I use Ops Inbox?
Ops Inbox fits situations like: asks to check inbox; tasks that involve Email management.
How do I install Ops Inbox in Claude Code?
Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a claude-code`. Or copy the skill folder (claude-ops/skills/ops-inbox in Lifecycle-Innovations-Limited/claude-ops) into .claude/skills/ops-inbox in your project. Claude Code loads it when a task matches its description.
How do I install Ops Inbox in Codex?
Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a codex`. Or copy the skill folder (claude-ops/skills/ops-inbox in Lifecycle-Innovations-Limited/claude-ops) into .agents/skills/ops-inbox in your project. Codex loads it when a task matches its description.
Can I use Ops Inbox 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 Lifecycle-Innovations-Limited/claude-ops --skill ops-inbox -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ops-inbox, .gemini/skills/ops-inbox, .github/skills/ops-inbox and .opencode/skills/ops-inbox in your project.
What does Ops Inbox need to run?
SKILL.md names no scripts, command-line tools or credentials: Ops Inbox is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpdate, TaskList, CronList, mcp__gog__gmail_search, mcp__gog__gmail_read_thread, mcp__gog__gmail_labels, mcp__claude_ai_Slack__slack_search_public_and_private, mcp__claude_ai_Slack__slack_read_channel, mcp__claude_ai_Slack__slack_list_channels, mcp__claude_ai_Slack__channels_list, mcp__claude_ai_Notion__notion-search, mcp__claude_ai_Notion__notion-fetch, mcp__claude_ai_Notion__notion-query-data-sources, mcp__claude_ai_Notion__notion-get-comments, mcp__claude_ai_Notion__notion-create-comment, mcp__claude_ai_Notion__notion-update-page, mcp__claude_ai_Notion__notion-create-pages, mcp__whatsapp__list_chats, mcp__whatsapp__list_messages, mcp__whatsapp__search_contacts, mcp__whatsapp__get_chat, mcp__whatsapp__get_message_context, mcp__whatsapp__archive_chat, mcp__whatsapp__resync_app_state, mcp__plugin_imessage_imessage__chat_messages.
Does Ops Inbox 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 Ops Inbox safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Ops Inbox use?
Ops Inbox is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ops Inbox use?
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.4k tokens, read only when the agent opens those files.
What are the alternatives to Ops Inbox?
Skills that share tags, products or a category with Ops Inbox: Garden Inbox (paperclipai/paperclip, 99k stars), Continue (telegramdesktop/tdesktop, 33k stars), Process Inbox (telegramdesktop/tdesktop, 33k stars) and Process Inbox (TDesktop-x64/tdesktop, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ops Inbox?
Lifecycle-Innovations-Limited (a GitHub organization) maintains it in Lifecycle-Innovations-Limited/claude-ops, which has 542 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 10, 2026.
Source: Lifecycle-Innovations-Limited/claude-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.