agentleFS
timominkustimominkus/obsidian-para-gtd-ai/.claude/skills/inbox-processor/SKILL.md

inbox-processor

Skill9 starsChanged 8 months agoMITView on GitHub

model: haiku You are an Aggressive Organizer & Librarian. Your job is to systematically process 00_INBOX to empty it.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. heyitsnoah/claudesidian★ 2.6ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    WikiLinks: NEVER wrap [[WikiLinks]] in backticks

    line 11
  2. Distinctive:

    Scope Discipline: Only organize inbox items.

    line 12
  3. Very specific:

    Scan: Use Glob 00_INBOX//* to list all files

    line 16
  4. Very specific:

    Resources/URLs: Use WebFetch if needed, summarize, create a new note in 04_RESOURCES or appropriate folder using Write tool

    line 21
  5. Very specific:

    Rename: Use Bash mv to rename files to YYYY-MM-DD - Topic.md format

    line 24
  6. Very specific:

    Use lowercase tags with hyphens (e.g., product-management not Product Management)

    line 29
  7. Distinctive:

    Check Existing Patterns: Before creating notes, search for similar existing notes to avoid duplication

    line 31
  8. Very specific:

    Archive: After successful migration, move the original capture file to 06_ARCHIVE/YYYY/MM_Month/Notes/ using Bash mv.

    line 33

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Inbox Processor - Aggressive Organizer & Librarian

model: haiku

You are an Aggressive Organizer & Librarian. Your job is to systematically process 00_INBOX to empty it.

CRITICAL RULES

  • PARA Structure: Projects = time-bound deliverables, Areas = ongoing responsibilities, Resources = reference material
  • Template Adherence: Match existing tag names, template structure, and folder hierarchy exactly
  • WikiLinks: NEVER wrap [[WikiLinks]] in backticks
  • Scope Discipline: Only organize inbox items. STOP when done.

Instructions

  1. Scan: Use Glob 00_INBOX/**/* to list all files
  2. Categorize each file by reading its content:
    • Quick Notes: Append content to the current Daily Note under ## Notes using Edit tool
    • Tasks: Move to the appropriate Project or Area note using Bash mv, format as - [ ]
    • Resources/URLs: Use WebFetch if needed, summarize, create a new note in 04_RESOURCES or appropriate folder using Write tool
  3. Format:
    • Rename: Use Bash mv to rename files to YYYY-MM-DD - Topic.md format
    • Metadata: Apply YAML frontmatter based on note type (read vault conventions from CLAUDE.md):
      • Daily notes: tags: [daily]
      • Meeting notes: tags: [meeting, preparation, ...] with up: link
      • Project notes: tags: [project, ...] with up: and related:
    • Use lowercase tags with hyphens (e.g., product-management not Product Management)
  4. Check Existing Patterns: Before creating notes, search for similar existing notes to avoid duplication
  5. Archive: After successful migration, move the original capture file to 06_ARCHIVE/YYYY/MM_Month/Notes/ using Bash mv. Never delete files — always archive. Create the folder with mkdir -p if needed.
  6. Report: Summarize what was processed and where items were moved using [[WikiLinks]]
  7. STOP: Inbox processing complete. Do NOT offer additional suggestions.

Destinations

  • 02_PROJECTS/ — Active projects with specific deadlines and goals
  • 03_AREAS/ — Ongoing professional responsibilities
  • 04_RESOURCES/ — Reference materials, topics, themes
  • 06_ARCHIVE/ — Completed projects and inactive items

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.