inbox-process
Skill5 starsChanged 6 months agoApache-2.0View on GitHub
Process new files in inbox/: detect, flag to {{OWNER}}, process with approval, mark as done
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- db-healthSkill
- dreamSkill
- forum-pulseSkill
- genesisSkill
- grill-meSkill
- handoffSkill
- hireSkill
- kaizenSkill
- quality-gateSkill
- quarterly-reviewSkill
- session-endSkill
- session-startSkill
- sync-upstreamSkill
- twin-updateSkill
- voice-gateSkill
- weekly-reviewSkill
- write-a-skillSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Check what's already processed:
- Distinctive: line 34
Wait for {{OWNER}}'s decision on each file.
- Distinctive: line 41
Read the file content
- Distinctive: line 44
Search first, so you do not file a second copy of something already there:
- Distinctive: line 63
After processing each file:
- Distinctive: line 71
Never process without {{OWNER}}'s approval
- Very specific: line 72
Never delete files from inbox/
- Distinctive: line 73
Always mark processed files in the DB
- Very specific: line 74
If 3+ files are being indexed, trigger /dream after completion
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Inbox Processing
Step 1 -- Detect New Files
List inbox/ contents:
ls -la "inbox/"Check what's already processed:
PRAGMA foreign_keys = ON; PRAGMA journal_mode = WAL; PRAGMA busy_timeout = 5000;
SELECT filename FROM processed_inbox_files;Compare: any file in the directory NOT in the processed list is new.
Step 2 -- Flag to {{OWNER}}
For each unprocessed file, present to {{OWNER}} with options:
- Index in knowledge base -- extract content, pick a wing/room/hall, store via
palace.py add - Assign to team member -- delegate to a specialist for analysis/action
- File for reference -- mark as processed without further action
- Ignore -- skip this file
Wait for {{OWNER}}'s decision on each file.
Step 3 -- Process
Based on {{OWNER}}'s choice:
If indexing in knowledge base:
- Read the file content
- Pick the most specific wing, room and hall (see the taxonomy in CLAUDE.md) —
never dump into
archivebecause nothing else fit - Search first, so you do not file a second copy of something already there:
python3 scripts/palace.py search "<key phrase from the file>" --mode keyword- File it:
python3 scripts/palace.py add --wing <wing> --room <room> --hall <hall> --file "inbox/<filename>"If assigning to team member:
- Identify the right team member
- Delegate the task
- Log in activity_history
If filing for reference:
- Just mark as processed (Step 4)
Step 4 -- Mark as Processed (MANDATORY)
After processing each file:
INSERT INTO processed_inbox_files (filename, processed_at, notes)
VALUES (?, strftime('%Y-%m-%dT%H:%M:%SZ', 'now'), ?);Rules
- Never process without {{OWNER}}'s approval
- Never delete files from
inbox/ - Always mark processed files in the DB
- If 3+ files are being indexed, trigger
/dreamafter completion
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.

