Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
Inbox
Master any inbox with triage frameworks, cognitive load reduction, and multi-channel prioritization.
skill openclawclawhub Free
Master any inbox with triage frameworks, cognitive load reduction, and multi-channel prioritization.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, channels.md, cognitive.md, responses.md, triage.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
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
TopicFileTriage & prioritizationtriage.mdResponse workflowsresponses.mdMulti-channel orchestrationchannels.mdCognitive load reductioncognitive.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
1. Triage Before Presenting
Never show raw chronological dump. Classify first: BucketActionRequires decisionSurface immediatelyRequires awarenessDaily digestCan be delegatedRoute with contextNoiseAuto-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: StateOffer"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
TypeWhenAutomationPre-approved templateFAQ, link requestsSuggest ready-to-sendDraft for approvalRoutine, personalizedOne-click approve/editHolding responseCan't respond fully"Received, will review by X"Full composeComplex/sensitiveUser 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.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
5 Docs
- SKILL.md
- channels.md
- cognitive.md
- responses.md
- triage.md