Defuddle extracts a page's main content and can return Markdown for your notes. Its repository calls the tool a work in progress, so I suggest checking one extracted page before handing a collection to an agent. ^[1]

Install Defuddle and extract one page

With Node.js and npm available, run the global installation command from Defuddle's README. The second command is its Markdown example for a public article. ^[1]

bash

npm install -g defuddle

bash

curl -L https://stephango.com/saw | npx defuddle parse --markdown

You should get extracted Markdown in the terminal. Compare it with the source page before saving it as a note. Check that headings, links and the paragraphs you need survived. The README says Defuddle removes page clutter; that is not a guarantee that every extraction preserves everything you want. ^[1]

Save the reviewed text in your Obsidian vault and retain the original URL so you can check the source later.

Add the Obsidian skills to your agent

The Obsidian skills repository documents this HTTPS installation command: ^[2]

bash

npx skills add https://github.com/kepano/obsidian-skills

Its skills cover Obsidian Markdown, Bases, JSON Canvas, the Obsidian CLI and Defuddle. Use the skill appropriate to the file you are working on; an ordinary note needs different instructions from a canvas. ^[2]

Ask the agent to work on the note you saved, then open the result in Obsidian. Check that its links resolve and that the text still agrees with the source. Review the change before letting the agent edit the rest of your vault.

Review Second Brain OS before adding automation

The caption includes this command to add the project's skills: ^[5]

bash

npx skills add undefined-ui/second-brain-os

The repository's full setup also includes a starter vault, commands, agents and supporting scripts. Installing skills alone does not reproduce that setup. Its README specifically says its maintenance commands need scripts copied into the vault. Follow the linked quickstart when you want those features. ^[3]

Per the repository, the workflow keeps source material separate from linked wiki notes. Start with a copy of your notes and inspect the first changes. Keep the source article available when checking whether an agent's summary or cross-reference is correct. ^[3]

Try Tolaria separately if you prefer its editor

Tolaria can open a folder of Markdown files as a vault. It is optional for this workflow. On macOS with Homebrew installed, its official documentation gives this command: ^[4]

bash

brew install --cask tolaria

Open Tolaria and choose its Getting Started vault to inspect the app before opening your notes. The official guide also provides desktop downloads for Windows and Linux. ^[4]

Use a copied folder for the first comparison. Open a note in both editors and check its formatting and links before choosing where to maintain the originals.