skills.rest
MDGrey33
MDGrey33COMMUNITY
Explore all skills by this author →
WebsiteGitHub

log

Append structured agent log entries with run IDs and rotate to 200 rows.

2|Updated Feb 23, 2026
Search Tags:#logging#claude code#session management#workspace#audit trail#rotation
One-click install
npx skills add https://github.com/MDGrey33/memnyx --skill log-mdgrey33
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: log
Source: https://github.com/MDGrey33/memnyx/tree/main/.claude/skills/log
Command: npx skills add https://github.com/MDGrey33/memnyx --skill log-mdgrey33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents fragmented, inconsistent agent logging by giving every skill and agent a single, structured place to record run outcomes, details, and timestamps.

Core Features & Use Cases

  • Structured append-only logging: Writes each run as a timestamped table row with run ID, skill name, status, and detail.
  • Automatic rotation: Keeps the log bounded by trimming the oldest entries after the file exceeds 200 data rows.
  • Shared utility for other skills: Centralizes log formatting and file management so other skills do not write directly to the log.
  • Use case: A workspace maintenance skill can record a successful sync, while a failed setup can log its error reason without duplicating logging logic.

Quick Start

Use the log skill to append a structured entry for the current run with the appropriate status and a concise detail message.

Frequently Asked Questions about log

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

FAQPage Schema
How do I keep Claude Code session logs from cluttering my workspace?▼

Workspace session logs are kept bounded by applying automatic rotation to the appended entries. The log is automatically trimmed after it exceeds 200 data rows, removing the oldest entries first.

What is the best way to maintain an audit trail for automated skill runs?▼

An audit trail for automated skill runs is maintained by appending structured table rows to a centralized memory log. Each row captures the run ID, skill name, status, and timestamp for consistent tracking.

How do I structure agent log entries for multiple workspace sessions?▼

Agent log entries are structured as timestamped table rows appended to a single memory log. This centralizes log formatting so other skills record run outcomes without duplicating logging logic.

Does the log rotation process delete historical workspace session data?▼

Log rotation deletes only the oldest historical workspace session data after the file exceeds 200 data rows. This bounded trimming keeps the workspace memory log manageable while retaining recent agent run outcomes.

Can I use this to log failed setup errors and successful syncs in the same place?▼

You can log both failed setup errors and successful syncs in the same place by appending structured entries to the shared memory log. The utility accepts various statuses and concise detail messages for each run.

Related Skills

Explore More Software Engineering Skills→
ScotterMonkScotterMonk
37

log-file-use

Create, read, and write timestamped log entries for project plans.

Community
Basic
Leep-GHLeep-GH

reskill

Extract recurring patterns from agent charters and histories into shared skills.

Community
Advanced
NirajkashyapNirajkashyap

wiki-history-ingest

Route agent history sources to the appropriate history-ingest workflow.

Community
Intermediate
w5851w5851
2

doc-exec-log-append

Append execution facts to a centralized log file using a Julia script.

Community
Intermediate