agentleFS
ThisisilyThisisily/momputer/skills/calendar-fixer/SKILL.md

calendar-fixer

Skill2 starsChanged 32 days agoLicence not identifiedView on GitHub

Reviews a Google Calendar read-only (the next four weeks, plus the last two for patterns) through a Calendar connector or MCP server, browser automation (Claude in Chrome, Codex's browser), or both, and builds a private HTML dashboard and a fix plan. It finds double bookings, back-to-back runs, meetings outside working hours, invitations never answered, stale repeating meetings, meetings with no video link or place, duplicates, time-zone slips, days with no free two hours, and where the hours go: by week, kind of meeting, weekday and hour, organizer and series. The user ticks the fixes they approve. Use when the user asks to fix, clean up, audit, review or declutter their calendar or schedule, find conflicts or double bookings, see how much time goes to meetings, or get focus time back. Never answers, declines, moves, edits or deletes an event without the user's tick for that event. Not for scheduling new meetings or finding a time across several people, and not for calendars other than Google Calendar.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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.