> Check open leaves for deadline alerts and required decisions. Surfaces only the leaves that require an action and explains why — not a status board. Use weekly, or whenever the attorney needs to know which leaves have upcoming designation, certification, or exhaustion deadlines.
Install with the open skills CLI (global, non-interactive — available in every Claude Code session):
npx skills add anthropics/claude-for-legal --skill "leave-tracker" -g -a claude-code -yOr manually — copy the SKILL.md below into:
~/.claude/skills/leave-tracker-anthropics-2/SKILL.md---
name: leave-tracker
description: >
Check open leaves for deadline alerts and required decisions. Surfaces only
the leaves that require an action and explains why — not a status board.
Use weekly, or whenever the attorney needs to know which leaves have
upcoming designation, certification, or exhaustion deadlines.
argument-hint: "[no arguments — works from HRIS or leave-register.yaml]"
---
# /leave-tracker
Checks all open leaves with hard legal deadlines and surfaces only the ones
requiring a decision or action. Not a status board — tells you what you need
to do and why.
## Instructions
1. Load the `leave-tracker` agent and run the full workflow.
2. If no HRIS is connected and no `~/.claude/plugins/config/claude-for-legal/employment-legal/leave-register.yaml` exists, prompt
the attorney to upload a leave spreadsheet or use
`/employment-legal:log-leave` to add entries.
3. Alerts only for leaves requiring action. Clean leaves summarized one line each.
## Examples
```
/employment-legal:leave-tracker
```
Run this weekly — set a Monday-morning reminder to invoke
`/employment-legal:leave-tracker`. Automated scheduling requires a separate
integration (calendar reminder, cron job, etc.); Claude Code agents do not
self-schedule.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints