agenda

Write timestamped activity entries to a reverse-datetree org-agenda.

6|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/junghan0611/agent-config --skill agenda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agenda
Source: https://github.com/junghan0611/agent-config/tree/main/skills/agenda
Command: npx skills add https://github.com/junghan0611/agent-config --skill agenda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) components.

What problem does it solve?

Agent activity often lacks a concise, cross-session log that can be viewed in org-agenda. agenda provides a lightweight method to stamp activity entries into a reverse datetree timeline for quick visibility.

Core Features & Use Cases

  • Create standardized timestamp entries with a title, optional tags, and an optional body.
  • Store entries under ~/org/botlog/agenda per device for cross-session tracking.
  • Support multi-line body text and per-device separation to keep context organized.

Quick Start

Run the agenda-stamp.sh script with a title and optional tags to create a timestamp entry.

Frequently Asked Questions about agenda

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

FAQPage Schema
How do I log agent activity to an org-agenda timeline?▼

You can log agent activity to an org-agenda timeline by running the agenda-stamp.sh script, which writes structured timestamp entries with a title, optional tags, and a body to a reverse-datetree structure.

What is a reverse-datetree and how does it organize activity logs?▼

A reverse-datetree organizes activity logs hierarchically by date, storing entries under ~/org/botlog/agenda so that recent sessions and tasks appear prominently in your org-agenda view.

Can I track multi-device agent sessions in a single org-agenda view?▼

Yes, you can track multi-device agent sessions by configuring a device identity for each agent, which separates entries per device while maintaining a unified activity timeline in org-agenda.

Do I need python3 to stamp agent activity entries?▼

Yes, python3 is a required dependency to run the agenda-stamp.sh script and generate standardized local entries for session starts, task completions, or notable actions.

What is the best way to record task completions across multiple agents?▼

The best way to record task completions across multiple agents is using a lightweight shell script to stamp standardized entries into a shared local directory, ensuring cross-session tracking without complex database setup.

Why are my agent activity logs not showing up in org-agenda?▼

Agent activity logs may not appear in org-agenda if the entries are not written to the expected ~/org/botlog/agenda directory or if the reverse-datetree structure is improperly configured for org-agenda parsing.