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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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.
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.
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.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。