← Back to Skills Marketplace
595
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install inbox
Description
Master any inbox with triage frameworks, cognitive load reduction, and multi-channel prioritization.
README (SKILL.md)
When to Use
User needs help managing incoming streams across email, chat, social, and project tools. Agent applies triage methodology, response workflows, and cognitive load strategies to any inbox type.
Quick Reference
| Topic | File |
|---|---|
| Triage & prioritization | triage.md |
| Response workflows | responses.md |
| Multi-channel orchestration | channels.md |
| Cognitive load reduction | cognitive.md |
Scope
This skill provides methodology and decision frameworks. It does NOT integrate with specific services.
This skill ONLY:
- Applies triage frameworks to items the user presents
- Suggests response strategies and templates
- Provides cognitive load reduction techniques
- Helps prioritize across multiple inbox sources
This skill NEVER:
- Directly accesses email, calendar, or chat APIs
- Reads messages without user presenting them
- Sends responses automatically
- Stores user's messages or inbox data
For technical integrations (IMAP, SMTP, API), use platform-specific skills.
What "Inbox" Means
Not just email. Any incoming stream requiring attention:
- Email (multiple accounts)
- Chat platforms (Slack, Discord, Teams, WhatsApp)
- Social DMs (Twitter, LinkedIn, Instagram)
- Project tools (GitHub, Jira, Asana, Notion)
- Calendar invites
- Voice messages and audio notes
- Saved articles, "read later" queues
Core Rules
1. Triage Before Presenting
Never show raw chronological dump. Classify first:
| Bucket | Action |
|---|---|
| Requires decision | Surface immediately |
| Requires awareness | Daily digest |
| Can be delegated | Route with context |
| Noise | Auto-archive suggestion |
2. Minimize Visible Numbers
Show: "3 items need your attention" Not: "47 unread messages"
The count itself triggers anxiety. Surface actionable items only.
3. Batch Similar Items
Group by type, project, or sender. "Here are 7 intro requests" beats 7 separate interruptions. Reduces context switching.
4. Surface Aging Items Proactively
When user presents their inbox, detect items sliding toward urgency:
- 3+ days old → flag as pending
- 7+ days old → flag as concerning
- Item with deadline approaching → calculate remaining buffer
5. Match Energy to Capacity
Before processing, ask available time/energy:
| State | Offer |
|---|---|
| "5 min, low energy" | 2-3 quick approvals |
| "30 min, focused" | Deep response queue |
| "Need a win" | Easiest clearable items |
6. Detect Avoidance Patterns
When same item mentioned as snoozed/skipped 3+ times:
- Acknowledge: "You've been avoiding this one"
- Break down: "Can we handle just one part?"
- Lower bar: "Just send a holding response?"
7. Response Type Selection
| Type | When | Automation |
|---|---|---|
| Pre-approved template | FAQ, link requests | Suggest ready-to-send |
| Draft for approval | Routine, personalized | One-click approve/edit |
| Holding response | Can't respond fully | "Received, will review by X" |
| Full compose | Complex/sensitive | User writes |
Common Traps
- Showing all unread → overwhelms user, causes avoidance. Triage first.
- Ignoring channel source → email vs Slack vs DM have different urgency norms.
- Treating snooze as archive → snoozed items MUST return. Track and resurface.
- Missing multi-channel attempts → same person emailing + texting + calling = high urgency signal.
- Forgetting "read later" → saved items decay into guilt. Resurface one per day.
Usage Guidance
This skill appears to be a methodology/reference pack (low inherent risk) but its files contain conflicting guidance about automation and data access. Before installing or enabling it for autonomous use, ask the publisher to clarify: (1) Will the skill ever perform automated sends, nudges, or archives, or is it strictly advisory? (2) What integrations (calendar, address book, transcription) does it require, and will it request explicit permission before accessing them? If you plan to grant the agent access to calendars/contacts or enable automation, decide which actions should remain manual and require explicit approval. If you want only advisory behavior, restrict the agent from performing outbound actions or integration access in your platform settings.
Capability Analysis
Type: OpenClaw Skill
Name: inbox
Version: 1.0.0
The OpenClaw AgentSkills bundle 'inbox' is benign. All files (SKILL.md, channels.md, cognitive.md, responses.md, triage.md) contain only conceptual instructions for an AI agent on how to manage an inbox, focusing on prioritization, cognitive load reduction, and response strategies. SKILL.md explicitly states the skill 'NEVER' directly accesses APIs, reads messages without user presentation, sends responses automatically, or stores user data. There are no shell commands, network calls, file system access instructions, prompt injection attempts to subvert the agent, or any other indicators of malicious behavior or significant vulnerabilities.
Capability Assessment
Purpose & Capability
The skill's stated purpose—providing triage frameworks and response workflows without integrating with services—is plausible. However many guidance items implicitly assume access to calendars, address books, transcription, and outbound messaging (e.g., {my_availability}, conflict detection, transcribe immediately), which go beyond a pure methodology document if executed.
Instruction Scope
The SKILL.md and supporting files include automation-oriented instructions ("Pre-approved auto-send: Fully automated", "Auto-nudge after configurable interval", "Auto-archive rest", "transcribe immediately") and template variables that require calendar/address-book data. Yet the SKILL.md explicitly says the skill NEVER accesses email, calendar, or chat APIs and NEVER sends responses automatically. This is an internal contradiction: the skill's prose both prohibits and prescribes automated integrations and outbound actions.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing will be written to disk or installed by the skill itself.
Credentials
No env vars, binaries, or config paths are requested (which is coherent for an instruction-only skill). But the instructions assume access to external data sources (calendar, address book, transcripts), yet the skill declares it will not access such services—this gap means additional permissions could be requested at runtime by the agent or by companion skills, so users should confirm what data the agent will actually access.
Persistence & Privilege
The skill does not request persistent or elevated privileges (always is false). It does not attempt to modify other skills or system-wide configs in the provided materials.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install inbox - After installation, invoke the skill by name or use
/inbox - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is Inbox?
Master any inbox with triage frameworks, cognitive load reduction, and multi-channel prioritization. It is an AI Agent Skill for Claude Code / OpenClaw, with 595 downloads so far.
How do I install Inbox?
Run "/install inbox" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Inbox free?
Yes, Inbox is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Inbox support?
Inbox is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).
Who created Inbox?
It is built and maintained by Iván (@ivangdavila); the current version is v1.0.0.
More Skills