PARA

Organize files and projects using the PARA method (Projects, Areas, Resources, Archives).

Security Scan

The skill's description matches its behavior (reorganizing files into a PARA folder layout), but its runtime instructions are overly broad and mandatory and could move or overwrite workspace files without safeguards.

Purpose & Capability

The skill claims to organize files with the PARA method and its instructions do exactly that (create/move files into /root/clawd/1-Projects, 2-Areas, etc.). Requiring file moves is proportionate to the stated purpose. However, the SKILL.md hardcodes an absolute path (/root/clawd/) that is not listed in the skill's declared config paths, so there is a mismatch between declared metadata and actual target scope.

Instruction Scope

The instructions mandate: 'You MUST follow the PARA structure for ALL file operations' and explicitly direct the agent to use mv for file organization. They lack safeguards (no dry-run, confirmations, exclusions, backups, or permission checks) and reference agent identity files (AGENTS.md, MEMORY.md) only as exceptions without a precise rule set. That gives the agent broad discretion to move arbitrary files under /root/clawd, which could cause unexpected data loss or break other components that expect files in fixed locations.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. Nothing is written to disk by an installer, which is the lowest-risk install profile.

Credentials

The skill requests no environment variables, credentials, or config paths. The lack of requested secrets is proportionate to the stated purpose.

Persistence & Privilege

always is false (good), but model invocation is allowed (default). Combined with the SKILL.md's mandatory rule to reorganize 'ALL file operations', autonomous invocation could allow the agent to perform destructive or disruptive file moves without explicit user approval. The skill also does not declare any scoped config paths, yet it assumes ownership of /root/clawd/.

What to consider before installing

This skill does what it says (reorganizes files into a PARA layout) but its instructions are forceful and have no safety checks — it could move or overwrite important files under /root/clawd without asking. Before installing or enabling it: (1) make a full backup of /root/clawd and test the skill on a copy, (2) ask the author to add safe behaviors (dry-run mode, confirmation prompts, explicit exclude lists for AGENTS.md/MEMORY.md and other critical files, and a way to opt into automatic moves), (3) prefer running it only via explicit user invocation (disable autonomous runs if your platform allows), and (4) request that the skill declare /root/clawd as an explicit config path in its metadata so its scope is transparent. If you cannot verify these changes, treat the skill as risky for production or agent-critical workspaces.

PARA Organization Skill

Use the PARA method to keep the workspace clean and organized.

Structure

• /root/clawd/1-Projects/: Active efforts with a deadline/goal.
• /root/clawd/2-Areas/: Ongoing responsibilities (e.g., Finances, Health, Personal Development).
• /root/clawd/3-Resources/: Interests and reference material.
• /root/clawd/4-Archives/: Completed projects or inactive areas/resources.

Mandate: Automatic Organization

You MUST follow the PARA structure for ALL file operations. Never leave new files in the root directory (/root/clawd/) unless they are core identity files (AGENTS.md, MEMORY.md, etc.).

1. New Project Files? Create a subfolder in 1-Projects/.
2. Long-term reference or data? Put it in 3-Resources/.
3. Finished work? Move it to 4-Archives/.
4. System/Config updates? Keep them in 2-Areas/.

Workflow

1. Identify: Determine which category a file or directory belongs to.
2. Move: Use mv to place it in the correct PARA folder.
3. Maintain: Periodically review Projects and move finished ones to Archives.

Categorization Guide

• Projects: Bot development, Specific homework assignments, Reports being written.
• Areas: Financial logs (MIANJY), Email configurations, Skill development.
• Resources: Research papers, Diagrams for learning, Snippets.
• Archives: Old reports, Finished semester files.