runtime-logger
Emit info-level logs to file during task execution, similar to logger.info() calls in code
npx skills add majiayu000/claude-skill-registry --skill runtime-logger --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Runtime Activity Logger Log key activities to `.claude/logs/activity.log` using bash as you work. This creates a trace of agent reasoning and actions analogous to info-level logging in deterministic code. ## Setup Before starting any task, ensure the log directory exists: ```bash mkdir -p .claude/logs ``` ## Log Format Use this consistent format for all log entries: ```bash echo "[$(date -Iseconds)] [LEVEL] phase: message" >> .claude/logs/activity.log ``` ### Log Levels | Level | Use For | |-------|---------| | `INFO` | Normal operations, progress updates, decisions | | `DEBUG` | Detailed technical information when troubleshooting | | `WARN` | Unexpected situations that don't block progress | | `ERROR` | Failures that affect task completion | ## When to Log ### Task Lifecycle - **Task start**: Log the goal and planned approach - **Task completion**: Log summary, outcome, and any artifacts created ### Tool Usage - **Before significant tool use**: Log what tool and why - **After tool use**: Log outcome (success/failure, key findings) ### Decision Points - **Architectural choices**: Log reasoning for design decisions - **Branch points**: Log why one approach was chosen over alternat
- Setup
- Log Format
- Log Levels
- When to Log
- Task Lifecycle
- Tool Usage
- Decision Points
- Subagent Activity
- Examples
- Starting a Task
- Subagent Delegation
- Warnings and Errors
- Task Completion
- Log File Management
mkdir -p .claude/logs echo "[$(date -Iseconds)] [LEVEL] phase: message" >> .claude/logs/activity.log echo "[$(date -Iseconds)] [INFO] start: Beginning refactoring task for payment module" >> .claude/logs/activity.log echo "[$(date -Iseconds)] [INFO] planning: Will analyze current structure, identify patterns, then apply Strategy pattern" >> .claude/logs/activity.log echo "[$(date -Iseconds)] [INFO] tool: Reading src/payments/processor.py to understand current implementation" >> .claude/logs/activity.log echo "[$(date -Iseconds)] [INFO] tool-result: Found 3 payment types with duplicated validation logic" >> .claude/logs/activity.log echo "[$(date -Iseconds)] [INFO] decision: Using Strategy pattern - cleaner than inheritance for 3 payment types" >> .claude/logs/activity.log echo "[$(date -Iseconds)] [INFO] decision: Keeping backward compatibility by wrapping legacy interface" >> .claude/logs/activity.log echo "[$(date -Iseconds)] [INFO] delegate: Spawning test-writer subagent for unit test coverage" >> .claude/logs/activity.log echo "[$(date -Iseconds)] [INFO] delegate-complete: test-writer created 12 unit tests, all passing" >> .claude/logs/activity.log
What does the runtime-logger skill do?
Emit info-level logs to file during task execution, similar to logger.info() calls in code
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill runtime-logger --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
