staff-scheduler
Build optimized staff schedules that match coverage to demand while respecting labor budgets, employee availability, and local labor laws. Handles shift swaps, time-off requests, and identifies over/under-staffing before it happens.
Profile →npx skills add cosmicstack-labs/mercury-agent-skills --skill staff-scheduler --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Staff Scheduler ## Core Principles Labor is typically the second-largest cost (after COGS) for any shop or restaurant — often 25-35% of revenue. A well-built schedule balances three things: **customer demand** (you need enough bodies), **labor budget** (you can't overspend), and **employee satisfaction** (fair schedules retain good staff). The Staff Scheduler skill automates this balancing act. ### The Three Pillars of Great Scheduling 1. **Demand-driven coverage.** Schedule to the forecast, not to habit. If Mondays are slow, don't staff for Saturday volumes. 2. **Labor cost targeting.** Set a target labor % (e.g., 28% of sales) and build the schedule to hit it. Every hour above target eats margin. 3. **Fairness & compliance.** Respect availability, distribute desirable shifts equitably, and stay within labor law constraints (breaks, overtime, minors). --- ## Skill Workflow ### Step 1 — Gather Baseline Data Ask the user for: - **Staff roster:** Names, roles (server, cook, cashier, manager), hourly rates - **Availability:** Days/times each person can work (and cannot) - **Sales forecast:** Projected daily covers or revenue for the scheduling period - **Labor target:** Target labor
- Core Principles
- The Three Pillars of Great Scheduling
- Skill Workflow
- Step 1 — Gather Baseline Data
- Step 2 — Calculate Labor Budget
- Step 3 — Build Coverage Schedule by Day Part
- Step 4 — Generate Draft Schedule
- Step 5 — Handle Time-Off & Shift Swaps
- Step 6 — Compliance Check
- Step 7 — Publish & Notify
- Trigger Phrases
- Key Instructions Summary
- Common Mistakes
What does the staff-scheduler skill do?
Build optimized staff schedules that match coverage to demand while respecting labor budgets, employee availability, and local labor laws. Handles shift swaps, time-off requests, and identifies over/under-staffing before it happens.
How do I install it?
Run `npx skills add cosmicstack-labs/mercury-agent-skills --skill staff-scheduler --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From cosmicstack-labs/mercury-agent-skills, a repository with 364 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.