Skip to content
Back to skills

Practice Calendar Sync

ASecurity

Audit or reconcile approved tracked dates with a configured dedicated calendar. Use for exact calendar diffs, not general scheduling or unverified legal-date calculation.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 11, 2026
developmentpythongobashapi

Works with

  • api

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add lawyered0/lawyeredos --skill practice-calendar-sync --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Practice Calendar Sync?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Practice Calendar Sync
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lawyered0-practice-calendar-sync/badge)](https://www.skillsdirectory.com/skills/lawyered0-practice-calendar-sync)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: practice-calendar-sync
description: Audit or reconcile approved tracked dates with a configured dedicated calendar. Use for exact calendar diffs, not general scheduling or unverified legal-date calculation.
---

# Calendar Reconciliation

The matter register is authoritative; Calendar is a downstream projection.
Missing or failed calendar access never reverses or conceals a tracker result.

Use the bundled planner for fixture or exported event JSON:

```bash
PYTHONPATH="${LAWYEREDOS_ROOT}/src" "${LAWYEREDOS_PYTHON:-python3}" -m lawyeredos.calendar_plan plan \
  --desired desired.json --existing existing.json
```

It produces a read-only create/update/remove/unchanged diff. If
`calendar_adapter = "google-calendar-api"` is explicitly configured, use the
bundled adapter described in `${LAWYEREDOS_ROOT}/docs/ADAPTERS.md`. Credentials come only from the
named environment variable. Automated tests use a fake transport and never a
live account.

For an adapter operation:

1. Require a non-empty configured calendar ID and timezone. Never default to a
   primary calendar.
2. Search a bounded window, paginate fully, and read every candidate.
3. Match on an exact parseable sync key, not title similarity.
4. Present the precise diff. Creation, update, and deletion require approval of
   the exact event or bounded set.
5. After an ambiguous response, search and read again; never blindly retry.
6. Use no attendees or meeting link, private visibility, and minimum necessary
   matter detail.
7. Re-read created or updated events before reporting success.

The adapter itself requires an exact event ID for update/delete, a private
`sync_key` for create/update, and a matching preview confirmation token. A
missing token, credential, calendar ID, or complete page traversal fails closed.
Use `lawyeredos.integrations calendar-preview` and
`calendar-commit`; never call the remote endpoint directly from the skill.

An asserted or calculated date is not a verified legal deadline. Use the
applicable jurisdiction profile and current primary sources first.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.