One-click install
npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill defuddle-mateus2411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defuddle
Source: https://github.com/Mateus2411/Hermes-PersonalBot/tree/main/skills/obsidian-skills/skills/defuddle
Command: npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill defuddle-mateus2411

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of wasting tokens and effort on noisy webpage content by extracting only the main readable text you actually need.

Core Features & Use Cases

  • Clean Markdown Extraction: Converts a webpage into readable markdown by removing clutter like navigation, ads, and repetitive elements.
  • Token-Saving Output: Helps you reduce the amount of irrelevant text you send to an AI for summarization or analysis.
  • Targeted Metadata Extraction: Extracts specific fields such as title, description, or domain when you only need key page attributes.

Quick Start

Use Defuddle to parse a web page into markdown by running: defuddle parse <url> --md

Frequently Asked Questions about defuddle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract clean markdown from a webpage?

To extract clean markdown from a webpage, run the Defuddle CLI with the parse command and the --md flag, which strips away navigation, ads, and repetitive clutter to isolate the main readable text.

What is the best way to reduce tokens when summarizing web articles?

The best way to reduce tokens for AI summarization is to parse the web page into clean markdown first, removing irrelevant elements like navigation and ads before submitting the text.

Can I extract specific metadata like title and description from a web page?

Yes, you can extract targeted metadata fields such as the title, description, or domain from a web page when you only need key page attributes instead of the full article text.

Does this webpage parsing approach work with all URL types?

This webpage parsing approach does not work with all URL types; it explicitly avoids URLs ending in .md, where WebFetch should be used instead, but handles standard articles and online documentation.

When should I not use webpage parsing for markdown extraction?

You should not use webpage parsing for markdown extraction when dealing with URLs ending in .md, because WebFetch should be used instead to retrieve the raw markdown content directly.