New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

History Insight

by team-attention in team-attention/plugins-for-claude-natives

This skill should be used when user wants to access, capture, or reference Claude Code session history.

MITAuto-check passed

Install History Insight

skills CLI
$ npx skills add team-attention/plugins-for-claude-natives --skill history-insight -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install team-attention/plugins-for-claude-natives history-insight --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/session-wrap/skills/history-insight .claude/skills/history-insight && rm -rf skills-src

Use ~/.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/

Facts

Skill name
history-insight
GitHub stars
827
Token cost
~834 tokens
SKILL.md length
224 words
Files
3 (incl. scripts, references)
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when user wants to access, capture, or reference Claude Code session history.

  • Works in 4 steps: Ask Scope [MANDATORY] → Find Session Files → Process Sessions → …
  • Wants to access
  • SKILL.md covers Data Location, Execution Algorithm, Error Handling and Security Notes, plus 1 more section
  • Runs Shell scripts from its folder

What it does

History Insight is an agent skill from team-attention/plugins-for-claude-natives. This skill should be used when user wants to access, capture, or reference Claude Code session history. Trigger when user says "capture session", "save session history", or references past/current conversation as a source - whether for saving, extracting, summarizing, or reviewing. This includes any mention of "what we discussed", "today's work", "session history", or when user treats the conversation itself as source material (e.g., "from our conversation").

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/session-file-format.md` and `scripts/extract-session.sh`).

The repository describes itself as: Claude Code plugins for power users. The licence is MIT.

When your agent uses it

  • Wants to access
  • Reference Claude Code session history
  • User says capture session
  • Save session history

Example prompts

  • “capture session”
  • “save session history”
  • “what we discussed”
  • “/history-insight”

Requirements

  • A Bash shell

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Ask Scope [MANDATORY]
  2. Find Session Files
  3. Process Sessions
  4. Report Results

What it can do on your machine

Read from SKILL.md and the folder at commit fd9c207. 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

    Ships 1 file in scripts/ (Shell), which the agent can run.

    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 Insight loads about 834 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 120 tokens; SKILL.md has 224 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~120
When it runs · the whole SKILL.md, loaded when a task matches
~834
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from team-attention/plugins-for-claude-natives at commit fd9c207, republished under its MIT licence (© team-attention). 224 words, ~834 tokens.

Download SKILL.mdSave it as .claude/skills/history-insight/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
history-insight
description
This skill should be used when user wants to access, capture, or reference Claude Code session history. Trigger when user says "capture session", "save session history", or references past/current conversation as a source - whether for saving, extracting, summarizing, or reviewing. This includes any mention of "what we discussed", "today's work", "session history", or when user treats the conversation itself as source material (e.g., "from our conversation").
version
1.1.0
user-invocable
true

History Insight

Claude Code 세션 히스토리를 분석하고 인사이트를 추출합니다.

Data Location

~/.claude/projects/<encoded-cwd>/*.jsonl

Path Encoding: /Users/foo/project → -Users-foo-project

상세 파일 포맷: ${baseDir}/references/session-file-format.md

Execution Algorithm

Step 1: Ask Scope [MANDATORY]

스코프 결정:

  1. 명시된 경우 (AskUserQuestion 생략 가능):

    • "현재 프로젝트만" / "이 프로젝트" → current_project
    • "모든 세션" / "전체" → all_sessions

  2. 명시되지 않은 경우 - AskUserQuestion 호출:

    question: "세션 검색 범위를 선택하세요"
options:
  - "현재 프로젝트만" → ~/.claude/projects/<encoded-cwd>/*.jsonl
  - "모든 Claude Code 세션" → ~/.claude/projects/**/*.jsonl
Step 2: Find Session Files
bash
# Current project only
find ~/.claude/projects/<encoded-cwd> -name "*.jsonl" -type f

# All sessions (모든 프로젝트)
find ~/.claude/projects -name "*.jsonl" -type f

날짜 필터링: 파일의 mtime(수정시간) 확인 후 필터. OS별 stat 옵션 다름:

  • macOS: stat -f "%Sm" -t "%Y-%m-%d" <file>
  • Linux: stat -c "%y" <file>
Step 3: Process Sessions
Decision Tree
Session files found?
├─ No → Error: "No sessions found"
└─ Yes → How many files?
    ├─ 1-3 files → Direct Read + parse
    └─ 4+ files → Batch Extract Pipeline
1-3 Files

직접 Read로 JSONL 파싱. 파일이 크면(≥5000 tokens) extract-session.sh 사용:

bash
${baseDir}/scripts/extract-session.sh <session.jsonl>
4+ Files: Batch Extract Pipeline
  1. 캐시 디렉토리 생성 (/tmp/cc-cache/<analysis-name>/)
  2. 세션 목록 저장 (sessions.txt)
  3. jq로 메시지 일괄 추출 (user_messages.txt)
  4. 정리 및 필터링 (clean_messages.txt)
  5. Task(opus)로 종합 분석
파일이 너무 클 때: 병렬 배치 분석

clean_messages.txt가 너무 커서 Read 실패 시:

  1. 파일 분할:

    bash
    split -l 2000 clean_messages.txt /tmp/cc-cache/<name>/batch_

  2. 병렬 Task(opus) 호출:

    Task(subagent_type="general-purpose", model="opus", run_in_background=true)
prompt: "batch_XX 파일을 읽고 주제/패턴 요약해줘"

  3. 결과 병합: Task(opus)로 종합

Step 4: Report Results
markdown
## Session Capture Complete

- **Sessions:** N files processed
- **Messages:** X total, Y after filter

### Extracted Insights
[분석 결과]

Error Handling

ScenarioResponse
No session files found"No session files found for this project."
File too largeAuto-preprocess with extract-session.sh
jq not installed"Error: jq is required. Install with: brew install jq"
Task failed"Warning: Could not process [file]. Skipping."
0 relevant sessions"No sessions matched your criteria."

Security Notes

  • 출력에 전체 경로 노출 금지 (~ prefix 사용)
  • ${baseDir}/scripts/extract-session.sh - JSONL 압축 (thinking, tool_use 제거)
  • ${baseDir}/references/session-file-format.md - JSONL 구조 및 파싱

© team-attention, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts, references) in plugins/session-wrap/skills/history-insight of team-attention/plugins-for-claude-natives.

  • SKILL.md
  • references/session-file-format.md
  • scripts/extract-session.sh

Open the folder on GitHubat commit fd9c207

Compare with similar skills

History Insight 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.

History Insight compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
History Insight this skillteam-attention/plugins-for-claude-natives827—~834Automated safety check: PassMIT
Formatting Insight AxesPostHog/posthog40k—~2.1kAutomated safety check: PassCustom licence
Insight Error Pagevercel/next.js143k—~5.5kAutomated safety check: PassMIT
Historyalsk1992/CloddsBot3k—~1.6kAutomated safety check: PassMIT
Insightsrohitg00/pro-workflow2.9k—~719Automated safety check: PassNone
Creating Box Plot InsightsPostHog/posthog40k—~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Formatting Insight Axes

    PostHog/posthog

    Official

    Pick the right y-axis unit when creating or updating an insight via posthog:insight-create or posthog:insight-update — both TrendsQuery (trendsFilter.aggregationAxisFormat) and SQL insights…

    40k GitHub stars~2.1k tokensUpdated yesterday
    DatabasesAuto-check passed

  • Insight Error Page

    vercel/next.js

    Official

    Write or audit an insight-kind error page for the Next.js dev overlay.

    143k GitHub stars~5.5k tokensUpdated today
    Writing & ContentAuto-check passed

  • History

    alsk1992/CloddsBot

    Trade history tracking, sync, and performance analytics. An agent skill from alsk1992/CloddsBot.

    3k GitHub stars~1.6k tokensUpdated 8 days ago
    Auto-check passed

  • Insights

    rohitg00/pro-workflow

    Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics.

    2.9k GitHub stars~719 tokensUpdated 12 days ago
    Agent WorkflowsAuto-check passed

  • Creating Box Plot Insights

    PostHog/posthog

    Official

    Creates product analytics or SQL-backed box plot insights in PostHog.

    40k GitHub stars~1.1k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed

  • Signals Scout Insight Alerts

    PostHog/posthog

    Official

    Signals scout over the project's configured insight alerts. An agent skill from PostHog/posthog.

    40k GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed

More from team-attention/plugins-for-claude-natives

All 16 skills in this repo

  • Gmail

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "check email", "read emails", "send email", "reply to email", "search inbox", or manages Gmail.

    827 GitHub stars~967 tokensUpdated 5 mo ago
    Auto-check passed

  • Session Analyzer

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants…

    827 GitHub stars~1.8k tokensUpdated 5 mo ago
    Auto-check passed

  • Youtube Digest

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "유튜브 정리", "영상 요약", "transcript 번역", "YouTube digest", "영상 퀴즈", or provides a YouTube URL for analysis.

    827 GitHub stars~557 tokensUpdated 5 mo ago
    Auto-check passed

  • Tech Decision

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야 할지", "트레이드오프", "기술 선택", "구현 방식 고민", or needs deep analysis for technical…

    827 GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed

  • Fetch Tweet

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "트윗 가져와", "트윗 번역", "X 게시글 읽어줘", "tweet fetch", "트윗 내용", "트윗 원문", or provides an X/Twitter URL (x.com, twitter.com) and wants to read, translate, or…

    827 GitHub stars~518 tokensUpdated 5 mo ago
    Auto-check passed

  • Podcast

    team-attention/plugins-for-claude-natives

    Generate Korean podcast episodes from any source (URLs, tweets, articles, PDFs) — analyzes content, writes a script, generates audio via OpenAI TTS, converts to MP4, and auto-uploads to YouTube.

    827 GitHub stars~1.5k tokensUpdated 5 mo ago
    Auto-check passed

Questions about History Insight

What does History Insight do?

This skill should be used when user wants to access, capture, or reference Claude Code session history. History Insight is an agent skill from team-attention/plugins-for-claude-natives. This skill should be used when user wants to access, capture, or reference Claude Code session history.

When should I use History Insight?

History Insight fits situations like: wants to access; reference Claude Code session history; user says capture session; save session history.

How do I install History Insight in Claude Code?

Run `npx skills add team-attention/plugins-for-claude-natives --skill history-insight -a claude-code`. Or copy the skill folder (plugins/session-wrap/skills/history-insight in team-attention/plugins-for-claude-natives) into .claude/skills/history-insight in your project. Claude Code loads it when a task matches its description.

How do I install History Insight in Codex?

Run `npx skills add team-attention/plugins-for-claude-natives --skill history-insight -a codex`. Or copy the skill folder (plugins/session-wrap/skills/history-insight in team-attention/plugins-for-claude-natives) into .agents/skills/history-insight in your project. Codex loads it when a task matches its description.

Can I use History Insight 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 team-attention/plugins-for-claude-natives --skill history-insight -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-insight, .gemini/skills/history-insight, .github/skills/history-insight and .opencode/skills/history-insight in your project.

What does History Insight need to run?

Going by SKILL.md and its folder, History Insight needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does History Insight 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 Insight 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does History Insight use?

History Insight 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 Insight use?

About 834 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 489 tokens, read only when the agent opens those files.

What are the alternatives to History Insight?

Skills that share tags, products or a category with History Insight: Formatting Insight Axes (PostHog/posthog, 40k stars), Insight Error Page (vercel/next.js, 143k stars), History (alsk1992/CloddsBot, 3k stars) and Insights (rohitg00/pro-workflow, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains History Insight?

team-attention (a GitHub organization) maintains it in team-attention/plugins-for-claude-natives, which has 827 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on April 20, 2026.

Source: team-attention/plugins-for-claude-natives on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.