Agent skill

Session Log

Create a timestamped research-session progress log that records completed work, evidence, decisions, and next steps.

MITAuto-check passed

Install Session Log

skills CLI

$ npx skills add flonat/flonat-research --skill session-log -a claude-code

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

GitHub CLI

$ gh skill install flonat/flonat-research session-log --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/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/session-log .claude/skills/session-log && 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/

Paste into Claude Code

Install the "session-log" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/session-log into .claude/skills/session-log/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-log", 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

$skill-installer install https://github.com/flonat/flonat-research/tree/main/skills/session-log

Type 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.

skills CLI

$ npx skills add flonat/flonat-research --skill session-log -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research session-log --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/session-log .agents/skills/session-log && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "session-log" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/session-log into .agents/skills/session-log/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-log", 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.

skills CLI

$ npx skills add flonat/flonat-research --skill session-log -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research session-log --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/session-log .cursor/skills/session-log && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "session-log" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/session-log into .cursor/skills/session-log/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-log", 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

$ gemini skills install https://github.com/flonat/flonat-research.git --path skills/session-log

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add flonat/flonat-research --skill session-log -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research session-log --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/session-log .gemini/skills/session-log && rm -rf skills-src

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

Paste into Gemini CLI

Install the "session-log" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/session-log into .gemini/skills/session-log/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-log", 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.

GitHub CLI

$ gh skill install flonat/flonat-research session-log

Installs 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).

skills CLI

$ npx skills add flonat/flonat-research --skill session-log -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/session-log .github/skills/session-log && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "session-log" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/session-log into .github/skills/session-log/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-log", 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.

skills CLI

$ npx skills add flonat/flonat-research --skill session-log -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research session-log --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/session-log .opencode/skills/session-log && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "session-log" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/session-log into .opencode/skills/session-log/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-log", 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: session-log
GitHub stars: 145
Token cost: ~916 tokens
SKILL.md length: 385 words
Files: 1
Skills in repo: 83
Repo updated: Sep 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create a timestamped research-session progress log that records completed work, evidence, decisions, and next steps.

Works in 4 steps: Identify Projects Touched → Create One Log Per Project → Cross-Reference → …
Checkpointing substantive project work that needs a durable chronology
SKILL.md covers Purpose, When to Use, Workflow and Log Template, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Session Log is an agent skill from flonat/flonat-research. Create a timestamped research-session progress log that records completed work, evidence, decisions, and next steps. Use when closing or checkpointing substantive project work that needs a durable chronology. Not for saving one reusable finding; use $store-insight.

Its SKILL.md is about 920 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: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

Checkpointing substantive project work that needs a durable chronology

Example prompts

“/session-log”

Requirements

Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(mkdir*), Bash(ls*)

Workflow steps

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

