Skip to main content
skill CX Codex official · Anthropic

leave-tracker — Claude Code skill: what it does, how to install

Checks open employee leaves for legal deadlines and flags only the cases requiring action. Helpful for tracking certification and leave exhaustion dates.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add anthropics/claude-for-legal --skill leave-tracker -a claude-code
Open on GitHub

What leave-tracker does

The skill checks open employee leaves with hard legal deadlines and highlights only records requiring a decision. Instead of acting as a general status board, it explains what action is needed and why. Clean leaves without pending actions are summarized in a single line.

For records, it looks for a connected HRIS or reads ~/.claude/plugins/config/claude-for-legal/employment-legal/leave-register.yaml. If neither is found, the agent asks you to upload a spreadsheet or log entries with /employment-legal:log-leave.

Claude Code agents do not self-schedule. Because weekly checks are recommended, running it on Monday mornings requires a separate integration like cron or a calendar reminder.

What it helps with

  • identify open employee leaves with approaching certification deadlines
  • catch pending designation decisions before legal time limits expire
  • track leave exhaustion across current records
  • summarize routine leaves into single-line updates

Example prompts for the agent

  • /employment-legal:leave-tracker
  • Check our open leaves for upcoming legal deadlines using /employment-legal:leave-tracker

How to install leave-tracker

1Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill leave-tracker -a claude-code

2Manually: put the files in place

~/.claude/skills/leave-tracker/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/leave-tracker/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about leave-tracker

How to install leave-tracker in Claude Code?

Run npx skills add anthropics/claude-for-legal --skill leave-tracker -a claude-code.

Where does leave-tracker pull employee records from?

It pulls data from a connected HRIS or the local file ~/.claude/plugins/config/claude-for-legal/employment-legal/leave-register.yaml. When both are absent, it asks for a spreadsheet or prompts you to run /employment-legal:log-leave.

Can leave-tracker run automatically every week?

No, Claude Code agents do not run on their own schedule. You need to set up a cron job or a calendar reminder to trigger the command weekly.

Source text

SKILL.md · Apache-2.0
---
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.

© anthropics · Apache-2.0 · anthropics/claude-for-legal

Similar skills

All skills for Notes, tasks and projects →

From the same set118

is-this-a-problem Answers the "is this a problem?" question in under a minute by matching it against your risk calibration table and returning fine, needs a look, or hold. CX Codex +1 601installs ai-inventory Keeps a register of AI systems with your role and risk tier for each one under the EU AI Act. Useful once you run more than a single system. CX Codex +1 601installs bar-prep-questions Generates targeted MBE and essay practice questions for US bar exams. It aligns with your jurisdiction and tracks recurring errors in a study plan. CX Codex +1 600installs deposition-prep Builds a deposition outline for a witness: pulls their documents from the eDiscovery platform, organizes topics around the case theory, and surfaces impeachment material. CX Codex +1 600installs registry-browser Searches watched registries for skills, lists matches with descriptions, and offers to show the full SKILL.md before you install anything. CX Codex +1 599installs matter-close Closes a matter in the portfolio: captures the outcome, final exposure and lessons, then archives it without deleting the record. CX Codex +1 598installs takedown Drafts DMCA takedown notices, triages incoming infringement claims, and prepares §512(g) counter-notices. Useful for copyright enforcement against services under US jurisdiction. CX Codex +1 598installs investigation-add Adds interview notes and documents to an open investigation log. Use it to process new evidence batches against documented pull criteria. CX Codex +1 597installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor