Executive OS
v0.0.1Build or operate a chief-of-staff style communications layer that merges multiple inboxes and chat sources into one prioritized digest with follow-up memory,...
⭐ 0· 65·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (merging inboxes into a prioritized digest) match the SKILL.md and its reference files. There are no unexpected environment variables, binaries, or installs requested that would be inconsistent with an inbox-triage/operating‑model assistant.
Instruction Scope
All runtime instructions are confined to reading the included reference files and producing prioritized digests, ledgers, and recommendations. The skill explicitly forbids sending messages or mutating external systems without explicit approval. One area to note: the references encourage supplementing signals with 'local notes and meeting docs' and tracking 'persistent memory' but do not specify storage locations or how local files would be accessed; that leaves some operational ambiguity about whether the agent will (or should be allowed to) open arbitrary local files or external mailboxes — the skill itself does not declare or require those accesses.
Install Mechanism
Instruction-only skill with no install spec and no code files to write or execute. This is the lowest-risk install posture.
Credentials
The skill requests no environment variables, credentials, or config paths. Its declared requirements are proportionate to a triage/prioritization assistant.
Persistence & Privilege
The skill describes a 'persistent memory' ledger conceptually, but provides no mechanism for storing that data and does not request persistent/system privileges. Confirm how (and where) follow-up/decision memory would be stored if you enable the skill; any external connectors or storage backends should require explicit user approval.
Assessment
This skill appears internally consistent: it provides policies, read-only triage rules, and an explicit 'do not send or mutate' safety boundary. Before installing, confirm (1) whether you will grant the agent access to any mailboxes, chat providers, or local files — those are not required by the skill package itself and should be consented to separately; (2) where 'persistent memory' would be stored if you enable it (and who can read it); and (3) that any connectors or drafts created in external systems require explicit approval. If you plan to let the agent access inboxes or persistent stores, review those connector permissions and the action-gate workflow to ensure the agent cannot send messages or change state without your explicit authorization.Like a lobster shell, security has layers — review code before you run it.
latestvk973fpmkp4030vm2taxvj7efr184bs12
License
MIT-0
Free to use, modify, and redistribute. No attribution required.