organize-clippings

organize-clippings is a skill for Claude Code from JeanDiable/obsidian-claude. It costs 28 tokens per session (752 once invoked), scanned A, original, MIT.

A workflow for processing uncategorized clippings in an Obsidian vault by adding metadata, summaries, links to related notes, and category folders.

In plain words
What is it for?
Use it to review files in the clippings inbox, assign categories, complete fields such as tags and sources, condense long content, and move notes into organized subfolders.
Why use it?
It gives loose saved material a consistent structure and makes connections between notes easier to find.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the obsidian-claude plugin — 19 skills shipped together

Good fit Use it to review files in the clippings inbox, assign categories, complete fields such as tags and sources, condense long content, and move notes into organized subfolders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeandiable/obsidian-claude/organize-clippings
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add JeanDiable/obsidian-claude --skill organize-clippings
Clone the repo
git clone --depth 1 https://github.com/JeanDiable/obsidian-claude

Made for: Claude Code.

Or install obsidian-claude, the plugin that ships this one along with the rest of its 19 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for organize-clippings

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/organize-clippings/github.svg)](https://agentmods.dev/skills/jeandiable/obsidian-claude/organize-clippings)
Your own site
<a href="https://agentmods.dev/skills/jeandiable/obsidian-claude/organize-clippings"><img src="https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/organize-clippings/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for organize-clippings

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeandiable/obsidian-claude/organize-clippings"><img src="https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/organize-clippings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 752 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00752
Opus 5 $0.00014 $0.00376
Sonnet 5 $0.00006 $0.00150
Haiku 4.5 $0.00003 $0.00075

Measured 12d ago against content hash 1ec928a3243b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

organize-clippings scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/organize-clippings/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Organize Clippings

Process uncategorized clippings in 50_Clippings/ root — add metadata, consolidate content, create connections, and move to category subfolders.

Vault Path

/Library/Mobile Documents/iCloudmd~obsidian/Documents/My_note

Workflow

Phase 1: Scan

  1. List all .md files directly in 50_Clippings/ root (not in subfolders — those are already categorized)

  2. For each file, read content and determine:

    • Current metadata state (missing/partial/complete)
    • Best category: AI, 金融, 科技, 自我成长, 社会学, 心理学, 投资, or suggest a new category
    • Content quality: needs condensing? already concise?
  3. Present plan to user:

    Uncategorized clippings: N
    Category breakdown:
    - AI: X files
    - 金融: Y files
    - 科技: Z files
    ...
    Files needing condensing: M
    
  4. Ask user to confirm categorization and any new subfolder creation.

Phase 2: Process Each File

For each clipping:

  1. Fix metadata: Add/complete YAML frontmatter:

    ---
    title: "..."
    created: YYYY-MM-DD
    modified: YYYY-MM-DD (today)
    tags: [tag1, tag2, tag3]
    description: "1-2 sentence summary"
    source: "URL or source name"
    ---
    
  2. Condense if needed: If the content is excessively verbose (web scraping artifacts, excessive formatting):

    • Preserve all substantive information
    • Remove navigation elements, ads, redundant text
    • Restructure into clean markdown with headers
    • Keep the original meaning and key details
  3. Build connections:

    • Use obsidian search query="<key terms>" to find related content in vault
    • Insert [[wikilinks]] inline where concepts match existing files
    • Add/update ## Related section immediately after YAML frontmatter (before main content)
    • Update any linked Wiki entries to point back

Phase 3: Move to Subfolders

For each processed file:

  1. Move to the determined category subfolder: 50_Clippings/<Category>/
  2. If file has an attach/ subfolder with images, move those too
  3. Verify the file is accessible after move

Read the full file on GitHub · 91 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 91 lines · 28 tokens per session scan A 1ec928a3243b

Subscribe to this mod's changes

organize-clippings is a skill published in the GitHub repository JeanDiable/obsidian-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 752 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories