Productivity Operating System
v1.0.0Help design and optimize daily productivity systems focused on energy management, priority setting, time blocking, and flow state to boost output and prevent...
⭐ 1· 2.8k·32 current·37 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill name/description (Productivity Operating System) aligns with the SKILL.md and README: interview the user about energy patterns, produce time-block templates, and provide frameworks. There are no unexpected credential or binary requirements that would be inconsistent with a productivity coaching skill.
Instruction Scope
SKILL.md contains explicit interview questions, templates (YAML), and step-by-step frameworks for prioritization and scheduling. It does not instruct the agent to read system files, environment variables, or reach out to external endpoints. It is user-interview centric and not overly open-ended.
Install Mechanism
No install spec or code files; instruction-only. Nothing will be downloaded or written to disk by the skill itself, minimizing installation risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. The content does not ask for secrets or unrelated service tokens; all requested user inputs are personal productivity details (wake time, energy drains, etc.).
Persistence & Privilege
always:false and no install actions. The skill can be invoked autonomously per platform default, but it does not request elevated privileges or modify other skills/config. Autonomous invocation is allowed by platform default and is not combined here with broad credential access.
Assessment
This skill is instruction-only and internally consistent with its stated purpose, so technical risk is low. Before installing or enabling autonomous use: (1) Confirm you trust the publisher — the registry entry has no homepage and a cryptic owner ID. (2) Be cautious about sharing sensitive or identifying information in the interview prompts (it asks for personal habits and schedules, not credentials). (3) Review your agent's platform permissions — the skill itself doesn’t make network calls, but your agent or other enabled tools might; if you do not want automated outbound communication, disable autonomous invocation or restrict the agent's tool access. (4) If you plan to follow paid links or download context packs referenced in the README, verify those external sites independently. If you want extra caution, run the skill only interactively (user-invoked) rather than allowing background/autonomous runs.Like a lobster shell, security has layers — review code before you run it.
latestvk97bmm965z9m0rpe6rc04rbxqd81fpxk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.