Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

browsing-history

Sterne308

Forks46

Aktualisiert1. Juni 2026 um 23:44

Query browsing history from all synced devices (iPhone, Mac, iPad, desktop). Supports natural language queries for filtering by date, device, domain, and keywords. Uses LLM classification for content categories. Can output to stdout or save as markdown/JSON to Obsidian vault.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

glebis

glebis/claude-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Allgemeine BürokräfteBüro- und Verwaltungsberufe·SOC 43-9061

Datei-Explorer

6 Dateien

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

elimination-research

glebis/claude-skills

This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric evidence, tournament-style comparison, source/domain classification, image-supported consumer reports, raw data tables, and ownership-cost estimates for replaceable parts. Use this skill whenever the user asks to compare options, buy something, shortlist candidates, rank alternatives, generate a "don't make me think" report, or produce a full audit report with raw numeric data.

2026-07-06308

nielsen-heuristics

glebis/claude-skills

This skill should be used to run a formal heuristic evaluation of a design artifact against Jakob Nielsen's 10 usability heuristics, producing an evidence-backed, severity-scored report. Use it when the user wants a "heuristic evaluation", "usability review", "Nielsen heuristics check", "UX heuristic audit", or asks whether a screenshot, live URL, HTML page, codebase UI, interface description, or JTBD/spec document holds up against usability principles. Accepts five input types (screenshot/image, live URL, codebase/HTML, interface description, JTBD/spec doc) and adapts its rigor and output honestly to what is actually observable. Can render the report as plain markdown (default) or as a Tufte-style HTML report, and can export findings above a severity threshold as Linear or Beads (bd) tasks after confirmation.

2026-07-04308

i18n-studio

glebis/claude-skills

This skill should be used when editing, translating, or reviewing an Astro-style i18n string corpus (files of the form export default { en: {...}, ru: {...} } under src/i18n/strings), or when the user wants to fill in missing translations, audit coverage, accept/review translations, propagate an edit across duplicate strings, get translation candidates, bulk-edit UI microcopy, or open a visual/keyboard translation editor. Drives the standalone i18n Studio tool at ~/ai_projects/i18n-studio (AST-safe minimal-diff saves via ts-morph, acceptance review state, duplicate propagation, hot-reload, and Claude translation suggestions).

2026-07-03308

feature-factory

glebis/claude-skills

This skill should be used when taking a single software feature from intent to shipped as a solo developer — goal-first, TDD, deterministic verification, evidence only where it earns its keep, and human judgment at the two moments that matter (goal approval, merge). Trigger when the user says "let's build feature X", "ship this feature", "run this through the factory", "write a goal contract", "feature-factory", or wants a disciplined intent→merge loop that resists process bloat. NOT for whole-product planning, multi-feature roadmaps, or autonomous multi-agent swarms.

2026-07-01308

the-goal

glebis/claude-skills

A Theory-of-Constraints diagnostic for deciding what to automate with AI agents. Before building any automation, skill, Goal, loop, or schedule, it walks Goldratt's Five Focusing Steps over the user's work system to find the real bottleneck, then recommends the single highest-leverage automation aimed at the constraint plus a what-NOT-to-automate list. Use when the user asks "what should I automate", "where do I point my agents", "prioritize my automation backlog", "which workflow should I agentify", "is this worth building", "find my bottleneck", "what's the highest-leverage thing", when they are about to build a Claude Code skill/Goal/loop/schedule and aren't sure it matters, or during a review of their automations. Guards against the common failure of automating busywork (a local optimum) instead of the constraint.

2026-07-01308

design-tokens

glebis/claude-skills

This skill should be used to set up, validate, resolve, and export design tokens following the DTCG (Design Tokens Community Group) Format Module 2025.10 standard. Use when the user wants to define a design token set globally or per project, compile tokens to CSS variables, layer a project's tokens over a global brand base, or produce an on-brand context file for other generation skills. Triggers on "set up design tokens", "create a token set", "compile tokens to CSS", "design system variables", "brand tokens".

2026-07-01308

name	browsing-history
description	Query browsing history from all synced devices (iPhone, Mac, iPad, desktop). Supports natural language queries for filtering by date, device, domain, and keywords. Uses LLM classification for content categories. Can output to stdout or save as markdown/JSON to Obsidian vault.

Browsing History Skill

Query browsing history from all synced devices with natural language.

When to Use

Use this skill when the user asks about:

Articles/pages they read (yesterday, last week, etc.)
Browsing history from specific devices (iPhone, iPad, desktop)
Finding pages by topic, domain, or keyword
Exporting browsing history to files
Grouping history by category or domain

Database

Location: ~/data/browsing.db

