Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/runtime-logger
Emit info-level logs to file during task execution, similar to logger.info() calls in code
Passed 6 of 11 test cases with the skill, and 6 of 11 without it.
and 2 more in the full report
4 fixed7 passed either way6 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are starting a new shell script session to perform codebase analysis. Before writing any log entries, we need to ensure the target logging folder structure exists even if nested folders are missing, without failing if it already exists. What bash setup command should be run first?
| Checked | Without skill | With skill |
|---|---|---|
| Uses mkdir command with flag -p to create log directory safely | Passed | Passed |
| Target log directory is .claude/logs | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Before starting any task, ensure the log directory exists:
mkdir -p .claude/logs
Use this consistent format for all log entries:
echo "[$(date -Iseconds)] [LEVEL] phase: message" >> .claude/logs/activity.log
| 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 |
test cases passed, vs 6 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.