organize-fragments
npx machina-cli add skill serudda/fragments-vault/organize-fragments --openclawOrganize 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
Source
git clone https://github.com/serudda/fragments-vault/blob/main/.claude/skills/organize-fragments/SKILL.mdView on GitHub Overview
Organize fragments from inbox.md into permanent categories. It reads the inbox, shows a summary, and for each fragment suggests a destination based on tags. You can move, skip, or delete fragments, and add new categories when needed.
How This Skill Works
It reads inbox.md, displays a concise summary, and for each fragment shows the text, source, tags, and a why. Based on tags, it suggests a best category and prompts for a move, skip, or delete. When moving, it appends to the destination file and removes it from inbox.md; a final summary reports results.
When to Use It
- You want to organize all new fragments in inbox.md quickly in a single pass.
- You want to categorize fragments automatically using tag signals to improve retrieval.
- You want to selectively process only some fragments and skip others for later.
- You need to create a new category when no existing file fits the fragment.
- You want a final summary showing moves, deletes, and remaining items in inbox.
Quick Start
- Step 1: Read inbox.md for new fragments.
- Step 2: Review each fragment, its source, and tags, using the suggested category to decide.
- Step 3: Respond with move, skip, or delete; the system updates the destination and inbox.md and shows a final summary.
Best Practices
- Process the inbox in a single pass to minimize friction.
- Rely on tags to drive category suggestions for consistency.
- Use skip for items you plan to revisit later to avoid misfiling.
- Always confirm before moving to prevent incorrect categorization.
- When creating a new category, follow the New Category steps to update CLAUDE.md.
Example Use Cases
- Process a batch of fragments and move them to building.md based on a tag hint; others may be moved to research.md or skipped.
- Move fragments to research.md or ideas.md according to their tags; keep non-matching items in inbox for later.
- Create a new category when a fragment does not fit existing files and move the fragment there.
- Delete a fragment that is no longer relevant and update the final summary accordingly.
- Use process-fragments to organize a daily backlog and end with a clear overview of moves and remaining items.
