agentleFS
spleenteospleenteo/maestro/.claude/skills/agenda/SKILL.md

agenda

Skill1 starsChanged 47 days agoMITView on GitHub

Today's plan, in any language: use for any question, in any language, about today's plan or what is left to do today, and to refresh today's agenda. The single entry point for that question: asks the scheduler agent for today's tasks and appointments and saves them to the agenda pane with mcp__agenda__agenda_set. Not for other days.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. tonydzi/second-brain-starter-kit★ 6same name
    2. yuri-xyz/skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Call the scheduler agent with the Agent tool and this request, with the lived day filled in:

    line 18
  2. Very specific:

    Call mcp__agenda__agenda_set with { date, events, tasks }.

    line 23
  3. Very specific:

    Read sources yourself or interpret a task manager's fields: scheduler does that.

    line 32
  4. Distinctive:

    Call the tool from a subagent: it refuses them, so this skill runs in the main conversation.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Agenda

Answers "what is on today" and keeps the agenda pane in step with the answer.

Steps

  1. Pane check. When mcp__agenda__agenda_set is not among the session's tools, take the local date from date '+%F', ask scheduler with the request of the scheduler step below, answer in chat as the reply step below says, and stop. Only when private/preferences.md exists in the working directory, add one line saying the pane needs the agenda plugin (claude plugin install agenda@maestro --scope project, run from the instance root). Elsewhere, add no hint.
  2. Lived day. The hour the day starts at is in the description of the date field of mcp__agenda__agenda_set. date '+%F %H:%M %z' gives local date, time and offset. If the local time is earlier than that hour, the day is the previous one (date -v-1d +%F on macOS, date -d yesterday +%F elsewhere). If no hour is found there, use the local date from date.
  3. Call the scheduler agent with the Agent tool and this request, with the lived day filled in:

    prospective_today for <lived day>. Return two blocks. APPOINTMENTS: that day's appointments that have a time, one per line as HH:MM title. TASKS: open tasks planned for that day, one title per line. Leave out reminders of future deadlines not planned for that day, done items, routines and notes. Plain titles, no source tags, flags or areas.

  4. Map the answer as is. Drop any trailing [source] tag or ⚠️ note from a line. Each APPOINTMENTS line becomes { start, title } with start = <day>T<HH:MM>:00<offset>, the offset from the lived day step (date gives +0100; write it +01:00). Each TASKS line becomes { title }. An empty block becomes []. Send every appointment that has a time: the pane hides the past ones.
  5. Call mcp__agenda__agenda_set with { date, events, tasks }.
  6. Reply in chat, in the language of the conversation. To a question about today's plan: short, appointments with their time, then tasks. To a refresh request: one short sentence saying the agenda is updated, since the pane shows it.

Keeping the pane current

Only when mcp__agenda__agenda_set is available; otherwise do nothing here. When a task or an appointment of today is created, closed, moved or cancelled, call mcp__agenda__agenda_set again with the whole list, updated with the change, without scheduler. If the list is not in the conversation, run the steps above from the start. Either way, confirm the change in one short sentence, without repeating the list.

Never

  • Read sources yourself or interpret a task manager's fields: scheduler does that.
  • Call the tool from a subagent: it refuses them, so this skill runs in the main conversation.

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.