fetch-favicons

Fetch favicons from Google, DuckDuckGo, and direct sources with automatic fallback.

Updated Dec 4, 2014
One-click install
npx skills add https://github.com/kevintraver/dotfiles --skill fetch-favicons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-favicons
Source: https://github.com/kevintraver/dotfiles/tree/main/agent-skills/fetch-favicons
Command: npx skills add https://github.com/kevintraver/dotfiles --skill fetch-favicons

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) components.

What problem does it solve?

This Skill automates fetching website favicons from multiple sources, ensuring you always have a site icon for dashboards, bookmarks, or UI elements without manual searching.

Core Features & Use Cases

  • Multi-source fallback: Google, DuckDuckGo, and direct retrieval to maximize success.
  • Domain extraction: Accepts domains or URLs and normalizes to a domain.
  • Output versatility: Saves as PNG or ICO depending on source.

Quick Start

python3 scripts/fetch_favicon.py github.com

Frequently Asked Questions about fetch-favicons

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

FAQPage Schema
How do I fetch favicons for a domain automatically?

Fetch favicons automatically by running the Skill with a domain or URL as input. It retrieves site icons from multiple sources—Google, DuckDuckGo, and direct domain lookup—with automatic fallback to maximize success rates and returns PNG or ICO format files.

Can I extract favicons from multiple domains at once?

Yes, the Skill processes multiple domains with cross-source retrieval and automatic fallback. Pass each domain or URL to fetch favicons in batch, with platform-friendly exit codes indicating success or failure for each source.

What formats do favicons get saved as?

Favicons are saved as PNG or ICO depending on the source retrieved. The Skill normalizes output across Google, DuckDuckGo, and direct sources, ensuring compatibility for dashboards, bookmarks, and UI elements.

Does the Skill work with full URLs or just domain names?

The Skill accepts both full URLs and domain names. It automatically extracts and normalizes the domain from URLs, then retrieves favicons using that normalized domain across all configured sources.

What happens if a favicon isn't found from the primary source?

The Skill automatically falls back to secondary and tertiary sources when the primary fails. It tries Google, then DuckDuckGo, then direct retrieval to maximize the chance of finding a site icon.