web-recap
Skill2 starsChanged 2 months agoMITView on GitHub
Search browser history for URLs by topic or visit statistics. Use when asked about visited sites, browsing history, or recent online activity. Do NOT use for project/git recaps or agent-session history.
In this repository27 other files it gives its agents.
- agent-guardrailsSkill
- benchmark-checklistSkill
- blast-radiusSkill
- blog-reviewSkill
- code-reviewSkill
- create-verification-skillSkill
- datavizSkill
- grill-meSkill
- grok-repoSkill
- hammerspoonSkill
- html-lessonSkill
- karpathy-planningSkill
- mechanism-vizSkill
- obsidian-captureSkill
- obsidian-searchSkill
- paper-searchSkill
- readbackSkill
- repo-evalSkill
- route-skillSkill
- sherlockSkill
- show-meSkill
- sketch-conceptSkill
- skill-curatorSkill
- test-writingSkill
- tla-modelSkill
- write-docsSkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
Never dump raw output: Use jq to reduce tokens.
≈ “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.
Files
web-recap
Extracts browser history from Chrome, Chromium, Brave, Firefox, Safari, Edge. Run web-recap --help for all flags.
The word "recap" alone is not a browser-history request. Resolve the subject from context before invoking the CLI.
Prerequisite
The web-recap CLI must be installed and on PATH. Check with web-recap --help; if missing, install a release binary (macOS Apple Silicon shown — pick the matching asset for your platform):
curl -L https://github.com/robzolkos/web-recap/releases/latest/download/web-recap-darwin-arm64 -o ~/.local/bin/web-recap
chmod +x ~/.local/bin/web-recapOr build from source (needs Go 1.21+):
git clone https://github.com/robzolkos/web-recap.git && cd web-recap && go build ./cmd/web-recapKey Flags
--date YYYY-MM-DD Specific date (local timezone)
--start-date YYYY-MM-DD Start of range
--end-date YYYY-MM-DD End of range
--time HH Specific hour (e.g., --time 14 for 2pm-3pm)
--browser NAME chrome|firefox|safari|edge|brave|autoOutput Format
JSON with entries array. Each entry has: timestamp, url, title, domain, visit_count, browser.
Usage Patterns
Never dump raw output. Use jq to reduce tokens.
Search (find URLs by topic)
# Find entries matching a topic (searches title, domain, url)
web-recap | jq '[.entries[] | select(.title + .domain + .url | test("KEYWORD"; "i"))] | unique_by(.url) | map({title, url, domain})'Stats (visit overview)
# Domain counts, sorted by visits
web-recap | jq '[.entries[].domain] | group_by(.) | map({domain: .[0], count: length}) | sort_by(-.count)'Quick metadata
web-recap | jq '{start: .start_date, end: .end_date, total: .total_entries}'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
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.

