skilldrop-cli 1.7.0 → 1.8.0

package/packs/interior-designer/skills/furniture-layout/templates/layout.json

@@ -0,0 +1,26 @@
+{
+  "title": "Living room, 5.0 × 4.2 m",
+  "units": "m",
+  "size": [5.0, 4.2],
+  "north": 0,
+  "min_walkway": 0.9,
+  "accessible": false,
+  "max_coverage": 0.5,
+  "doors": [
+    {"name": "Hall door", "at": [0.8, 0], "width": 0.9, "hinge": "left", "swing": "in", "entrance": true}
+  ],
+  "windows": [
+    {"at": [2.5, 4.2], "width": 1.8, "sill": 0.9}
+  ],
+  "obstacles": [
+    {"name": "Radiator", "type": "radiator", "rect": [1.8, 4.1, 1.4, 0.1]}
+  ],
+  "furniture": [
+    {"name": "Sofa", "type": "sofa", "width": 2.2, "depth": 0.9, "at": [0, 1.6], "facing": "E"},
+    {"name": "Coffee table", "type": "coffee_table", "width": 1.2, "depth": 0.6, "at": [1.3, 2.1], "facing": "E"},
+    {"name": "Armchair", "type": "armchair", "width": 0.85, "depth": 0.85, "at": [3.4, 3.2], "facing": "S"},
+    {"name": "TV unit", "type": "tv_unit", "width": 1.6, "depth": 0.45, "at": [4.55, 1.8], "facing": "W"},
+    {"name": "Bookcase", "type": "bookcase", "width": 1.0, "depth": 0.35, "at": [3.6, 0], "facing": "N"},
+    {"name": "Rug", "type": "rug", "width": 2.0, "depth": 1.6, "at": [1.0, 1.9]}
+  ]
+}

package/packs/operations-manager/skills/shift-roster/SKILL.md

@@ -32,7 +32,7 @@ the team.
   days and change you write is read from the check's per-person summary and its comparison
   with their original, run on the final rota. Never from memory of an earlier draft.
 - **Working files stay out of sight.** The check's input and any intermediate file go in a
-  temporary folder outside the working directory, or are deleted before you reply. Draw the
+  private temporary folder made for this run alone (`mktemp -d`, never a fixed path such as `/tmp/roster`, which another session can read or overwrite), and are deleted before you reply. Never overwrite a file the person gave you: write the corrected copy beside it under a plain name (`rota-fixed.csv`), and leave theirs as it was. Draw the
   week grid only when a drawing is asked for, or as the one extra file named in one line.
   Never leave anything running in the background; wait for it.
 - **Carry every field through.** Every column or note the person gave about a person or a
@@ -70,10 +70,11 @@ the team.
 4. **Check it, and fix every failure before showing anything.**
 
    ```bash
+   work=$(mktemp -d 2>/dev/null || mktemp -d ./.work.XXXXXX)   # a private folder for this run only
    # Claude Code
-   python3 "${CLAUDE_SKILL_DIR}/scripts/roster_check.py" "$TMPDIR/roster.json"
+   python3 "${CLAUDE_SKILL_DIR}/scripts/roster_check.py" "$work/roster.json"
    # Other IDEs (from the skill folder); add --svg only when a drawing is wanted
-   python3 scripts/roster_check.py /tmp/rota/roster.json --svg rota-week-of-2026-11-09.svg
+   python3 scripts/roster_check.py "$work/roster.json" --svg rota-week-of-2026-11-09.svg
    ```
 
    Exit 0 means no failures, 1 means a failure, and 2 means the input can't be read. Fix only
@@ -162,5 +163,7 @@ flagged in the reply. With no staff or no shifts at all, emit
 - ❌ **Searching every arrangement by hand.** Build one, check, fix what fails, five rounds at most.
 - ❌ **Reshuffling their rota** to fix three problems. Fix the three, and list them.
 - ❌ **Ignoring "don't put her on more than she needs".** A note is a rule.
+- ❌ **A fixed temporary path.** Two sessions at once share it, and one plan leaks into the other.
+- ❌ **Overwriting the person's own file.** They lose the version they sent.
 - ❌ **A JSON file and a drawing nobody asked for** left beside their files.
 - ❌ **"The script says…"** The manager wants the rota and what's wrong with it, not how it was checked.

package/packs/operations-manager/skills/shift-roster/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "shift-roster",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Build a staff rota for a week or a fortnight from who is available, what each shift needs and the working-time rules, and check it with a script before anyone sees it — every shift covered with the right skills, nobody double-booked, over their hours, short of rest between shifts or past the consecutive-day limit — drawn as a week grid. Use when a manager asks to \"make the rota\", \"build next week's schedule\", \"who should work which shift\", \"check this rota\", \"fill these shifts\", or has staff availability and shift needs for a shop, restaurant, clinic, warehouse or call centre.",
   "entrypoint": "SKILL.md",
   "deps": {