~ / rigs / PsychQuant / che-ical-mcp

PsychQuant/che-ical-mcp

macOS Calendar & Reminders MCP server (29 tools) — native Swift EventKit for Claude Desktop & Code. Events + reminders CRUD, recurring, batch ops, conflict & duplicate detection, per-event timezone, undo/redo, #tags, --cli mode, SwiftUI --s

↗ GitHub ★ 40 MIT updated today project Claude CodeCodex Claude plugin
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~5.9k tokens
Moderate · median rig: 2.3k · breakdown
GUARDRAILS
1/5
No YOLO mode · details

Copy this rig

# review before running: this installs third-party code
$ npx degit PsychQuant/che-ical-mcp/.claude ./rig-che-ical-mcp  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit PsychQuant/che-ical-mcp/.agents/skills/spectra-apply .claude/skills/spectra-apply
$ npx degit PsychQuant/che-ical-mcp/.agents/skills/spectra-archive .claude/skills/spectra-archive
$ npx degit PsychQuant/che-ical-mcp/.agents/skills/spectra-ask .claude/skills/spectra-ask
$ npx degit PsychQuant/che-ical-mcp/.agents/skills/spectra-audit .claude/skills/spectra-audit
$ npx degit PsychQuant/che-ical-mcp/.agents/skills/spectra-debug .claude/skills/spectra-debug
$ npx degit PsychQuant/che-ical-mcp/.agents/skills/spectra-discuss .claude/skills/spectra-discuss
$ npx degit PsychQuant/che-ical-mcp/.agents/skills/spectra-ingest .claude/skills/spectra-ingest
$ npx degit PsychQuant/che-ical-mcp/.agents/skills/spectra-propose .claude/skills/spectra-propose
$ npx degit PsychQuant/che-ical-mcp/plugin/skills/archive-event .claude/skills/archive-event
$ npx degit PsychQuant/che-ical-mcp/plugin/skills/calendar-management .claude/skills/calendar-management
$ npx degit PsychQuant/che-ical-mcp/plugin/skills/troubleshoot-tcc .claude/skills/troubleshoot-tcc

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 7,204 rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(rm -rf *)",
      "Read(**/*.pem)",
      "Bash(rm -rf /)",
      "Bash(git push --force:*)",
      "Bash(sudo *)",
      "Read(.env)",
      "Bash(rm -rf /*)",
      "Read(./.env.*)",
      "Read(~/.aws/**)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(sudo:*)",
      "Bash(git reset --hard*)",
      "Bash(git reset --hard:*)",
      "Read(.env.*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(rm:*)",
      "Bash(git rebase *)",
      "Bash(wget *)",
      "Bash(npm publish:*)",
      "Bash(git commit *)",
      "Bash(gh pr merge *)"
    ]
  }
}

Skills (11)

Similar rigs

copied ✓