anthropics/log-leave
> Add a new leave to the leave register with the minimum information needed to start tracking deadlines. Use when an employee goes on leave and you want the tracker to watch designation, certification, and exhaustion clocks from day one.
npx skills add https://github.com/anthropics/claude-for-legal --skill log-leave
Adds a new leave entry to ~/.claude/plugins/config/claude-for-legal/employment-legal/leave-register.yaml with the minimum
information needed to start tracking deadlines. Use when an employee goes on
leave and you want the tracker to watch the clocks from day one.
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → jurisdiction table and Systems section.> A few quick questions to set up leave tracking:
>
> - Employee name or role (anonymized is fine)
> - Where do they work? (State — this determines which rules apply)
> - Leave type: FMLA / state leave (which state) / USERRA / ADA accommodation
> - Leave start date
> - Is this intermittent leave?
> - Expected return date (if known — leave blank if not)
> - Has the designation notice been sent? If yes, when?
> - Has medical certification been requested? If yes, when?
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md, look up the applicable leaveentitlement (hours/weeks) for this leave type in this jurisdiction.
~/.claude/plugins/config/claude-for-legal/employment-legal/leave-register.yaml using the leave registerformat from the leave-tracker agent. If the file doesn't exist, create it.
> "Logged. [Employee/Role] — [Leave type] — [Jurisdiction] — started [date].
> First deadline: [what it is and when]. Leave tracker will alert automatically."
/employment-legal:log-leave
/employment-legal:log-leave
Sarah (Sr. Engineer, works in California) just started FMLA today for a
serious health condition. Intermittent. No designation sent yet.
Take anthropics/log-leave from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.