playbooks

home / skills / openclaw / skills / browser-bookmarks-cleanup

browser-bookmarks-cleanup skill

/skills/makkoncept/browser-bookmarks-cleanup

This skill analyzes, organizes, and safely cleans browser bookmarks on macOS using local files, with opt-in writes and rollback.

npx playbooks add skill openclaw/skills --skill browser-bookmarks-cleanup

Review the files below or copy the command above to add this skill to your agents.

Files (8)
SKILL.md
2.0 KB
---
name: browser-bookmarks-cleanup
description: Analyze, organize, and clean browser bookmarks on macOS using on-disk bookmark and history files. Detects duplicates, stale bookmarks, tracking parameters, and folder issues. All writes are opt-in with backup and rollback.
---

# Browser Bookmark Cleanup

Analyze first, organize, then clean up. All writes are opt-in and reversible.

> **Supported browsers:** Chrome and Firefox out of the box. Other Chromium-based browsers (Edge, Brave, Arc, etc.) can be handled by pointing to their profile directories, which use the same Bookmarks JSON format as Chrome.

## Workflow

1. Discover browser profiles.
2. Run read-only analysis and share findings.
3. Propose cleanup plan with preview.
4. Get explicit user approval before any writes.
5. Dry-run first, then write with automatic backup.
6. Report changes and how to roll back.

## Hard Safety Rule

Never send network requests to bookmark URLs. Analysis uses only local files.

## Commands

Discover profiles:

```bash
python3 scripts/browser_bookmarks.py discover [--browser chrome|firefox]
```

Analyze bookmarks:

```bash
python3 scripts/browser_bookmarks.py analyze --bookmarks "<PATH>" --output /tmp/bookmark-analysis.json
```

Apply plan (dry-run by default, `--write` to commit):

```bash
python3 scripts/browser_bookmarks.py apply-plan --bookmarks "<PATH>" --plan /tmp/bookmark-plan.json [--write]
```

## Analysis Categories

1. Exact and semantic duplicate URLs
2. Tracking-parameter variants (`utm_*`, `gclid`, `fbclid`, etc.)
3. Subdomain and domain concentration
4. HTTP links that should be HTTPS
5. Empty, singleton, deep, and oversized folders
6. Weak bookmark names
7. Old bookmarks by age
8. Never-visited and stale bookmarks (from browser history)

## Approval Gate

Before any write: show plan preview, get explicit approval, ask user to close the browser.

## Plan Format

See `references/plan-schema.md` for the JSON plan structure.

## Rollback

Restore the timestamped backup file created before any write.

Overview

This skill analyzes, organizes, and cleans browser bookmarks on macOS by inspecting on-disk bookmark and history files. It supports Chrome and Firefox out of the box and can handle other Chromium-based profiles by pointing to their profile directories. All write operations are opt-in, performed after explicit approval, and fully reversible with automatic backups and rollback instructions.

How this skill works

The skill discovers local browser profiles, reads bookmark and history files in a read-only analysis pass, and produces a detailed cleanup plan. It detects exact and semantic duplicate URLs, tracking-parameter variants, stale or never-visited items, HTTP-to-HTTPS candidates, folder issues, and weak or old bookmarks. Writes only occur after the user reviews a preview and explicitly approves the plan; a dry-run and timestamped backup are created before any commit, enabling rollback.

When to use it

  • You have thousands of bookmarks and need to reduce clutter.
  • You want to remove tracking parameters from saved links for privacy and consistency.
  • You need to consolidate duplicates across folders or profiles.
  • You want to identify stale or never-visited bookmarks using browser history.
  • You need safe, reversible batch edits to bookmark files on macOS.

Best practices

  • Run the discover and analyze steps first and review the generated JSON report before making changes.
  • Always inspect the proposed cleanup plan preview; the tool requires explicit approval before writing.
  • Close the browser before applying writes to ensure consistent file state.
  • Use dry-run mode to validate changes, then commit with --write when satisfied.
  • Keep the generated timestamped backup until you confirm the changes are correct.

Example use cases

  • Detect and remove duplicate and near-duplicate bookmarks across Chrome and Firefox profiles.
  • Strip UTM, gclid, fbclid and other tracking parameters from saved links in bulk.
  • Identify oversized or deep folder structures and suggest folder merges or flattening.
  • Find bookmarks that point to HTTP and suggest HTTPS replacements when available.
  • Restore bookmarks from the created backup after an accidental change.

FAQ

Which browsers are supported?

Chrome and Firefox are supported out of the box. Other Chromium-based browsers (Edge, Brave, Arc, etc.) can be handled by pointing to their profile directories using the same Bookmarks JSON format.

Does the tool contact bookmark URLs over the network?

No. A hard safety rule prevents any network requests to bookmark URLs; all analysis uses only local files.

Can I undo changes if I make a mistake?

Yes. Before any write the tool creates a timestamped backup and provides rollback instructions to restore the previous state.