# Log

> Use when following what one teams ticket is doing right now (tm_log). Triggers: "P2 지금 뭐 하고 있어", "로그 보여줘", "tail the log for E-xxx/P2", "what is this story doing".

- Skill: `newkayak12/log` (Agent Skill)
- Install (CLI): `npx get-skill add newkayak12/log`
- Raw SKILL.md: https://api.skillmd.com/api/skills/newkayak12/log/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: newkayak12 (https://skillmd.com/u/newkayak12)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/newkayak12/log

---


# log — tm_log, rendered as a tail

`tm_log` is read-only and reads a log the key already points at: a STORY key follows its latest
dispatch's driver stream, an EPIC key follows the task ledger. It reads the file from its end and
returns only the last `tail` lines, already rendered one event per line. This skill calls it and
prints the Output Template below; it makes no decisions.

## Process

1. Take the key as given: `E-xxxxxxxx/Pn` for a STORY's driver, `E-xxxxxxxx` for the EPIC
   ledger (`E-xxxxxxxx/S` for a size-S task's harness driver). A TASK key (`.../Pn/U1`) is refused —
   use its STORY; that driver's stream covers every stage of the child run.
2. Call `tm_log({key, tail})` — `tail` defaults to 50 (max 500). Pass a number only if the user
   named one.
3. Print the Output Template. `lines` are already readable; print them as-is, in order.
4. To follow ("what's new since"), call again with `since: <cursor>` from the previous reply —
   only lines appended after it come back.
5. If `note` is set (no dispatch has started yet), print it instead of an empty block.

## Output Template

```
E-a1b2c3d4/P2  driver  dispatch:P2:1  alive      (EPIC: E-a1b2c3d4  ledger)
log: ~/.harness/tasks/<task_id>/drivers/dispatch_P2_1.stream.jsonl
--- last 3 of more (truncated) ---
assistant -> Bash npm test
<- ERROR 1 failing
result success turns=7 cost=$0.5000: done
cursor: 184213   (pass as since: to continue)
```

`alive` is the driver's (or, for an EPIC, the daemon's) pid liveness — `dead`/`—` otherwise.
Print `(truncated)` only when `truncated` is true (older lines exist). Driver lines read
`init model=...`, `assistant says: <text>`, `assistant -> <Tool> <what>`, `<- [ERROR] <result>`,
`result <subtype> turns=N cost=$X: <text>`, `rate_limit <status>`. Ledger lines read
`HH:MM:SS <event> k=v ...` (UTC).

## What Claude Does / What You Do

| Claude | You |
|--------|-----|
| Calls `tm_log({key, tail?, since?})` and prints the tail above — nothing more | Give a ticket key, STORY or EPIC, and optionally how many lines |
| Never reads the log file directly; never asks for `raw: true` unless you want the exact JSON | Say "more" or "what's new" to continue from the last cursor |

## Related Skills

- `ticket` — the same key's state, worktree and last verdict
- `board` — every STORY of the EPIC at a glance
- `inbox` — work waiting on you rather than on a driver

