vaultage-inbox
Skill2 starsChanged 10 months agoMITView on GitHub
Process and categorize items in the vault inbox using PARA method. Set your vault path via environment variable:
In this repository17 other files it gives its agents.
- react-best-practices/AGENTS.mdAGENTS.md
- agent-browserSkill
- claudeceptionSkill
- devlog-harvesterSkill
- humanizerSkill
- knowledge-forgeSkill
- loop-maestroSkill
- notebooklmSkill
- obsidian-bridgeSkill
- portfolio-forgeSkill
- project-analyzerSkill
- pr-review-resolverSkill
- vercel-react-best-practicesSkill
- vaultage-captureSkill
- vaultage-dailySkill
- vaultage-searchSkill
- web-design-guidelinesSkill
The file
Files
Vaultage Inbox Processor Skill
Process and categorize items in the vault inbox using PARA method.
Configuration
Set your vault path via environment variable:
export VAULTAGE_PATH="$HOME/Documents/Vaultage" # Customize to your vault locationTrigger Phrases
- "process inbox"
- "categorize inbox"
- "organize vault inbox"
Process
- Scan inbox:
ls -la "$VAULTAGE_PATH/00_Inbox/"- For each item, analyze content and suggest destination:
- 01_Projects: Has deadline, specific outcome, requires multiple steps
- 02_Areas: Ongoing responsibility, no end date, maintenance
- 03_Resources: Reference material, might need later, learning
- 04_Archive: Completed, no longer relevant, historical
- Move files with user confirmation:
mv "$VAULTAGE_PATH/00_Inbox/note.md" "$VAULTAGE_PATH/01_Projects/"Decision Framework
| Signal | Destination |
| Has due date | 01_Projects |
| "I need to..." | 01_Projects |
| Recurring topic | 02_Areas |
| "How to..." | 03_Resources |
| Historical reference | 04_Archive |
| Completed task | 04_Archive |
Inbox Health
Target: < 20 items in inbox at any time
PARA Structure
- 00_Inbox: Unprocessed items
- 01_Projects: Active projects with deadlines
- 02_Areas: Ongoing responsibilities
- 03_Resources: Reference materials
- 04_Archive: Completed/inactive items
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.