Skip to content
TrustedSkillsbeta
Back to all skills

Session Logger

Checked
charon-fan·vlatest·security·MIT

This Session Logger tracks user interactions within a session for analysis and debugging, improving application understanding & troubleshooting.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add zhaono1/agent-playbook --skill session-logger -a claude-code

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

charon-fan

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

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    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 charon-fan/agent-playbook at be7a9d7d17.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
be7a9d7d17
Manifest
skills/session-logger/SKILL.md
Scanned
2 files, 91 lines
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

The session-logger skill enables AI agents to automatically record and track user interactions within a specific session. It captures detailed logs of activities, timestamps, and context to provide a complete history of the agent's performance during that interaction window.

When to use it

  • Audit complex multi-step workflows to verify every action taken by the agent.
  • Debug issues by reviewing exactly what occurred during a failed task execution.
  • Generate compliance reports requiring proof of specific user interactions or data access.
  • Analyze session duration and activity patterns to optimize future agent responses.

Key capabilities

  • Automatic recording of all actions taken within the current session context.
  • Timestamped logging of events for precise timeline reconstruction.
  • Preservation of interaction history for post-session analysis.

Example prompts

  • "Start a new session and log every step you take while setting up the project environment."
  • "Before we begin troubleshooting, please enable session logging so I can review your actions later."
  • "Log this entire debugging session including all error messages and commands executed."

Tips & gotchas

Ensure the agent has permission to write logs before initiating complex tasks that require auditing. Session data is typically ephemeral; retrieve or export logs immediately after a task concludes if long-term storage isn't configured.