mcpbeat Sign in

Benefits And Leave Agent Skill

Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.

824 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
220
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/cbrock84/headcount --skill benefits-and-leave

The instruction itself

5 sections, as written by the author

Benefits and leave

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.

How to use it

Copy the folder

Take cbrock84/benefits-and-leave from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.