Synced devices: iPhone, iPad, Mac, desktop, Android

Timestamps

visit_time: Actual visit timestamp from Chrome (100% coverage for all devices)
first_seen: Import timestamp (fallback when visit_time unavailable)

The skill uses COALESCE(visit_time, first_seen) for accurate time-based queries.

Usage

python3 ~/.claude/skills/browsing-history/browsing_query.py "<query>" [options]

Options

Option	Description	Example
`--device`	Filter by device	`--device iPhone`
`--days`	Number of days back	`--days 7`
`--domain`	Filter by domain	`--domain medium.com`
`--limit`	Max results	`--limit 50`
`--format`	Output format	`--format json`
`--output`	Save to file	`--output history.md`
`--group-by`	Group results	`--group-by domain` or `--group-by category`
`--categorize`	Use LLM to categorize	`--categorize`

Example Queries

Basic queries:

# Yesterday's browsing history
python3 ~/.claude/skills/browsing-history/browsing_query.py "yesterday"

# Articles from iPhone yesterday
python3 ~/.claude/skills/browsing-history/browsing_query.py "yesterday" --device iPhone

# Last week's history grouped by domain
python3 ~/.claude/skills/browsing-history/browsing_query.py "last week" --group-by domain

# Find articles about economics
python3 ~/.claude/skills/browsing-history/browsing_query.py "economics" --days 7

Save to Obsidian:

# Save yesterday's history as markdown
python3 ~/.claude/skills/browsing-history/browsing_query.py "yesterday" \
  --output ~/Research/vault/browsing-2025-11-27.md

# Save with LLM categorization
python3 ~/.claude/skills/browsing-history/browsing_query.py "yesterday" \
  --categorize --group-by category \
  --output ~/Research/vault/browsing-categorized.md

# Save as JSON
python3 ~/.claude/skills/browsing-history/browsing_query.py "last week" \
  --format json --output ~/Research/vault/history.json

Device-specific:

# iPhone tabs
python3 ~/.claude/skills/browsing-history/browsing_query.py "yesterday" --device iPhone

# Desktop history
python3 ~/.claude/skills/browsing-history/browsing_query.py "today" --device desktop

# All mobile devices
python3 ~/.claude/skills/browsing-history/browsing_query.py "yesterday" --device mobile

Search and filter:

# Sites starting with "joy"
python3 ~/.claude/skills/browsing-history/browsing_query.py "joy" --days 7

# Medium.com articles
python3 ~/.claude/skills/browsing-history/browsing_query.py "last month" --domain medium.com

Natural Language Patterns

The script recognizes:

Pattern	Interpretation
`yesterday`	Previous day
`today`	Current day
`last week`	Past 7 days
`last month`	Past 30 days
`last N days`	Past N days

Keywords are searched in URL and title.

Output Formats

Markdown (default)

# Browsing History: yesterday

*47 unique URLs from 2025-11-27*

## 2025-11-27

- [Article Title](https://example.com/article) - iPhone - 14:32
- [Another Page](https://another.com/page) - desktop - 16:45

Markdown with categories (--categorize --group-by category)

# Browsing History: yesterday

## News & Current Events
- [Breaking: Something Happened](https://news.com/...) - iPhone

## Technology & Programming
- [How to Build APIs](https://dev.to/...) - desktop

## Research & Learning
- [Academic Paper on AI](https://arxiv.org/...) - Mac

JSON (--format json)

{
  "query": "yesterday",
  "date_range": "2025-11-27",
  "total": 47,
  "results": [
    {"url": "...", "title": "...", "device": "iPhone", "time": "14:32", "category": "News"}
  ]
}

Workflow Examples

User: "Show me articles I read yesterday on my phone"

python3 ~/.claude/skills/browsing-history/browsing_query.py "yesterday" --device iPhone

User: "Save my browsing history from last week to Obsidian, grouped by category"

python3 ~/.claude/skills/browsing-history/browsing_query.py "last week" \
  --categorize --group-by category \
  --output ~/Research/vault/browsing-week.md

User: "Help me find that article about economics I read on my computer"

python3 ~/.claude/skills/browsing-history/browsing_query.py "economics" \
  --device desktop --days 7

User: "Sites that start with 'joy' from last week"

python3 ~/.claude/skills/browsing-history/browsing_query.py "joy" --days 7

Notes

URLs are deduplicated per day (same URL on same day = one entry)
visit_time: Actual visit timestamps from Chrome history
- Desktop: 100% coverage (from Chrome SQLite last_visit_time)
- Mobile: 100% coverage (extracted from Chrome Sync LevelDB)
first_seen: Fallback import timestamp (~15min resolution)
LLM categorization uses Claude 3.5 Haiku via llm CLI