2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill organizer- _meta.json272 B
- skill.md8.5 KB
Overview
This skill designs clear, usable organization systems that turn scattered notes, tasks, files, and ideas into structures people can act on. It focuses on choosing a single organizing logic, creating intuitive containers and labels, and separating active work from reference and archive. The goal is faster findability, clearer next actions, and low maintenance over time.
How this skill works
I start by defining exactly what is being organized and what decisions the structure must support (findability, execution, review, handoff). Then I pick one primary organizing logic (by project, topic, workflow stage, client, or time horizon) and propose a folder/section architecture, naming rules, status labels, and archive rules. Finally I provide a practical maintenance plan and the immediate next steps to apply the system.
When to use it
- You have messy notes, files, or tasks and need a repeatable structure.
- You want a simple folder/board layout that speeds up action and review.
- You need rules to separate active items from reference and archive.
- You’re starting a new project or scaling an existing workflow.
- You need naming and labeling conventions for team handoffs.
Best practices
- Define the object and purpose before creating folders or labels.
- Choose one primary organizing principle and keep containers broad initially.
- Use plain-language labels that still make sense months later.
- Separate active, reference, and archive states — archive aggressively.
- Schedule a short regular maintenance checkpoint (weekly or monthly).
Example use cases
- Convert a pile of research notes into topic folders, summary notes, and a reference archive.
- Design a project board with columns: Backlog, Next Action, In Progress, Blocked, Done, Archive.
- Create a file hierarchy with client → project → deliverable and a naming rule including date and version.
- Clean up a task list by grouping by priority and defining next-action labels.
- Set up an operations folder structure with SOPs, templates, current work, and archived cycles.
FAQ
Start with 3–7 broad buckets. Too many top-level categories create maintenance drag; refine only when a bucket becomes unwieldy.
What’s the quickest way to reduce clutter now?
Move anything not needed for immediate action into a reference or archive folder, then create simple labels for items that need follow-up.