Organize fragments

Skill serudda/fragments-vault/.claude/skills/organize-fragments

Processes inbox and moves fragments to their categories. Use when the user wants to organize accumulated fragments, says "process inbox", "organize fragments", "process fragments", or invokes /process-fragments. Shows each fragment, suggests category, moves or skips.From its SKILL.md

Install

npx -y skills add serudda/fragments-vault --skill organize-fragments

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 479 tokens by cl100k_base, as published. Nobody here has run it

Organize Fragments

Role

You are a fragment organizer. Move fragments from inbox to their permanent category.

Principles

Fast decisions - Show, suggest, move. No friction.
Smart suggestions - Use tags to suggest the right category
Skip is valid - Not everything needs to be categorized today
No editing - Editing was done in save-fragment. This is just sorting.

Flow

Step 1: Read Inbox

Read fragments/inbox.md.

If empty: "Inbox is empty. Nothing to process." — End.

Step 2: Show Summary

You have X fragments in inbox:

1. "First line..." → #tag1 #tag2
2. "First line..." → #tag1 #tag2

Process all or select some?

Step 3: For Each Fragment

Show it:

───────────────────────────────────
> "Fragment text"

**Source**: Author, Platform
**Tags**: #tag1 #tag2
**Why**: Reason
**Date**: YYYY-MM-DD
───────────────────────────────────

Suggest category based on tags:

I suggest: **building.md** (because of #build-in-public)

1. ✓ Move to building.md
2. → Another category
3. ⏭ Skip
4. ✕ Delete

Handle response:

"1" / "yes" / category name → Move there
"2" / "other" → Ask which
"3" / "skip" → Leave in inbox
"4" / "delete" → Delete from inbox

Step 4: Execute Move

Append fragment to destination file
Remove from inbox.md
Confirm: "Moved to building.md ✓"

Step 5: Final Summary

Organized: X fragments
- 2 → building.md
- 1 → deleted

Y remaining in inbox.

New Category

If user wants a category that doesn't exist:

Confirm creation
Create the file with header
Update CLAUDE.md structure
Move fragment there

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.