CHAT—Logger
v1.0.1Automatically logs every conversation message to workspace/chat/YYYY-MM-DD.md. Creates new files if needed, always appends never overwrites.
⭐ 0· 233·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (daily append-only logging) align with the SKILL.md. No extra binaries, credentials, or config paths are requested that would be unrelated to simple filesystem logging.
Instruction Scope
Instructions are narrowly scoped to creating a chat/ directory and appending timestamped entries to daily Markdown files using Node.js fs APIs. One practical note: the sample code uses process.cwd() as the workspace, so the agent will write to its current working directory unless an explicit workspace path is provided — this is expected but worth being deliberate about to avoid writing logs to an unexpected location.
Install Mechanism
No install spec or external downloads; instruction-only skill that relies on built-in Node.js modules. Lowest-risk installation footprint.
Credentials
No environment variables, credentials, or config paths are required. The requested filesystem write access (workspace) is proportionate to the stated logging purpose.
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform privileges. It only describes writing files under the workspace, which is consistent with its purpose.
Assessment
This skill appears to do exactly what it says: append conversation turns to daily Markdown files under workspace/chat. Before using it, decide and configure where 'workspace' should be (avoid ambiguous process.cwd()), restrict filesystem permissions for the chat directory, and consider privacy: logs may contain sensitive information or secrets from conversations. Implement retention/rotation, encryption, or opt-out for sensitive messages if needed. Because this is an instruction-only skill, it won't run unless the agent or runtime implements the logging steps — review any agent code that performs the actual writes to ensure it follows the append-only behavior and writes only to the intended path.Like a lobster shell, security has layers — review code before you run it.
latestvk971g7txbg7x788jv8g3epjyq982f1zf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.