agentleFS
Sign inStart free
maroffomaroffo/claude-forge/skills/process-clippings/SKILL.md

process-clippings

Skill17 starsChanged 50 days agoMITView on GitHub

Process web clippings into Second Brain. Use when user mentions clippings, asks to process articles, or wants to integrate saved content. Not for newsletters (use newsletter-digest) or email bookmarks (use process-email-bookmarks).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After processing each clipping, report:

    line 70
  2. Distinctive:

    Code examples: only if genuinely useful, keep minimal

    line 81

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

ABOUTME: Process web clippings from Obsidian vault into Second Brain via CLI

ABOUTME: Reads clippings, categorizes, extracts knowledge, integrates, archives

Process Clippings Skill

Process web clippings from the Clippings folder and integrate them into the Second Brain.

Obsidian CLI: See ../_OBSIDIAN.md | Integration: See ../_SECOND_BRAIN.md

Vault Structure

Documents/                        (vault)
├── Clippings/                    ← Inbox (unprocessed)
│   └── Processed/                ← Archive
├── Second Brain/                 ← Destination for actionable knowledge
│   ├── Second Brain - AI Agents and Tools.md
│   ├── Second Brain - Claude Code.md
│   ├── Second Brain - Development.md
│   ├── Second Brain - DevOps and Cloud.md
│   └── Second Brain - Engineering Management.md
└── Bookmarks/                    ← Reference links only

Processing Workflow

Step 1: Find Clippings

obsidian files folder=Clippings ext=md

Step 2: For Each Clipping

  1. Read the clipping:
obsidian read path="Clippings/<file>.md"
  1. Categorize per ../_SECOND_BRAIN.md routing table
  2. Decide: Actionable (tutorials, patterns, code) -> Second Brain | Reference only -> Bookmarks
  3. Extract & integrate per ../_SECOND_BRAIN.md content template:
# Append to destination
obsidian append file="Second Brain - <Topic>" content="<extracted>"
# Update timeline
obsidian append file="Second Brain - Timeline" content="- **YYYY-MM-DD** | [Topic] | Source: Clipping | -> Second Brain - <File>.md"

Step 3: Archive Clipping

After successful integration:

obsidian move path="Clippings/<file>.md" to="Clippings/Processed/<file>.md"

Or if user prefers, delete:

obsidian delete path="Clippings/<file>.md"

Output Format

After processing each clipping, report:

Processed: [Clipping Title]
  -> Added to: Second Brain - [File].md
  -> Type: [Actionable/Reference]
  -> Key insight: [1-line summary]

Rules

See ../_SECOND_BRAIN.md for shared rules. Additional:

  • Code examples: only if genuinely useful, keep minimal

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.

Check your setup, free