leave-tracker

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean and well-organized for a simple delegating skill, but its core instruction defers to an external agent ("run the full workflow") without documenting the actual procedure or any validation checkpoints, leaving actionability and workflow clarity incomplete.

Suggestions

Replace 'Load the `leave-tracker` agent and run the full workflow' with the concrete steps of that workflow (which deadlines are checked, how they are computed against today's date, how an item is judged 'requiring action') so Claude can execute or verify the agent's output rather than trusting a black box.

Add explicit validation/checkpoint steps — e.g., confirm the HRIS or leave-register.yaml data is current before alerting, and define what 'clean' vs 'requires action' means operationally — instead of only a conditional fallback for missing data.

Include a concrete example of the alert output (the one-line-per-clean-leave summary and the action-required alert format) so the expected behavior is unambiguous and testable.

Dimension	Reasoning	Score
Conciseness	The body is lean and short with no concept-explanation padding (it does not explain what a leave or HRIS is), and it assumes Claude's competence. The closing scheduling note is a brief, useful guardrail rather than fluff. Not score 2 because nearly every line carries actionable instruction or scope.	3 / 3
Actionability	Provides some concrete guidance (the leave-register.yaml path, the fallback `/employment-legal:log-leave` command, and the invocation example) but the core step — "Load the `leave-tracker` agent and run the full workflow" — defers to an undocumented agent without specifying what the workflow does. Not score 1 because real concrete specifics exist; not score 3 because key operational details are missing.	2 / 3
Workflow Clarity	A numbered 1-3 sequence exists (load agent, fallback if no HRIS/yaml, alert behavior) but there are no validation checkpoints and "run the full workflow" hides the actual process. Not score 1 because steps are present and ordered; not score 3 because checkpoints and the real procedure are absent.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no bundle files (references/scripts/assets absent) and is organized into clear ## Instructions and ## Examples sections, meeting the simple-skill guideline that well-organized sections alone warrant a 3. Not score 2 because content is appropriately sectioned with nothing that should be split out.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete actions, names specific deadline categories, includes an explicit "Use when" trigger, and carves out a distinct niche with "not a status board" scoping. Voice is consistently third person. It is concise without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Check open leaves for deadline alerts and required decisions" and "Surfaces only the leaves that require an action and explains why" — tied to three named concrete deadline types (designation, certification, exhaustion). It is not the level below because it goes beyond naming a domain to enumerate specific operations and objects, matching the score-3 anchor.	3 / 3
Completeness	Clearly answers both what ("Check open leaves for deadline alerts... Surfaces only the leaves that require an action and explains why") and when ("Use weekly, or whenever the attorney needs to know...") with an explicit trigger. Not score 2 because the when-clause is explicit, not merely implied.	3 / 3
Trigger Term Quality	Includes an explicit trigger clause ("Use weekly, or whenever the attorney needs to know which leaves have upcoming designation, certification, or exhaustion deadlines") with natural domain terms an attorney would actually say. Not score 2 because coverage is broad and the trigger is explicitly stated rather than merely implied.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (leave-deadline tracking for attorneys) and explicitly scopes itself with "not a status board," with specific triggers unlikely to fire for unrelated skills. Not score 2 because the triggers are distinct enough to avoid overlap with general leave/status skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: anthropics/claude-for-legal
Path: employment-legal/skills/leave-tracker/SKILL.md
Commit: 4a6c651

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.