chrome-history
Query Chrome browsing history with natural language. Filter by date range, article type, keywords, and specific sites.
What this skill does
# Chrome History Query Skill Search and filter your Chrome browsing history using natural language queries. ## What It Does 1. Parses natural language queries to understand date ranges and filters 2. Queries Chrome's SQLite history database 3. Filters out noise (social media, email, redirects) 4. Groups results by type (reading, research, tools, events) 5. Returns formatted markdown with links ## Supported Queries ### Date Range - "yesterday" → previous day only - "today" → today only - "last week" → past 7 days - "last month" → past 30 days - "last 2 weeks" → past 14 days ### Content Filters - "articles I read" → reading cluster (news, blogs, essays) - "scientific articles" → research cluster (papers, docs) - "code/research" → GitHub, Stack Overflow, docs ### Keyword Filtering - "articles about AI" → finds pages mentioning AI - "scientific articles about climate" → finds research pages mentioning climate ### Site-Specific - "reddit threads" → reddit.com only - "on medium" → medium.com only - "twitter posts" → twitter.com only ## Example Queries ``` "articles I read yesterday" "articles about AI I read yesterday" "scientific articles for the last week" "research about machine learning this week" "reddit threads last month" "code repos I visited yesterday" "on medium this week" ``` ## Usage Run directly with a query: ```bash python3 ~/.claude/skills/chrome-history/chrome_history_query.py "articles I read yesterday" ``` Or integrate into Claude Code when user asks: - "Show me articles I read yesterday" - "What scientific papers did I look at last week?" - "Show reddit threads I visited last month" - "Articles about AI from yesterday?" ## Configuration - **Chrome History**: `~/Library/Application Support/Google/Chrome/Default/History` - **Vault Location**: `/Users/glebkalinin/Brains/brain` - **Filtered Sites**: Social media, email, Google redirect wrappers - **Clustering**: Automatic by domain type (reading, research, tools, events) ## Exclusions Automatically filters out: - Social media: Facebook, Instagram, Twitter, TikTok, Reddit, LinkedIn - Email: Gmail, Outlook - Shopping: Amazon, eBay - Google redirects: google.com/url wrappers - Utility sites: FreeFeed, YouTube ## Output Format Results grouped by content type with timestamps: ``` ## Chrome History: articles about AI yesterday *Found 5 items* ### Reading (3) - 14:22 [The more that people use AI...](url) - 16:38 [AI makes you smarter but...](url) ### Research (2) - 11:23 [GitHub: AI project](url) ```
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.