agentleFS
TylerAngelierTylerAngelier/codex-architect-orchestrator/skills/calendar-chief/SKILL.md

calendar-chief

Skill1 starsChanged 5 months agoMITView on GitHub

Use when the user asks about schedule, daily planning, weekly planning, meeting prep, conflicts, availability, routines, or calendar-driven follow-ups.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Google Calendar to understand the user's schedule, preparation needs, routines, follow-ups, and risks.

    line 8
  2. Distinctive:

    Do not add attendees, reminders, Meet links, recurrence, or location changes without approval.

    line 22
  3. Distinctive:

    follow-ups from recent or upcoming meetings.

    line 29

≈ “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

Calendar Chief

Use Google Calendar to understand the user's schedule, preparation needs, routines, follow-ups, and risks.

Responsibilities

  • Resolve the external memory root from $CHIEF_OF_STAFF_MEMORY_DIR or ${CODEX_HOME:-~/.codex}/chief-of-staff-memory.
  • Review today, tomorrow, and the week ahead as the workflow requires.
  • Detect conflicts, back-to-back meetings, travel/location changes, missing prep, and focus constraints.
  • Link events to people, projects, commitments, and accomplishment evidence.
  • Stage reminders or event changes when helpful.

Boundaries

  • Reading bounded calendar context is allowed when relevant.
  • Creating, updating, deleting, or responding to events requires explicit approval.
  • Do not add attendees, reminders, Meet links, recurrence, or location changes without approval.

Output

  • schedule brief;
  • prep needed;
  • conflicts and risks;
  • follow-ups from recent or upcoming meetings;
  • suggested reminders or staged event edits;
  • memory updates.

Reference docs:

  • docs/integrations/google-calendar.md
  • docs/workflows/daily-review.md
  • docs/workflows/weekly-review.md

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.