log

Create structured session logs in an Obsidian vault or local logs directory.

7|3|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/gyroid-eth/orrery-telemetry --skill log-gyroid-eth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log
Source: https://github.com/gyroid-eth/orrery-telemetry/tree/main/skills/log
Command: npx skills add https://github.com/gyroid-eth/orrery-telemetry --skill log-gyroid-eth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with coding agents across sessions, decisions, changes, and verification steps are easily lost. This Skill preserves what happened in a session as a structured Markdown log so you or a teammate can reconstruct the work weeks later. ## Core Features & Use Cases - Two-layer destination strategy: Writes logs into an Obsidian vault with daily-note links, tags, and graph integration when configured, or falls back to a plain logs/ directory when Obsidian is unavailable. - Structured log template: Captures goal, decisions, work performed, verification, related notes, and next actions with consistent frontmatter and timestamped filenames like LOG_2026-01-15T0930 API Migration.md. - Related context search: Searches prior logs with ripgrep and links relevant earlier entries so the history of decisions stays connected. - Use Case: After finishing a debugging session, ask the agent to log the work; it records the root cause, files changed, and test results, then links the entry from today's daily note in your Obsidian vault. ## Quick Start Ask the agent to create a session log with a short theme, for example: create a session log for the API migration work we just finished.

Frequently Asked Questions about log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a session log of my coding agent's work?

Invoke the log skill with a short theme as the first argument, optionally followed by a project hint. The skill gets the current timestamp from the shell, searches for related prior logs, and writes a structured Markdown file with goal, decisions, work performed, and verification sections.

How do I save agent session notes to Obsidian?

Set the AGENTSTACK_OBSIDIAN_APP environment variable to an Obsidian-capable launcher and point AGENTSTACK_PROJECT_KEY at your vault. The skill then writes logs inside the vault with wiki links, tags, and a linked entry in the daily note.

What happens if Obsidian is not configured?

The skill falls back to a minimal mode that creates a logs directory at the git root or current working directory and writes the log file there. It skips daily-note editing and uses relative Markdown links instead of wiki links.

What filename format do session logs use?

Logs are named LOG_<YYYY-MM-DDTHHmm> <Theme>.md, for example LOG_2026-01-15T0930 API Migration.md. The timestamp always comes from the shell date command, never from the model's internal clock.

Can I update an existing session log instead of creating a new one?

Yes. The skill reads the whole note first, integrates new facts into the appropriate sections, avoids duplicating statements, and preserves existing links and frontmatter unless they are incorrect.