agentleFS
Sign inStart free
apinizerapinizer/agentnizer-cookbook/.claude/skills/logs/SKILL.md

logs

Skill2 starsChanged 4 months agoMITView on GitHub

Tail the daemon log or a specific task's handoffs/meta. Read-only.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read-only wrapper around team.sh logs.

    line 8
  2. Distinctive:

    Does not spawn any agent.

    line 42
  3. Very specific:

    Does not write to .state/.

    line 43
  4. Distinctive:

    Does not modify any file.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/logs — Tail daemon or task logs

Read-only wrapper around team.sh logs. Streams or prints the daemon's log file or a specific task's per-task log without spawning anything.

Usage

/logs                          # tail the daemon log, live (Ctrl+C to stop)
/logs <task-id>                # stream one task's handoffs.jsonl (last 50 lines, then live)

What it does

Forwards to the repo-root team.sh:

  • /logs → ./team.sh logs --daemon, which runs tail -f on the daemon log file (streams from the current end; Ctrl+C to stop).
  • /logs <task-id> → ./team.sh logs <task-id>, which tails .state/tasks/<task-id>/handoffs.jsonl (last 50 lines, then live — one row per agent transition). team.sh logs does not print meta.json; read it separately if you need the current snapshot.

team.sh logs has no --tail N or --follow flag — the daemon log always streams live from wherever tail -f starts.

Output sample

2026-05-09T10:14:02Z INFO  [pipeline_daemon] spawn role=analyst task=20260509-1014-abc
2026-05-09T10:14:31Z INFO  [pipeline_daemon] role_done analyst task=20260509-1014-abc tokens=8421
2026-05-09T10:14:31Z INFO  [pipeline_daemon] spawn role=architect task=20260509-1014-abc

What it does NOT do

  • Does not spawn any agent.
  • Does not write to .state/.
  • Does not modify any file.

Notes

The daemon log is the first place to look when a task seems stuck. For a specific task's history, prefer /logs <task-id> over grepping the daemon log — the per-task handoffs.jsonl is the authoritative timeline.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free