chrome-history

Parse natural-language queries to filter Chrome history by date, content, and site.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/KISHOR403/claude-skills --skill chrome-history-kishor403
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-history
Source: https://github.com/KISHOR403/claude-skills/tree/main/chrome-history
Command: npx skills add https://github.com/KISHOR403/claude-skills --skill chrome-history-kishor403

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browsing history search across desktop and synced mobile history is tedious; this skill enables natural-language queries to filter Chrome history by date ranges, content type, keywords, and site constraints.

Core Features & Use Cases

  • Accesses desktop (SQLite History) and synced (LevelDB) history to produce unified results.
  • Supports natural-language date ranges (yesterday, today, last week, last month, last 2 weeks) and content filters (articles, reading, research, code sites).
  • Provides site-specific filtering and keyword-based searches with clustering by domain type and clean markdown output.
  • Returns results grouped by category (Reading, Research, Tools, Events) with timestamps and direct URLs.

Quick Start

Run a query like 'articles I read yesterday' to retrieve matching Chrome history.

Frequently Asked Questions about chrome-history

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

FAQPage Schema
How do I search Chrome history using natural language?

You can search Chrome history by parsing natural-language queries to extract date ranges, keywords, and site constraints. The tool queries both desktop SQLite and synced LevelDB browser history, returning clustered markdown results.

Can I filter browser history by content type like articles or research?

Yes, browser history can be filtered by content type. Natural-language queries support filtering Chrome history for articles, reading, research, and code sites, grouping results into categories with timestamps and URLs.

Does querying synced mobile history require accessing LevelDB?

Querying synced mobile history requires reading LevelDB data. The tool unifies desktop SQLite History and synced LevelDB browser history, applying blocklists and deduplication to generate a single set of search results.

How do I cluster Chrome history results by domain?

Chrome history results are clustered by domain type automatically. After querying the SQLite and LevelDB sources, the tool applies domain clustering and outputs results formatted in markdown with per-item details and domain clusters.

What natural language date ranges work for Chrome history search?

Natural language date ranges like yesterday, today, last week, last month, and last 2 weeks work for Chrome history search. The parser extracts these ranges to filter both desktop and synced mobile browser history data.

Are there limitations when searching synced mobile browser history?

A limitation of searching synced mobile browser history is that data must exist in the LevelDB sync files. The tool queries LevelDB alongside desktop SQLite history, but synced data availability depends on Chrome's sync configuration.