Benefits and leave
SkillMediabenefits-and-leave is a skill for designing and running employee benefits and leave programs, covering health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Once added, your AI can design or review a benefits package, prepare for a renewal, write leave policy, and handle leave requests.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, describe the task at hand — such as reviewing a benefits package, preparing for a renewal, or handling a leave request — and share any relevant plan or policy details you already have.
Then ask your AI: use the Benefits and leave skill
What your AI can do with it
- Design or review a benefits package, including health and retirement plans
- Prepare for a benefits renewal
- Write leave policy
- Handle a leave request
- Keep benefits administration compliant
- Help decide what benefits to offer
What this skill tells your AI
The instructions your AI receives, as published by cbrock84/headcount in plugins/people/skills/benefits-and-leave/SKILL.md and read by ahel’s review.
Benefits are the second largest people cost after salary and the one employees judge most directly.
people:compensation-and-leveling covers pay bands and leveling; this covers everything else in the
package.
Benefits and leave are heavily regulated and jurisdiction-specific — in the United States, ERISA, COBRA, ACA, FMLA and their state equivalents, with state family-leave and sick-leave laws differing substantially. Plan design and administration need a qualified benefits broker or employment counsel. This structures the decisions and names what to ask.
Design for what people actually value
Benefits budgets are routinely spent on things that survey well and are used rarely, while the things people quietly need are underfunded.
The reliable pattern: health coverage quality, retirement match, and real time off dominate perceived value nearly everywhere. Beyond those, ask rather than assume — a young workforce and one with school-age children value very different things, and the difference is large enough to be worth measuring.
Watch utilization. A benefit nobody uses is either badly communicated or badly chosen, and the two have different remedies.
Cost, and the renewal you should not sleepwalk
Health costs rise faster than general inflation more or less every year, so a flat renewal is not the baseline — the baseline is an increase you must actively negotiate down or absorb by design.
Start renewal months ahead, not weeks. Understand what drives your own experience rating, model plan design changes against employee impact, and market the plan periodically even when you intend to stay — a broker who knows you are not looking negotiates accordingly.
Cost-shifting to employees is a pay cut delivered indirectly. It may be the right call; describe it honestly when you make it, because employees compute it correctly and describing it otherwise costs more trust than the money saved.
Leave: policy is the easy part
Write policy that a manager can apply without calling HR for every case — eligibility, notice, documentation, pay treatment, and how it interacts with other leave types.
The failures are in administration: leave running concurrently under multiple entitlements, return-
to-work handled ad hoc, and accommodation requests treated as leave questions when they are legal
ones. Route anything touching disability, pregnancy, or accommodation through counsel via
people:employee-relations.
Track leave centrally rather than in managers' memories. The organization that cannot say who is on what leave and until when is the one that mishandles a return.
Never
- Change plan design without modeling the effect on the employees who use it most.
- Enter a renewal without having tested the market recently.
- Describe cost-shifting as a benefits enhancement.
- Handle an accommodation request as a leave administration question.
Signals
- GitHub stars
- 1k
- Forks
- 209
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
benefits-and-leave- Source
- github.com/cbrock84/headcount