Identify Projects Touched
Create One Log Per Project
Cross-Reference
Offer Follow-Up

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Edit
- Bash(mkdir*)
- Bash(ls*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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

Session Log loads about 916 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 385 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~69
When it runs · the whole SKILL.md, loaded when a task matches: ~916

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 flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 385 words, ~916 tokens.

Download SKILL.mdSave it as .claude/skills/session-log/SKILL.md (or your agent's skills folder).

name: session-log
description: Create a timestamped research-session progress log that records completed work, evidence, decisions, and next steps. Use when closing or checkpointing substantive project work that needs a durable chronology. Not for saving one reusable finding; use $store-insight.
allowed-tools: Read, Write, Edit, Bash(mkdir*), Bash(ls*)
argument-hint: [project-name-or-path]
skill-dependencies: update-focus

Session Log Skill

Automatically create timestamped progress logs for research sessions.

Purpose

Based on Scott Cunningham's session workflow: “Progress logs are my autosave of the workflow.” When sessions end or crash, the next AI client can read logs and pick up exactly where you left off.

When to Use

At the end of any significant work session, or when asked to "log this session" or "update progress".

Workflow

Step 1: Identify Projects Touched

Before writing anything, inventory which projects were affected during this session. A "project" is any directory with its own CLAUDE.md or log/ directory. Common splits:

Scope	Where the log goes
Work inside a specific project	That project's `log/`
Global infrastructure (skills, hooks, rules, settings)	Task Management's `log/`
Course/module-level changes (reorganisation, new CLAUDE.md)	That module's `log/`

Signs of a multi-project session:

Files changed in AI client infrastructure (skills, hooks, settings) → global/infrastructure log
Files changed in the CWD project → project-specific log
Files changed in a parent or sibling directory → check if that's a separate project

Step 2: Create One Log Per Project

For each project identified in Step 1:

Read existing context — check that project's .context/current-focus.md and recent log/ entries
Create log/ directory if it doesn't exist
Write the log to log/YYYY-MM-DD-HHMM.md within that project
Scope the content — each log only covers what happened in that project, not the whole session

If there's only one project, this reduces to a single log (the common case).

Show full SKILL.md (145 more words)Show less

Step 3: Cross-Reference

When multiple logs are created, add a brief cross-reference at the top of each:

markdown

> Also logged: [other project name] — `[relative or absolute path to other log]`

This lets a future session in one project discover that related work happened elsewhere.

Step 4: Offer Follow-Up

Offer to run update-focus for a structured update (session rotation, open loops), rather than making ad-hoc edits to current-focus.md
If multiple projects were touched, offer to update focus for each

Log Template

markdown

# Session Log: [Date] [Time]

## Project: [Project Name]

## What We Did
- [Bullet points of accomplishments]

## Key Decisions
- [Any choices made and why]

## Problems/Blockers
- [Issues encountered]

## Next Steps
- [ ] [Actionable next items]

## Files Changed
- [List of modified files — only those in THIS project]

Examples

Single-project session

"Please log this session — we worked on the research paper, fixed the simulation code, and decided to target Journal B instead of Journal A."

→ One log in the MCDM project's log/

Multi-project session

"Please log this session — we did Workshop 17, reorganised the module folder, and created two new global skills."

→ Three logs:

Module project log/ — workshop completion, reorganisation, CLAUDE.md creation
Task Management log/ — new skills (init-project-course, audit-project-course), new hook (ensure-latexmkrc.sh), settings.json changes

Files

Just SKILL.md in skills/session-log of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Session Log 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.

Session Log compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Session Log this skillflonat/flonat-research	145	—	~916	Automated safety check: Pass	MIT	8 days ago
Recordingcodewhale-hq/Codewhale	41k	—	~540	Automated safety check: Pass	MIT	today
Growth Logaffaan-m/ECC	274k	1 repos	~1.7k	Automated safety check: Pass	MIT	2 days ago
Audit Logsickn33/agentic-awesome-skills	47k	1 repos	~3.6k	Automated safety check: Pass	MIT	yesterday
Architecture Decision Recordsaffaan-m/ECC	274k	4 repos	~1.8k	Automated safety check: Pass	MIT	2 days ago
Architecture Decision Recordsaffaan-m/ECC	274k	1 repos	~863	Automated safety check: Pass	MIT	2 days ago

Similar skills

Recording
codewhale-hq/Codewhale
Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures.
41k GitHub stars~540 tokensUpdated today
Productivity & AutomationAuto-check passed
Growth Log
affaan-m/ECC
Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence…
274k GitHub starsUsed in 1 repo~1.7k tokens
DevelopmentAuto-check passed
Audit Log
sickn33/agentic-awesome-skills
Audit trail register: timestamp, user, module, record, action, field changed, old and new value, and the reason for the change.
47k GitHub starsUsed in 1 repo~3.6k tokens
Auto-check passed
Architecture Decision Records
affaan-m/ECC
Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README.
274k GitHub starsUsed in 4 repos~1.8k tokens
DevelopmentAuto-check passed
Architecture Decision Records
affaan-m/ECC
在Claude Code会话期间，将做出的架构决策捕获为结构化的架构决策记录（ADR）。自动检测决策时刻，记录上下文、考虑的替代方案和理由。维护一个ADR日志，以便未来的开发人员理解代码库为何以当前方式构建。
274k GitHub starsUsed in 1 repo~863 tokens
DevelopmentAuto-check passed
Architecture Decision Records
affaan-m/ECC
コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。
274k GitHub stars~1.1k tokensUpdated 2 days ago
DevelopmentAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo

Latex Posters
flonat/flonat-research
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.
145 GitHub stars~1.5k tokensUpdated 8 days ago
Auto-check: notes
Skill Creator
flonat/flonat-research
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.
145 GitHub stars~4.4k tokensUpdated 8 days ago
Auto-check passed
DOCX
flonat/flonat-research
Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.
145 GitHub stars~1.2k tokensUpdated 8 days ago
Auto-check passed
PDF
flonat/flonat-research
Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.
145 GitHub stars~488 tokensUpdated 8 days ago
Auto-check passed
Init Project Orchestration
flonat/flonat-research
Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.
145 GitHub stars~1.6k tokensUpdated 8 days ago
Auto-check passed
Pre Commit Audit
flonat/flonat-research
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.
145 GitHub stars~2.8k tokensUpdated 8 days ago
Auto-check: notes

Questions about Session Log

What does Session Log do?

Create a timestamped research-session progress log that records completed work, evidence, decisions, and next steps. Session Log is an agent skill from flonat/flonat-research. Create a timestamped research-session progress log that records completed work, evidence, decisions, and next steps.

When should I use Session Log?

Session Log fits situations like: checkpointing substantive project work that needs a durable chronology.

How do I install Session Log in Claude Code?

Run `npx skills add flonat/flonat-research --skill session-log -a claude-code`. Or copy the skill folder (skills/session-log in flonat/flonat-research) into .claude/skills/session-log in your project. Claude Code loads it when a task matches its description.

How do I install Session Log in Codex?

Run `npx skills add flonat/flonat-research --skill session-log -a codex`. Or copy the skill folder (skills/session-log in flonat/flonat-research) into .agents/skills/session-log in your project. Codex loads it when a task matches its description.

Can I use Session Log 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 flonat/flonat-research --skill session-log -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/session-log, .gemini/skills/session-log, .github/skills/session-log and .opencode/skills/session-log in your project.

What does Session Log need to run?

SKILL.md names no scripts, command-line tools or credentials: Session Log is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(mkdir*), Bash(ls*).

Does Session Log 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 Session Log 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 Session Log use?

Session Log 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 Session Log use?

About 916 tokens (SKILL.md is roughly 3.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 Session Log?

Skills that share tags, products or a category with Session Log: Recording (codewhale-hq/Codewhale, 41k stars), Growth Log (affaan-m/ECC, 274k stars), Audit Log (sickn33/agentic-awesome-skills, 47k stars) and Architecture Decision Records (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Session Log?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Session Log

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Session Log Skill

Purpose

When to Use

Workflow

Step 1: Identify Projects Touched

Step 2: Create One Log Per Project

Step 3: Cross-Reference

Step 4: Offer Follow-Up

Log Template

Examples

Single-project session

Multi-project session

Files

Compare with similar skills

Similar skills

More from flonat/flonat-research

Questions about Session Log