session-log
Skill198 starsChanged 8 months agoMITView on GitHub
Inspect prove_it session logs—review history, reviewer verdicts, and session state. Use when asked about session logs, reviewer results, or "what did the last hook say".
19 other projects use a version of this.
Adopted by
Most recently taken up by
- flonat/flonat-researchtheir own version, first seen Nov 3, 2026
- AN0099/toothpaste-kittheir own version, first seen Oct 24, 2026
- sunnysxg/claude_skillstheir own version, first seen Oct 20, 2026
- tderoussel/agent-skillstheir own version, first seen Oct 20, 2026
- jacobgreenwald21/claude-skillstheir own version, first seen Oct 15, 2026
- gufranco/claude-engineering-rulestheir own version, first seen Oct 12, 2026
Used with
Projects with it also use ml-training-recipe, replication and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
getcompanion-aiSkillml-training-recipe
Find implementable ML training recipes from papers, datasets, docs, and code. Use when the user wants to fine-tune, train, reproduce, or choose a practical ML method, dataset, hyperparameter setup, or benchmark recipe.
Also in 3 projects that use this
getcompanion-aiSkillreplication
Plan a replication of a paper, claim, or benchmark, and execute only after an explicit environment choice. Use when the user asks to replicate results, reproduce an experiment, verify a claim empirically, or build a replication package.
Also in 3 projects that use this
brainbytes-devSkillalpha-research
Also in 3 projects that use this
JaimeParkerSkillpaper-code-audit
Perform three-way cross-validation of a research paper by comparing the original paper text (via Zotero), official code implementation (via Git), and personal Obsidian notes. Use this skill whenever the user wants to "audit a paper", "verify paper claims against code", "cross-check notes with implementation", "triangulate paper + code + notes", "find discrepancies between paper and code", or mentions wanting a deep, structured comparison of a paper's claims against its implementation and their own notes. Also trigger when the user asks to "analyze this paper thoroughly" with code available, or when they want to systematically reconcile what the paper says, what the code does, and what their notes claim.
Also in 3 projects that use this
JimLiuSkillpdf-explore
Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.
Also in 3 projects that use this
KISHOR403Skillsession-search
This skill should be used when searching Claude Code session transcripts with semantic understanding. Triggers on queries like "find sessions about X", "when did I work on Y", "search previous conversations". Supports natural language queries with synonym matching.
Also in 4 projects that use this
- +1 more from getcompanion-ai
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- getcompanion-ai/feynman★ 10ksame name
- advaitpaliwal/feynman★ 10ksame name
- companion-inc/feynman★ 10ksame name
- michalparkola/tapestry-skills-for-claude-code★ 557same name
- michalparkola/tapestry-skills★ 538same name
- flonat/flonat-research★ 150same name
- Felpix-Studios/social-science-research★ 8same name
- cyberfly/agent-skills★ 3same name
- gufranco/claude-engineering-rules★ 3same name
- AN0099/toothpaste-kit★ 1same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- prove-featureSkill
- releaseSkill
- test-localSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Read it and display each entry as a table or formatted list showing:
- Very specific: line 35
Read <session_id>.jsonl and <session_id>.json and display both the session state and reviewer entries.
- Distinctive: line 49
Use the reviewer name as-is (e.g., "coverage-review", "fast-tests")
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Inspect prove_it session logs
Session data lives in ~/.claude/prove_it/sessions/. Two file types per session:
<session_id>.json—session state (project dir, git HEAD, started_at)<session_id>.jsonl—reviewer log (one JSON object per line: at, reviewer, status, reason, projectDir, sessionId)_project_<hash>.jsonl—project-level reviewer log (when session_id was null)
Determine the current session ID
The current Claude Code session ID is passed in hook input. To find it for the active conversation, check the most recently modified .jsonl file:
ls -t ~/.claude/prove_it/sessions/*.jsonl | head -5What to show
Default (no args): show the current session's reviewer log
- Find the most recently modified
.jsonlfile (excluding_project_*andtest-session*files). - Read it and display each entry as a table or formatted list showing:
- Time (human-readable from the
attimestamp) - Reviewer name
- Status (PASS/FAIL/SKIP/BOOM)
- Reason (the reviewer's rationale)
- Time (human-readable from the
With a session ID arg: show that specific session
Read <session_id>.jsonl and <session_id>.json and display both the session state and reviewer entries.
With --all or all: list all sessions
List all session .json files sorted by modification time, showing session ID, project, and started_at.
With --stats or stats: aggregate reviewer stats
Count PASS/FAIL/SKIP/BOOM across all .jsonl files and show totals.
Formatting
- Show timestamps as relative times (e.g., "2 min ago") or HH:MM:SS
- Truncate long reasons to ~120 chars in table view, show full text if only one session
- Use the reviewer name as-is (e.g., "coverage-review", "fast-tests")
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.

