clawsec-session

Scans OpenClaw session logs and directories for insecure world-readable permissions using bash commands.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/4e696b6f/clawsec-agent --skill clawsec-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clawsec-session
Source: https://github.com/4e696b6f/clawsec-agent/tree/main/skills/clawsec-session
Command: npx skills add https://github.com/4e696b6f/clawsec-agent --skill clawsec-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses potential security vulnerabilities in how session data and logs are stored, ensuring that sensitive conversation histories and memory stores are not inadvertently exposed.

Core Features & Use Cases

  • Session Log Permissions Check: Verifies that session log files (.jsonl) are not world-readable.
  • Session Directory Permissions Check: Ensures that directories containing session data are not world-readable.
  • Use Case: Protects against unauthorized access to user conversation histories stored in session files by identifying and flagging permission misconfigurations.

Quick Start

Scan for world-readable session log files and directories.

Frequently Asked Questions about clawsec-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if session log files are world-readable?

Session log files containing .jsonl conversation histories pose data privacy risks if stored with world-readable permissions. Scanning directory and file metadata prevents sensitive data disclosure by flagging unauthorized access to OpenClaw memory stores and conversation history.

How do I prevent unauthorized access to OpenClaw session data?

You prevent unauthorized access to OpenClaw session data by scanning for world-readable directories and .jsonl log files. Checking file metadata using bash commands flags permission misconfigurations that expose conversation histories and memory stores to data disclosure risks.

Does checking log permissions require any external dependencies?

Checking log permissions requires no external dependencies. The scan applies standard bash commands to inspect file metadata and directory permissions for OpenClaw session data, ensuring memory stores and conversation history remain secure against disclosure.

What is the best way to secure conversation history stored in .jsonl files?

Securing conversation history in .jsonl files requires verifying that session directories and log files are not world-readable. Scanning file metadata and directory permissions using bash commands prevents sensitive data disclosure from OpenClaw session data and memory stores.

What permissions should session directories have to avoid data privacy issues?

Session directories should not be world-readable to avoid data privacy issues. Scanning directory and file metadata verifies that .jsonl session logs and memory stores are configured securely, preventing sensitive conversation history exposure and data disclosure.