Skip to content
TrustedSkillsbeta
Back to all skills

Session Export

Checked
ajoslin·vlatest·security

This skill exports a user’s entire session data for debugging or analysis, streamlining troubleshooting and understanding user behavior.

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 ajoslin/dot --skill session-export -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

ajoslin

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 ajoslin/dot at 8aa8e87ab2.

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

Scanned
1 file, 129 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

What it does

The session-export skill allows AI agents to export a user's current session data. This includes information like browsing history, form entries, and other interactive elements within the session. The exported data can be saved locally or shared with others for review or backup purposes.

When to use it

  • Troubleshooting: Exporting a session allows developers to examine user interactions in detail when debugging issues.
  • Data Recovery: Users can recover lost data from a previous session by exporting and re-importing the information.
  • Sharing workflows: A user could export their session to share their progress with a colleague or demonstrate a specific workflow.
  • Compliance/Auditing: Exported sessions can be used for audit trails or compliance requirements related to user activity.

Key capabilities

  • Session data extraction
  • Local file saving
  • Data sharing (potential, not explicitly stated)

Example prompts

  • "Export my current session as a JSON file."
  • "Save this browsing history to a local file."
  • “Can you create an archive of what I’ve been doing?”

Tips & gotchas

The format of the exported data is not specified, so be prepared for potential parsing or interpretation challenges depending on the application. Consider that large sessions may result in substantial export file sizes.