agentleFS
Sign inStart free
Kevin-Liu-01Kevin-Liu-01/Local-Search/scripts/SKILL.md

local-search-scripts-skill

Skill16 starsChanged 31 days agoMITView on GitHub

Maintenance scripts for local-search. Read before editing scripts here.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not delete browser profile data or cookies from scripts.

    line 20
  2. Very specific:

    Prefer exact managed local-search targets over broad browser/process cleanup.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

local-search / scripts

Purpose

Small agent-callable wrappers around the Rust CLI for cleanup and maintenance.

Mental model & key files

  • local-search-cleanup.sh delegates to lsearch cleanup.
  • capture-agent-guide.mjs captures the public-safe visual guide with an isolated agent-browser session. It never attaches to a user's signed-in Chrome. Build site/ first for the local Manrope font; --serve opens a loopback preview.
  • Scripts should stay thin; command behavior belongs in Rust.

Patterns to follow / invariants

  • Dry-run by default for cleanup.
  • Do not delete browser profile data or cookies from scripts.
  • Prefer exact managed local-search targets over broad browser/process cleanup.

Common tasks → first action

  • Need to stop the managed browser: run scripts/local-search-cleanup.sh --kill.
  • Need to inspect cleanup state: run scripts/local-search-cleanup.sh --pretty.

Gotchas

  • The managed Chrome profile is persistent by design. Cleanup removes lock and DevTools marker files, not profile data.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free