Session Log

Name: Session Log
Author: simhacker

Listed

simhacker·vlatest·security·MIT

This skill extracts and displays detailed session logs for analysis, aiding in troubleshooting and understanding user behavior.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add simhacker/moollm --skill session-log -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

simhacker

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 30 Sept 2026

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

Declares what it does: failed
No SKILL.md was found in the skill's directory.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned simhacker/moollm at 8f6d840b2f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 8f6d840b2f
Manifest: skills/session-log/SKILL.md
Scanned: 0 files

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill, session-log, allows an AI agent to record and manage a history of its interactions. It provides the ability to store prompts, responses, and other relevant data from each session. This logged information can then be reviewed or used for analysis and debugging purposes.

When to use it

Debugging Agent Behavior: Review past conversations to understand why an agent made certain decisions or encountered issues.
Tracking Progress in Complex Tasks: Log steps taken during a multi-stage process, allowing you to reconstruct the workflow later.
Analyzing User Interactions: Gain insights into user behavior and preferences by examining logged prompts and responses.
Reproducing Specific Scenarios: Recreate past interactions for testing or demonstration purposes.

Key capabilities

Session recording
Prompt storage
Response storage
Session management

Example prompts

"Start a new session."
"Show me the last 3 sessions."
"Log this interaction: [prompt] - [response]"

Tips & gotchas

The effectiveness of session-log depends on the underlying agent's ability to accurately capture and store data. Ensure that the agent is configured to properly utilize the skill’s logging features for optimal results.