agentleFS
BayramAnnakovBayramAnnakov/ai-personal-os-skills/skills/atomize/SKILL.md

atomize

Skill19 starsChanged 8 months agoMITView on GitHub

Atomize any content into your Zettelkasten vault. Accepts text, file paths, or URLs. Extracts atomic ideas, finds connections to existing notes, and saves to your vault.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. sergeeey/Claude-cod-top-2026★ 9same name
    2. blueOctopusAI/intel-hub★ 0same 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 repository5 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 10 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask ONE question using AskUserQuestion:

    line 18
  2. Distinctive:

    Pasted text: Use it directly

    line 26
  3. Distinctive:

    File path: Read the file

    line 27
  4. Distinctive:

    Describe an idea: Use their description

    line 28
  5. Very specific:

    Daily logs: Read all notes/daily-log-*.md files, extract Highlight and Blocker sections (ignore Vitals metrics — energy/focus/mood are …

    line 29
  6. Very specific:

    Use Glob to find all existing atomic/*.md files

    line 50
  7. Very specific:

    Use Grep to search existing notes for related keywords and concepts

    line 51
  8. Very specific:

    If related notes exist, add [[wikilinks]] with a brief explanation of the connection

    line 52
  9. Distinctive:

    If no related notes exist, that's fine — connections grow over time

    line 53
  10. Very specific:

    Create the atomic/ directory if it doesn't exist

    line 58
  11. Distinctive:

    Check existing files to avoid number collisions

    line 60
  12. Distinctive:

    If this is their first time using /atomize and they have fewer than 3 atomic notes total, add:

    line 100
  13. Very specific:

    If atomic/ has 0 existing notes: skip connection search, just create the notes and mention "No existing notes to connect to yet — your …

    line 106
  14. Distinctive:

    If input is very short (1 sentence): create just 1 atomic note, that's fine

    line 107
  15. Distinctive:

    If input is very long (full article): extract the 5-7 most important ideas, not everything

    line 108
  16. Distinctive:

    If a daily log has "Nothing major" as blocker: skip it, no knowledge there

    line 109
  17. Distinctive:

    Do NOT turn this into a long conversation.

    line 111

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

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

/atomize — Knowledge Atomizer

Turn any content into connected atomic notes in your Zettelkasten vault.

Input Flow

Ask ONE question using AskUserQuestion:

Question 1: What to atomize?

  • Question: "What do you want to atomize?"
  • Options: ["Paste text here", "Give a file path", "Describe an idea", "Atomize my recent daily logs"]
  • Accept whatever they provide.

Based on their choice:

  • Pasted text: Use it directly
  • File path: Read the file
  • Describe an idea: Use their description
  • Daily logs: Read all notes/daily-log-*.md files, extract Highlight and Blocker sections (ignore Vitals metrics — energy/focus/mood are data, not knowledge)

Extraction Rules

From the input, extract atomic ideas following these rules:

  1. One concept per note — if an idea has two parts, make two notes
  2. 2-5 sentences — express the idea concisely
  3. Own words — reformulate, don't copy-paste. The goal is YOUR understanding, not a quote
  4. Tags — add 2-4 relevant tags based on content
  5. Source attribution — note where the idea came from

Typically extract 2-5 atomic notes from a paragraph or article excerpt. For daily logs, focus on:

  • Ideas hidden in Highlight entries (things learned, realized, discovered)
  • Patterns in Blocker entries (recurring problems = knowledge)
  • Any insights that weren't fully developed

Connection Discovery

For EACH extracted idea:

  1. Use Glob to find all existing atomic/*.md files
  2. Use Grep to search existing notes for related keywords and concepts
  3. If related notes exist, add [[wikilinks]] with a brief explanation of the connection
  4. If no related notes exist, that's fine — connections grow over time

File Creation

  1. Get today's date via date +%Y-%m-%d (Bash)
  2. Create the atomic/ directory if it doesn't exist
  3. For each atomic idea, create a file: atomic/YYYY-MM-DD_NNN.md where NNN is a 3-digit sequence number (001, 002, 003...)
  4. Check existing files to avoid number collisions

File Template

---
id: YYYY-MM-DD_NNN
title: "[Descriptive title]"
date: YYYY-MM-DD
source: "[Where the idea came from]"
tags: [tag1, tag2]
---

# [Title]

[2-5 sentences expressing the idea in your own words]

## Connections

- [[related-note-id]] — [Why this connects]

## Source Context

[Brief: who said it, where you read it, what prompted the thought]

---
*Created via /atomize*

After Saving

Print a summary:

Atomized! X notes created, Y connections found to existing notes.

New notes:

  • atomic/YYYY-MM-DD_001.md — "[title]"
  • atomic/YYYY-MM-DD_002.md — "[title]" → connected to [[existing-note]]
  • atomic/YYYY-MM-DD_003.md — "[title]"

If this is their first time using /atomize and they have fewer than 3 atomic notes total, add:

Tip: The more notes you add, the more connections appear. Try /atomize daily with one article, conversation, or idea.

Edge Cases

  • If atomic/ has 0 existing notes: skip connection search, just create the notes and mention "No existing notes to connect to yet — your graph starts here!"
  • If input is very short (1 sentence): create just 1 atomic note, that's fine
  • If input is very long (full article): extract the 5-7 most important ideas, not everything
  • If a daily log has "Nothing major" as blocker: skip it, no knowledge there

Do NOT turn this into a long conversation. Extract, create, summarize. The whole interaction should take under 3 minutes after the user provides input.

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.