# Ics Manager

> Manage local or remote ICS calendar sources to inspect upcoming meetings, summarize work hours, and add, update, or delete calendar events when users need a quick operational view of their schedule.

- Skill: `hsiangjenli/ics-manager` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add hsiangjenli/ics-manager`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hsiangjenli/ics-manager/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: hsiangjenli (https://skillmd.com/u/hsiangjenli)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/hsiangjenli/ics-manager

---


# ICS Manager

Read or edit `.ics` files from a local path or HTTP(S) URL.

## Setup (one-time only)

```bash
uv run scripts/check_dependencies.py --install
# Set ICS_SOURCE and optional ICS_RANGE_START/ICS_RANGE_DAYS in .env or ~/.config/ics-manager/.env
```

> **Do NOT run `check_dependencies.py` on every invocation.** `uv run` resolves dependencies automatically. Only run it once during initial setup or when the environment may be broken.

## Commands

All operations go through `scripts/ics_manager.py`:

| Command | Key flags | Notes |
|---|---|---|
| `list-events` | `--source` (repeatable), `--start`, `--end`, `--contains`, `--format json` | Default window: active configured range, else 14 days |
| `summarize-hours` | `--source` (repeatable), `--group-by day\|week`, `--contains` | Aggregates event durations across all sources |
| `overview` | `--source` (repeatable), `--start`, `--end`, `--contains`, `--format json` | Count, total hours, busiest day, per-source counts — **use this instead of combining list-events + summarize-hours** |
| `add-event` | `--source`, `--summary`, `--start`, `--end` | Local files only |
| `update-event` | `--source`, `--uid`, `--summary` | Local files only |
| `delete-event` | `--source`, `--uid` | Local files only; `.bak` backup written by default |

Remote URLs are read-only. Use `--uid` for update/delete.

`ICS_SOURCE` can contain multiple calendars separated by commas or new lines. You can also repeat `--source` on read commands:

```bash
uv run scripts/ics_manager.py overview \
	--source ~/calendar/work.ics \
	--source ~/calendar/team.ics
```

To make Scrum check-ins default to the current sprint window, set these once in `.env`:

```dotenv
ICS_RANGE_START=2026-05-01
ICS_RANGE_DAYS=14
```

With that configuration, `list-events`, `overview`, and `summarize-hours` automatically use the active 14-day window starting from the configured anchor. You only need `--start` or `--end` when overriding the default sprint window.

## Efficiency rules

- **One command per task**: use `overview` when the user asks for a schedule summary or total hours; only call `list-events` when full event details are needed.
- **Never run the same command twice**: do not call `list-events --format json` followed by `list-events` in plain format; pick one.
- **Prefer configured sprint defaults**: when `ICS_RANGE_START`/`ICS_RANGE_DAYS` are set, use that active window without asking for a start date again.
- **Skip setup**: do not call `check_dependencies.py` before each command.

## Resources

- `scripts/ics_manager.py` - Parse, summarize, and modify ICS files
- `references/workflows.md` - Prompt patterns and caveats
- `.env.example` - Environment configuration template