Projects
v1.0.0Build a personal project management system that scales from simple lists to structured planning.
⭐ 4· 1.7k·10 current·10 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the runtime instructions: creating project folders, README/tasks/notes files, templates, and review prompts are exactly what a personal 'Projects' helper would need. The skill does not request unrelated binaries, credentials, or system access.
Instruction Scope
Instructions direct the agent to create and read files under ~/projects/ and to ask users project-scoping questions — this is within scope. The doc mentions integrations (Calendar, Contacts, Invoices) but does not supply or require credentials or concrete API hooks; if the agent later asks for calendar/contacts access or credentials, those should be treated as separate consent points. The fixed workspace path (~/projects/) means the skill will create files in the user's home directory; users should be aware of potential overwrites or sensitive content being stored there.
Install Mechanism
No install spec and no code files — instruction-only — so nothing is downloaded or written to disk by the installer. This is low-risk from an installation perspective.
Credentials
The skill requires no environment variables, credentials, or config paths. That aligns with an offline/local project-organizing helper.
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform privileges. It will create files in a user workspace but does not modify other skills or system-wide settings.
Assessment
This skill appears internally consistent, but before installing consider: (1) it will create and manage files under ~/projects/ — back up any existing folder with that name to avoid overwriting; (2) project files may contain sensitive client/contact/invoice data — store only what you want on disk and consider encryption or a private directory; (3) although the skill mentions integrating with calendar/contacts/invoices, it doesn't include connectors or request credentials — do not supply credentials unless you trust a subsequent, explicit prompt and know where they'll be used; (4) review templates and any created README/tasks.md before sharing their contents; (5) if you do not want the agent to autonomously create files, adjust agent invocation settings or run the skill only on demand. Overall the skill is coherent for personal project organization and doesn't request unexpected access.Like a lobster shell, security has layers — review code before you run it.
latestvk97d1j3xn0bt6js2tz0thwwezs80xtev
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📁 Clawdis
OSLinux · macOS · Windows