Personal Os Framework
v0.3.0Build a second brain that AI can understand and maintain. This framework provides decision logging with follow-up tracking, periodic review generation, routi...
⭐ 0· 100·0 current·0 all-time
bywuu Dao@daowuu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the skill's runtime guidance is limited to building and maintaining a 'personal-os' (STATE.md, TODO.md, DECISIONS.md, Inbox/Knowledge/, etc.). There are no unrelated requirements (no cloud creds, no binaries, no external services).
Instruction Scope
The SKILL.md explicitly tells an AI collaborator to read and update local workspace files after conversations, generate periodic reviews, and perform routing/distillation. This stays within the claimed domain, but the guidance to 'not wait for commands' and to act proactively grants broad discretionary behavior to an agent (within the personal-os file set). There are no instructions to access unrelated system paths or external endpoints.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written by an installer. Lowest install risk.
Credentials
The skill requests no environment variables, credentials, or config paths. All required inputs are local markdown files, which is proportional to the stated functionality.
Persistence & Privilege
The skill does not set always:true and has no installer, but its content recommends autonomous, periodic behavior (cron jobs optional) and encourages the AI to act proactively. Autonomous invocation is the platform default; combined with the proactive guidance this increases the chance the agent will read/write the workspace frequently — this is consistent with purpose but worth noting from a policy/operational perspective.
Assessment
This skill is internally coherent and does what it says: it asks an AI collaborator to read and update files in a workspace to implement a 'personal OS'. Before installing or enabling autonomous use, consider: 1) Only point the skill at a directory you control and that does not contain secrets or sensitive credentials (the skill will read/write markdown files). 2) Decide whether you want the agent to act proactively — if not, restrict autonomous invocation or require manual triggers. 3) Monitor the files the agent writes (HEARTBEAT-LOG.md, reviews) and keep backups. 4) If you plan to run periodic jobs (cron), ensure they run with minimal privileges and under a controlled account. If you need more assurance, ask the skill author for explicit boundaries (exact file paths, a dry-run mode, and a clear list of files the skill will modify).Like a lobster shell, security has layers — review code before you run it.
latestvk97cgm2rpta92c6z0keyqcg92183mrvq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.