Antigravity-awesome-skills defuddle

Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.

install
source · Clone the upstream repo
git clone https://github.com/sickn33/antigravity-awesome-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sickn33/antigravity-awesome-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/antigravity-awesome-skills/skills/defuddle" ~/.claude/skills/sickn33-antigravity-awesome-skills-defuddle-051220 && rm -rf "$T"
manifest: plugins/antigravity-awesome-skills/skills/defuddle/SKILL.md
safety · automated scan (low risk)
This is a pattern-based risk scan, not a security review. Our crawler flagged:
  • global npm install
Always read a skill's source content before installing. Patterns alone don't mean the skill is malicious — but they warrant attention.
source content

Defuddle

Use Defuddle CLI to extract clean readable content from web pages. Prefer over WebFetch for standard web pages — it removes navigation, ads, and clutter, reducing token usage.

When to Use

  • Use when the user provides a normal webpage URL to read, summarize, or analyze.
  • Prefer it over noisy page-fetch approaches when token efficiency matters.
  • Use for docs, articles, blog posts, and similar public web content.

If not installed:

npm install -g defuddle

Usage

Always use

--md
for markdown output:

defuddle parse <url> --md

Save to file:

defuddle parse <url> --md -o content.md

Extract specific metadata:

defuddle parse <url> -p title
defuddle parse <url> -p description
defuddle parse <url> -p domain

Output formats

FlagFormat
--md
Markdown (default choice)
--json
JSON with both HTML and markdown
(none)HTML
-p <name>
Specific metadata property

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.