Inbox

v1.0.0

Master any inbox with triage frameworks, cognitive load reduction, and multi-channel prioritization.

0· 550·1 current·1 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
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.
What to consider before installing
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.

Like a lobster shell, security has layers — review code before you run it.

latestvk97dtznwf8d9km52q4bpvf2k3h81att3

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📥 Clawdis
OSLinux · macOS · Windows

Comments