@iceinvein/agent-skills 0.10.0 → 0.10.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iceinvein/agent-skills",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "Install agent skills into AI coding tools",
   "author": "iceinvein",
   "license": "MIT",

package/skills/index.json

@@ -283,7 +283,7 @@
     "name": "sluice",
     "description": "Routes work by change shape into four channels (bypass, fast, main, deep) and applies only the rules each channel needs, so a one-line fix does not pay the cost of a multi-subsystem build. Carries seven rules as one-liners in the router and the full treatment in references read only on friction. Checks the finished plan with plan.sh validate rather than trusting it to memory, seeds the run state from it, keeps a deep run's task breakdown in .sluice/run.json so a statusline segment and one status command can answer where the run is, and closes each run with a ledger read out of the session transcript: elapsed, tools, tokens, and what each dispatched agent cost where the transcript recorded it. Claude Code only; stands down where the superpowers pipeline governs the repo.",
     "type": "prompt",
-    "version": "0.12.0"
+    "version": "0.12.1"
   },
   {
     "name": "temporal-coupling-detector",

package/skills/sluice/references/status.md

@@ -169,6 +169,7 @@ state file existing so a session with no run spawns no process at all:
 sluice_line=""
 if [ -n "$cwd" ] && [ -f "$cwd/.sluice/run.json" ]; then
   for sluice_sh in "$cwd/.claude/skills/sluice/scripts/status.sh" \
+                   "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/skills/sluice/scripts/status.sh" \
                    "$HOME/.claude/skills/sluice/scripts/status.sh"; do
     [ -f "$sluice_sh" ] || continue
     sluice_line=$(bash "$sluice_sh" line --full --dir "$cwd" 2>/dev/null)
@@ -187,7 +188,11 @@ if [ -n "$sluice_line" ]; then printf '%s\n' "$sluice_line"; fi
 short form makes it exit 1 on every render with no run live, which is the common
 case. `%s` rather than `%b`: the render already carries real escape bytes, and
 `%b` would reinterpret a backslash inside a task name. `$cwd` is
-`workspace.current_dir` from the JSON the harness sends on stdin. It renders as:
+`workspace.current_dir` from the JSON the harness sends on stdin. The configured
+config dir is read before the default because a session started with
+`CLAUDE_CONFIG_DIR` set installs the skill there, which is the one place a
+`$HOME/.claude` lookup will not find it; the two paths collapse to one when the
+variable is unset, at the price of a second `[ -f ]`. It renders as:
 
 ```
 ⧗ deep · sluice-cross-harness   ◷ 38m

package/skills/sluice/scripts/run-stats.sh

@@ -40,7 +40,14 @@ if [ -z "$TRANSCRIPT" ]; then
     exit 1
   fi
   # The session id is unique across projects, so glob rather than guess the slug.
-  TRANSCRIPT="$(ls "$HOME"/.claude/projects/*/"$sid".jsonl 2>/dev/null | head -1)"
+  # The harness writes under whichever config dir it was started with, so read
+  # CLAUDE_CONFIG_DIR first and fall back to the default: a machine that has run
+  # under both profiles keeps transcripts in both, and a miss under the
+  # configured one is not the end of the search.
+  for root in "${CLAUDE_CONFIG_DIR:-$HOME/.claude}" "$HOME/.claude"; do
+    TRANSCRIPT="$(ls "$root"/projects/*/"$sid".jsonl 2>/dev/null | head -1)"
+    [ -n "$TRANSCRIPT" ] && break
+  done
 fi
 
 if [ -z "$TRANSCRIPT" ] || [ ! -f "$TRANSCRIPT" ]; then

package/skills/sluice/skill.json

@@ -1,6 +1,6 @@
 {
   "name": "sluice",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "description": "Routes work by change shape into four channels (bypass, fast, main, deep) and applies only the rules each channel needs, so a one-line fix does not pay the cost of a multi-subsystem build. Carries seven rules as one-liners in the router and the full treatment in references read only on friction. Checks the finished plan with plan.sh validate rather than trusting it to memory, seeds the run state from it, keeps a deep run's task breakdown in .sluice/run.json so a statusline segment and one status command can answer where the run is, and closes each run with a ledger read out of the session transcript: elapsed, tools, tokens, and what each dispatched agent cost where the transcript recorded it. Claude Code only; stands down where the superpowers pipeline governs the repo.",
   "author": "iceinvein",
   "type": "prompt",