Skip to content

Packs

Operations manager

When to use it
Staff rotas from who is available, what each shift needs and the working-time rules: a week or fortnight built and drawn as a grid, shown only once a script has checked every shift's cover and skills, and every person's hours, rest between shifts and days in a row.
Covers
Staff the shifts (1)
Where you decide
No gated loop of its own; the skills run one at a time.
Size
6 skills · 0 loops
npx skilldrop-cli install --pack operations-manager

Installs 6 skills, including core.

Other ways to install

The pack's loops too, each as an invokable skill:

npx skilldrop-cli install --loop --pack operations-manager

In Claude Code, as a plugin (after /plugin marketplace add sananthanarayan/skilldrop):

/plugin install operations-manager@skilldrop

Into Cursor, Kiro or another IDE:

npx skilldrop-cli install --pack operations-manager --ide cursor

Start here: Get next week's rota, with every shift covered and nobody short of rest

Paste this into your agent:

Make next week's rota for the café, Monday to Saturday. Every day: an opening shift 06:30–14:30 and a closing shift 14:00–21:00, each needing one keyholder and one barista. Staff: Amira (keyholder, barista, max 40 h), Ben (barista, max 24 h, not Wednesdays), Chloe (keyholder, barista, max 32 h), Dev (keyholder, barista, max 40 h), Ema (barista, max 24 h, not Mondays or Tuesdays), Fay (barista, max 32 h). At least 11 hours between shifts, nobody more than 5 days in a row.
Before you start
  • Who works for you, what they can do, and when they can't work
  • The shifts you need covered, with how many people of each kind
  • Python 3 on the machine, which the rota check and week drawing run on
How to tell it worked
shift-roster leads with the rota as a table of days by people, says which shifts it couldn't fill and why, lists the rules it assumed, and saves a week grid drawn from a check that found every shift covered and no rest, hours or consecutive-day rule broken.
If nothing happens
If shift-roster does not activate, ask for it by name ("use shift-roster"). If it says a week can't be covered, it names the smallest change that would; give it that change or say which rule may bend.

A typical session

When: You need next week's rota, or want to know whether the one you drew breaks any rule.

You bring:

  1. shift-roster
    You
    Give it the staff, the shifts and the rules, or a rota you've already drawn.
    You get
    A rota that passes every rule, as a table and a week grid, or the problems in yours with the fix for each.
    You decide
    Publish the rota, or say which preference to trade (a person's day off, a rule that may bend).
  2. shift-roster
    You
    Tell it what changed: someone off sick, a swap two people asked for.
    You get
    The rota re-checked with the change, and who can cover any shift it leaves short.

You end with: A rota you can publish, checked shift by shift and person by person.

Compare Operations manager with another pack

Skills in this pack (1)

Included from core (5)