agentleFS
davekilleendavekilleen/Dex/.agents/skills/calendar-setup/SKILL.md

calendar-setup

Skill509 starsChanged 3 months agoMITView on GitHub

Grant Python calendar access for ~30x faster calendar queries. Use when the user says 'connect my calendar', 'calendar is slow', 'set up calendar access'. Not for connecting Google Workspace as a whole; use `google-workspace-setup`.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After initial Dex installation

    line 13
  2. Distinctive:

    If calendar queries feel slow

    line 14
  3. Distinctive:

    If you see "Calendar access denied" errors

    line 15
  4. Very specific:

    Run the permission checker: python3 core/mcp/scripts/check_calendar_permission.py

    line 22
  5. Distinctive:

    Do not promise that a Mac permission dialog will appear.

    line 24
  6. Distinctive:

    No user action possible

    line 49
  7. Distinctive:

    No need to run this again - permission is persistent for that app

    line 54
  8. Distinctive:

    Privacy: All calendar data stays local - Dex never sends calendar data anywhere

    line 63
  9. Distinctive:

    Fallback: If EventKit isn't available, Dex falls back to AppleScript (works but slower)

    line 64
  10. Distinctive:

    Do not wait for a dialog, and do not switch to Terminal as the only fix

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
<!-- Generated from `.claude/skills/calendar-setup/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->

Calendar Setup - Enable Fast Queries

Purpose: Grant calendar access for 30x faster calendar queries (30s → <1s)

When to run:

  • After initial Dex installation
  • If calendar queries feel slow
  • If you see "Calendar access denied" errors

Process

  1. Check current permission status:
    • Run the permission checker: python3 core/mcp/scripts/check_calendar_permission.py
    • Show the user what status was returned
    • Do not promise that a Mac permission dialog will appear. When Dex runs inside VS Code or Cursor, that dialog often never shows.
  2. If Already Authorized:
    • Great! Calendar queries are already optimized.
    • No action needed.
  3. If NotDetermined or Denied:
    • VS Code and Cursor are first-class Calendar surfaces. Send the person to System Settings for the app Dex is running in. Do not send them to a standalone terminal as the only path. Do not tell them to wait for a popup. Do not tell them that granting Terminal, Python, or python3 is enough.
    • Show clear instructions:
      To enable fast calendar queries:
      
      1. Open System Settings (Command+Space, type "System Settings")
      2. Click "Privacy & Security" in the sidebar
      3. Click "Calendars"
      4. Find the app Dex is running in — VS Code or Cursor — and turn it on
      5. Click that app and set access to Full (not "Add Only")
      6. Quit the editor and open it again
      7. Run /calendar-setup again to verify
    • A Terminal grant does not transfer to the editor. Reinstalling Dex does not fix a missing editor grant.
  4. If Restricted:
    • Explain: "Calendar access is blocked by system policies (parental controls or enterprise MDM)"
    • Calendar queries will use AppleScript (slower but functional)
    • No user action possible
  5. After Success:
    • Confirm: "✅ Calendar access granted! Queries are now 30x faster."
    • Explain: "Calendar queries now use native EventKit instead of AppleScript"
    • No need to run this again - permission is persistent for that app

Technical Notes

  • EventKit vs AppleScript: EventKit uses database queries (fast), AppleScript loads all events then filters (slow)
  • Permission is per app: macOS grants Calendar access to the app that is asking. When Dex runs inside VS Code or Cursor, grant that editor. A Terminal grant does not carry over.
  • Permission is persistent: Once granted to the editor, access lasts until it is revoked
  • Privacy: All calendar data stays local - Dex never sends calendar data anywhere
  • Fallback: If EventKit isn't available, Dex falls back to AppleScript (works but slower)

Troubleshooting

"Module EventKit not found":

  • Run: pip3 install pyobjc-framework-EventKit
  • This should have been installed during Dex setup

No permission popup / access still denied:

  • Do not wait for a dialog, and do not switch to Terminal as the only fix
  • Open System Settings → Privacy & Security → Calendars
  • Turn on VS Code or Cursor (the app Dex is running in) and set Full access
  • A grant already given to Terminal, Python, or python3 does not transfer
  • Reinstalling Dex does not fix this

Still seeing slow queries after granting access:

  • Restart the app Dex is running in (VS Code or Cursor) to reload the calendar connection
  • Verify permission: python3 core/mcp/scripts/check_calendar_permission.py

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.