0
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 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 spm1001/trousse --skill filing- README.md1.3 KB
- SKILL.md18.8 KB
Overview
This skill orchestrates disciplined file cleanup by enforcing mandatory processing before any file is moved. It reads file content, extracts actions, waiting-fors, and calendar items, then places files into a PARA-aligned Work structure (Projects, Areas, Resources, Archive) plus Meeting Notes. The skill prevents lost follow-ups and buried tasks by making processing the gating step in weekly review filing.
How this skill works
The skill inspects nine common clutter zones (Downloads, iCloud downloads, Desktop, Work root, My Drive inbox, Temp, Work Inbox, JPR recordings, and iA Writer strays) and reports which zones contain items. For each file it opens and reads content, extracts concrete next actions, waiting-fors, and calendar dates, then suggests destination folders and standardized names. Meeting notes must pass a processing checklist before moving. Temporary staging folders are cleared or emptied after review.
When to use it
- During weekly review filing phase (mandatory)
- When you ask: 'where should this go?', 'help me tidy', 'clean up downloads', or 'triage inbox'
- Moving files between Projects, Areas, Resources, and Archive
- Processing meeting notes, voice transcripts, or quick captures before adding tasks
- Clearing transient Temp or My Drive inbox items after a work session
Best practices
- Always read a file before moving it — extracting actions and waiting-fors is mandatory
- Use the five-step per-file process: process, extract, rename if needed, choose destination, then move
- Keep Work root empty except for CLAUDE.md; use Temp only for transient session files
- Organize Projects as '{Area} - {Outcome statement}' and move completed projects to Archive
- Batch-process meeting notes with the Sublime Loop: extract to a temp file, review, then push actions to Todoist
Example use cases
- Weekly cleanup: scan all nine zones, extract actions from meeting notes, file items into Projects/Areas/Resources or Archive
- Triage Downloads: open each PDF/screenshot, determine project context, file to project folder or delete
- Process voice memos: transcribe JPR recordings, review transcript, extract actions, then archive audio
- Empty Temp folder after an analysis session, keeping only items that were processed and filed
- Resolve My Drive inbox: move new Google Docs into Meeting Notes/{year}/ or relevant Project folders
FAQ
Confirm by reading; if truly empty or irrelevant, delete with confirmation. Do not move unlabeled 'maybe' files into Archive.
How strict is the naming standard?
Rename meeting notes to '{date} {Person/Topic} - {Brief description}.md' and projects as '{Area} - {Outcome statement}' to preserve discoverability.