How do I install the Task Logbook skill?

Run npx skillmds@latest add marin-community/task-logbook in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Task Logbook safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Task Logbook?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Task Logbook free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Task Logbook?

marin-community (@marin-community) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Task Logbook by marin-community — Agent Skill

Name: Task Logbook
Author: marin-community

Task Logbook

Maintain a cross-project task or research log in Echo. Use for multi-step investigations, experiments, long-running implementation work, or any task whose milestones must survive the current agent session without adding a repository logbook file.

File contents

Skill: Task Logbook

Use Echo's append-only work log instead of .agents/logbooks/, .agents/ops/, or another repository progress file. Pick one stable project slug such as harbor:issue-123 or vllm:grugmoe-refresh and reuse it for the whole thread.

Append one entry after each milestone that changes the next action:

uv run .agents/skills/consult-echo/scripts/echo.py work-log add \
  --project "<repo>:<issue-or-task>" \
  --title "<one-line result>" \
  --body "<evidence, interpretation, and next action>"

Record decisions, falsified hypotheses, measured results, launches, failures, and handoff state. Link the issue, PR, run, dashboard, or immutable artifact that supports the entry. Omit routine commands and narrative that will not affect a future reader.

The work log is chronological and append-only. Correct a mistaken entry with a new entry. Keep coordinating issues concise and link the Echo conversation page when the detailed history matters.

At completion, publish reusable conclusions through write-ops-log, write-design-doc, repository docs, or an existing Echo synthesis. Do not copy the whole work log into that durable summary.

Frequently asked questions