pm-inbox
Skill0 starsChanged 33 days agoMITView on GitHub
Sorts whatever has been dumped into inbox/ into the right folders of the base. Use when the user says "process the inbox", "sort my files", "I copied my downloads in", "разбери inbox", "разбери папку", "я скинул сюда файлы", or runs /pm-inbox.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read every file in inbox/, including subfolders.
- Distinctive: line 33
Don't open images either, even though you can.
- Distinctive: line 48
Only what was agreed, and only after the answer.
- Distinctive: line 64
When a file looks like that, it falls under "not product material".
- Distinctive: line 72
Don't pick a side — a contradiction found at this moment is the most valuable thing in the batch.
- Very specific: line 74
Add every new file to index.md.
- Very specific: line 82
Never edit a file after it has landed in raw/.
- Distinctive: line 86
Don't empty the queue for the sake of emptying it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Process the inbox
inbox/ is a queue, not a store. Things land there unsorted and leave typed.
raw/ is the opposite: once a source is there it stays forever and is never
edited.
Most people come to this with years of material already on disk. They do not reorganise it — they copy it in and let the base absorb what matters.
Work in three passes. Never skip the second.
1. Scan
Read every file in inbox/, including subfolders. Do not write, move, rename
or delete anything in this pass.
For each file work out: what kind of thing it is, what date it belongs to, and whether it is product material at all.
Some files you cannot read — archives, installers, video, binaries. Don't guess at their contents from the filename.
Don't open images either, even though you can. A screenshot carries no provenance: you cannot tell what it shows, when it was taken or whether the numbers in it are still true, and twenty of them will eat the session for nothing. List them by filename and ask which ones matter.
2. Show the plan and wait
Show a table — file, what you think it is, where it would go, why — grouped by outcome, with counts. Then stop and wait for an answer.
The person may say "that one's not what you think" or "leave that alone". That is the point of the pass.
3. Execute
Only what was agreed, and only after the answer.
The four outcomes
| Outcome | What you do |
| Source — transcript, email, export, a document someone else wrote | Move it to raw/. Then write the document it supports: a note in calls/, a fact in context/, a decision in decisions/. The new document cites the file in raw/. |
| Derived — something you can summarise but whose original is not worth keeping | Write the document in the right folder, cite where it came from, move the original to raw/ anyway if it is the only evidence. |
| Unclear | Leave it in inbox/ and ask one specific question about it. Never invent a type to empty the queue. |
| Not product material | Leave it exactly where it is. Say that you left it and why, in one line. Do not open it, do not copy it, do not describe its contents. |
Personal material
People's folders contain their private life. Bank statements, tickets, passports, photos, medical documents, contracts that are not yours to read.
When a file looks like that, it falls under "not product material". Name it by filename only — never by content — and move on. If you are unsure whether something is private, treat it as private and ask.
After the queue
- Compare what you just wrote against each other and against the base. Where
two documents disagree, say so, show both and mark the claim
[verify]. Don't pick a side — a contradiction found at this moment is the most valuable thing in the batch. - Add every new file to
index.md. - Report: how many files, split by outcome; what is still in
inbox/and what you need to know about it; which contradictions you found.
Rules
- Nothing is deleted. Ever. Files move inside the base or stay where they are.
- Nothing leaves the base. You do not publish, send or upload anything.
- Never edit a file after it has landed in
raw/. - A document with no
sourceis a defect. Write the link or don't write the document. - Everything you write is
status: draft. - Don't empty the queue for the sake of emptying it. Three files understood are worth more than thirty files filed wrongly.
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.