Browsing History
glebis/claude-skills
Query browsing history from all synced devices (iPhone, Mac, iPad, desktop).
Browse and search past analyses from the knowledge system's analysis archive.
MITAuto-check passed
Install History
$ npx skills add ai-analyst-lab/ai-analyst --skill history -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ai-analyst-lab/ai-analyst history --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/history .claude/skills/history && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "history" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/history into .claude/skills/history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/historyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ai-analyst-lab/ai-analyst --skill history -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ai-analyst-lab/ai-analyst history --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/history .agents/skills/history && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "history" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/history into .agents/skills/history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ai-analyst-lab/ai-analyst --skill history -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ai-analyst-lab/ai-analyst history --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/history .cursor/skills/history && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "history" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/history into .cursor/skills/history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ai-analyst-lab/ai-analyst.git --path .claude/skills/history--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ai-analyst-lab/ai-analyst --skill history -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ai-analyst-lab/ai-analyst history --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/history .gemini/skills/history && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "history" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/history into .gemini/skills/history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ai-analyst-lab/ai-analyst historyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ai-analyst-lab/ai-analyst --skill history -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/history .github/skills/history && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "history" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/history into .github/skills/history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ai-analyst-lab/ai-analyst --skill history -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ai-analyst-lab/ai-analyst history --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/history .opencode/skills/history && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "history" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/history into .opencode/skills/history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
history- GitHub stars
- 304
- Token cost
- ~1.2k tokens
- SKILL.md length
- 515 words
- Files
- 1
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- MIT
At a glance
Browse and search past analyses from the knowledge system's analysis archive.
- Works in 4 steps: Load Archive → Determine Active Dataset (Critical) → Execute Command → …
- The user invokes /history
- SKILL.md covers Purpose, When to Use, Invocation and Instructions, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
History is an agent skill from ai-analyst-lab/ai-analyst. Browse and search past analyses from the knowledge system's analysis archive. Use this skill whenever the user invokes /history or variants like /history search=X, /history {id}, /history --all, /history dataset=X, or asks questions about their analytical work history such as "what have I analyzed before?", "what analyses have I run?", "show me past work", "show my history", "what have we looked at?", "what questions have I answered?", "can I see my analysis history?", "list my analyses", "what did I work on last…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: AI Product Analyst — Claude Code-powered data analysis toolkit. The licence is MIT.
When your agent uses it
- The user invokes /history
- Variants like /history search=X
- /history dataset=X
- Asks questions about their analytical work history such as what have I analyzed before?
Example prompts
- “what have I analyzed before?”
- “what analyses have I run?”
- “show me past work”
- “/history”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 52c0744. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
History loads about 1.2k tokens when it runs. Until then it costs about 251 tokens; SKILL.md has 515 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ai-analyst-lab/ai-analyst at commit 52c0744, republished under its MIT licence (© ai-analyst-lab). 515 words, ~1,169 tokens.
Download SKILL.mdSave it as
.claude/skills/history/SKILL.md (or your agent's skills folder).- name
- history
- description
- Browse and search past analyses from the knowledge system's analysis archive. Use this skill whenever the user invokes `/history` or variants like `/history search=X`, `/history {id}`, `/history --all`, `/history dataset=X`, or asks questions about their analytical work history such as "what have I analyzed before?", "what analyses have I run?", "show me past work", "show my history", "what have we looked at?", "what questions have I answered?", "can I see my analysis history?", "list my analyses", "what did I work on last week?", "have I analyzed X before?", "find analyses about Y", or mentions reviewing prior analyses, checking if similar work was already done, needing context on previous findings, or wants to build on past work. This skill also applies automatically at session start when you need context on the user's analytical history to inform current work. When displaying history, ALWAYS filter to the active dataset unless the user explicitly requests --all or dataset={id}.
Skill: History
Purpose
Browse and search past analyses from the analysis archive. Helps users recall what they've analyzed before, find prior findings, and build on previous work.
When to Use
- User says
/historyor "what have I analyzed before?" - At session start, to provide context on prior work
- When framing a new question, to check if similar analysis exists
Invocation
/history — list recent analyses (last 10)
/history {id} — show full details for a specific analysis
/history search={term} — search by title, question, or tags
/history --all — list all analyses across all datasets
/history dataset={id} — filter to a specific dataset
Instructions
Step 1: Load Archive
- Read
.knowledge/analyses/index.yaml - If empty: "No analyses archived yet. Complete an analysis and it will appear here."
Step 2: Determine Active Dataset (Critical)
IMPORTANT: Before filtering results, determine the active dataset:
- Read
.knowledge/active.yamlto get the active dataset ID - If
--allflag is present: skip filtering, show all datasets - If
dataset={id}is specified: filter to that dataset - Otherwise: filter to active dataset only
This ensures users see relevant analyses for their current working context by default.
Step 3: Execute Command
List recent (/history):
- Filter to active dataset (unless
--allflag present) - Sort by date descending
- Show last 10 as a table: date, title, level, key finding count, dataset
- Show total count: "Showing 10 of {total} analyses for {dataset_name}." (or "across all datasets" if --all)
Show specific (/history {id}):
- Find entry by ID in index
- Display: title, date, question, level, all key findings, metrics used, agents used, output files, tags, confidence, recommendations
- If output files exist, offer: "Want to review the full analysis? The deck is at {path}"
Search (/history search={term}):
- Filter to active dataset first (unless
--allordataset={id}specified) - Search across: title, question, key_findings, tags (case-insensitive)
- Display matching entries as a table
- If no matches: "No analyses match '{term}' in {dataset_name}. Try broader terms or use
--allto search across all datasets."
All datasets (/history --all):
- Include dataset_id column in output
- Sort by date descending across all datasets
Show full SKILL.md (178 more words)Show less
Step 4: Contextual Suggestions
After displaying history:
- "Want to re-run this analysis with fresh data?"
- "Want to build on finding #{n}?"
- If recent analysis was partial: "This analysis was incomplete. Resume with
/resume-pipeline."
Edge Cases
- No active dataset: Show all analyses or prompt to connect
- Archive file missing: Create empty index
- Analysis output files deleted: Note "output files no longer available"
- Very long history (>100): Paginate, show 20 at a time
Why This Matters
Dataset filtering ensures users see relevant analyses for their current working context. A user analyzing one dataset shouldn't see unrelated-dataset analyses by default — it creates noise and makes it harder to find relevant prior work. The --all flag is available when cross-dataset comparison is needed.
Contextual offers ("Want to review the full analysis?") help users take action on the information. Simply listing file paths isn't enough — explicitly offering next steps makes the history actionable.
Consistent table format allows quick scanning. Users browse history to find patterns, check if work was done before, or locate specific analyses. Tables are faster to scan than prose paragraphs.
© ai-analyst-lab, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/history of ai-analyst-lab/ai-analyst.
Open the folder on GitHubat commit 52c0744
Compare with similar skills
History next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| History this skillai-analyst-lab/ai-analyst | 304 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Browsing Historyglebis/claude-skills | 391 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Paste Inputsthedaviddias/Front-End-Checklist | 74k | — | ~443 | Automated safety check: Pass | MIT | |
| Browseyc-software/qm | 15k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Historyalsk1992/CloddsBot | 3k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Extracting Browser History Artifactsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.9k | Automated safety check: Warn | Apache-2.0 |
Similar skills
Paste Inputs
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Allow pasting into form inputs.
Browse
yc-software/qm
Drive a real stealth browser from your shell — act on websites (order food, file an expense, pull data behind a login), with per-person persistent sign-ins via the provider's managed auth (Kernel…
History
alsk1992/CloddsBot
Trade history tracking, sync, and performance analytics. An agent skill from alsk1992/CloddsBot.
Extracting Browser History Artifacts
mukul975/Anthropic-Cybersecurity-Skills
Extracts and analyzes browser history, cookies, cache, downloads, and bookmarks from Chrome, Firefox, and Edge using sqlite3, DB Browser for SQLite, Hindsight, and NirSoft tools…
System History
BuilderIO/agent-native
Blobless-safe git and PR history for this repo. An agent skill from BuilderIO/agent-native.
More from ai-analyst-lab/ai-analyst
All 43 skills in this repoAlways Compare
ai-analyst-lab/ai-analyst
Never present a metric or number in isolation; anchor every number to a comparison (prior period, benchmark, or another segment) or state that none is available.
Archaeology
ai-analyst-lab/ai-analyst
Retrieve proven SQL patterns, table cheatsheets, and join patterns from .knowledge/query-archaeology/ so past work gets reused.
Archive Analysis
ai-analyst-lab/ai-analyst
Save completed analyses to the knowledge system's analysis archive for future reference.
Auth Preflight
ai-analyst-lab/ai-analyst
Verify Google Workspace MCP authentication at the start of any session that needs Google APIs (Docs, Slides, Drive).
Causal
ai-analyst-lab/ai-analyst
Causal inference toolkit for when experiments are not possible: estimate treatment effects from observational data with assumption checks and mandatory caveats.
Chart To Drive
ai-analyst-lab/ai-analyst
Standardized workflow for uploading local chart PNGs to Google Drive and making them available for insertion into Google Docs and Slides.
Questions about History
What does History do?
Browse and search past analyses from the knowledge system's analysis archive. History is an agent skill from ai-analyst-lab/ai-analyst. Browse and search past analyses from the knowledge system's analysis archive.
When should I use History?
History fits situations like: the user invokes /history; variants like /history search=X; /history dataset=X; asks questions about their analytical work history such as what have I analyzed before?.
How do I install History in Claude Code?
Run `npx skills add ai-analyst-lab/ai-analyst --skill history -a claude-code`. Or copy the skill folder (.claude/skills/history in ai-analyst-lab/ai-analyst) into .claude/skills/history in your project. Claude Code loads it when a task matches its description.
How do I install History in Codex?
Run `npx skills add ai-analyst-lab/ai-analyst --skill history -a codex`. Or copy the skill folder (.claude/skills/history in ai-analyst-lab/ai-analyst) into .agents/skills/history in your project. Codex loads it when a task matches its description.
Can I use History in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ai-analyst-lab/ai-analyst --skill history -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/history, .gemini/skills/history, .github/skills/history and .opencode/skills/history in your project.
What does History need to run?
SKILL.md names no scripts, command-line tools or credentials: History is instructions for the agent only.
Does History access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is History safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does History use?
History is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does History use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to History?
Skills that share tags, products or a category with History: Browsing History (glebis/claude-skills, 391 stars), Paste Inputs (thedaviddias/Front-End-Checklist, 74k stars), Browse (yc-software/qm, 15k stars) and History (alsk1992/CloddsBot, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains History?
ai-analyst-lab (a GitHub organization) maintains it in ai-analyst-lab/ai-analyst, which has 304 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on September 30, 2026.
Source: ai-analyst-lab/ai-analyst on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.