workforce-scheduling

workforce-scheduling is a skill for Claude Code from kishorkukreja/awesome-supply-chain. It costs 78 tokens per session (6,671 once invoked), scanned A, original, MIT.

A workforce scheduling guide for planning employee shifts around demand, availability, skills, labor rules, and operating constraints.

In plain words
What is it for?
Use it to plan warehouse shifts, assign staffing levels, balance labor demand, and review scheduling constraints.
Why use it?
It helps replace manual rosters with schedules that account for staffing needs, overtime, breaks, and employee availability.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the supply-chain-skills plugin — 133 skills shipped together , and of supply-chain-skills

Good fit Use it to plan warehouse shifts, assign staffing levels, balance labor demand, and review scheduling constraints.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kishorkukreja/awesome-supply-chain/workforce-scheduling
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add kishorkukreja/awesome-supply-chain --skill workforce-scheduling
Clone the repo
git clone --depth 1 https://github.com/kishorkukreja/awesome-supply-chain

Made for: Claude Code.

Or install supply-chain-skills, the plugin that ships this one along with the rest of its 133 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for workforce-scheduling

README.md
[![agentmods](https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/workforce-scheduling/github.svg)](https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/workforce-scheduling)
Your own site
<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/workforce-scheduling"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/workforce-scheduling/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for workforce-scheduling

Your own site · 80×15
<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/workforce-scheduling"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/workforce-scheduling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,671 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.06671
Opus 5 $0.00039 $0.03335
Sonnet 5 $0.00016 $0.01334
Haiku 4.5 $0.00008 $0.00667

Measured 9d ago against content hash c86b10172f7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

workforce-scheduling scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/workforce-scheduling/SKILL.md · 944 lines

How it starts

The opening of the file, as written. The whole thing — 944 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workforce Scheduling

You are an expert in workforce scheduling and labor optimization for warehouses and supply chain operations. Your goal is to help create optimal shift schedules that match labor supply with demand, minimize costs, ensure compliance, and improve employee satisfaction.

Initial Assessment

Before optimizing workforce scheduling, understand:

  1. Labor Demand

    • Daily/weekly order volume patterns?
    • Peak periods and seasonality?
    • Tasks to be performed (picking, packing, receiving)?
    • Required skills and certifications?
    • Service level targets (on-time shipping)?
  2. Labor Supply

    • Total workforce size (full-time, part-time, temp)?
    • Employee availability and preferences?
    • Skill levels and cross-training?
    • Shift length preferences (8hr, 10hr, 12hr)?
    • Union rules and labor agreements?
  3. Business Constraints

    • Operating hours (24/5, 24/7, day shift only)?
    • Minimum staffing levels?
    • Maximum consecutive days worked?
    • Overtime rules and costs?
    • Break and meal period requirements?
    • Weekend and holiday staffing needs?
  4. Current State

    • Current scheduling method (manual, software)?
    • Current labor costs (regular + OT)?
    • Labor utilization rates?
    • Employee satisfaction with schedules?
    • Schedule change frequency?

Workforce Scheduling Framework

Scheduling Objectives

Primary Goals:

  1. Match Demand: Ensure sufficient labor for forecasted workload
  2. Minimize Cost: Optimize mix of regular hours, overtime, and temps
  3. Maximize Utilization: Reduce idle time and overstaffing
  4. Employee Satisfaction: Consider preferences, fairness, work-life balance
  5. Compliance: Meet labor laws, union rules, company policies

Key Metrics:

  • Labor cost per unit ($/order, $/line picked)
  • Labor utilization % (productive time / scheduled time)
  • Schedule efficiency (actual vs. planned labor hours)
  • Employee turnover and absenteeism
  • Overtime % (OT hours / total hours)

Read the full file on GitHub · 944 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 944 lines · 78 tokens per session scan A c86b10172f7e

Subscribe to this mod's changes

workforce-scheduling is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 12d ago), licensed MIT. It adds 78 tokens to every session and 6,671 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories