@monoes/monomindcli 2.16.2 → 2.16.3

package/.claude/skills/mastermind-idea/SKILL.md

@@ -13,7 +13,7 @@ This skill is invoked by `mastermind:master` or directly via `/mastermind:idea`.
 
 **File mode (default, `USE_MONOTASK=false`):**
 
-Invoke `Skill("mastermind-ideate", $ARGUMENTS)` immediately — it provides the same research, evaluation, elaboration, and task-decomposition pipeline with file-first storage (`docs/ideas/` and `docs/tasks/`). The rest of this skill is skipped in file mode.
+Invoke `Skill("mastermind:ideate", $ARGUMENTS)` immediately — it provides the same research, evaluation, elaboration, and task-decomposition pipeline with file-first storage (`docs/ideas/` and `docs/tasks/`). The rest of this skill is skipped in file mode.
 
 **Board mode (`USE_MONOTASK=true`):**
 
@@ -154,59 +154,38 @@ echo "==================================="
 
 ### Step 4 — Idea Manager Agent (Divergent Thinking)
 
-**Before spawning the Idea Manager**, run the registry-aware specialist selection to determine which agents to use. This replaces hardcoded agent types with the best available specialists for the prompt.
+**Before spawning the Idea Manager**, pick specialists from the shared agent index instead of hardcoded agent types (pick order in `mastermind-agent-select/SKILL.md`).
+
+**If `mcp__monomind__pick` is available**, call it twice — `{ task: prompt, kind: "agents", categories: ["marketing","specialized","design","testing"], top: 6 }` and `{ task: prompt, kind: "agents", categories: ["engineering","architecture","core","specialized"], top: 2 }` — merge the `agents.ranked[].name` values (unique, max 8) into `specialist_list`, and skip the Bash block below unless fewer than 2 came back.
 
 ```bash
-REGISTRY=".monomind/registry.json"
 PROMPT="$prompt"
-TOP_N=6
-
-# Select user/market/ops angle specialists
-CATEGORIES="marketing strategy product academic specialized"
-user_market_agents=$(jq \
-  --arg cats "$CATEGORIES" \
-  --arg kw "$(echo "$PROMPT" | tr '[:upper:]' '[:lower:]' | grep -oE '[a-z]{5,}' | sort -u | tr '\n' ' ')" \
-  --argjson n "$TOP_N" \
-  '[ (.agents // [])[] | select(.deprecated != true)
-     | select(.category as $c | ($cats | split(" ") | any(. == $c)))
-     | {name: .name, slug: .slug, category: .category,
-        score: (
-          (.name | ascii_downcase) as $n |
-          (.description // "" | ascii_downcase) as $desc |
-          # Score keyword matches against both name (weight 2) and description (weight 1) —
-          # name match is a stronger signal (mirrors master.md pick_domain_manager scoring).
-          # Bind each word to $w before contains(): piping into contains(.) rebinds "." to the
-          # piped value, which would silently match everything.
-          (if ($kw | length) > 0
-           then ([$kw | split(" ")[] | select(length > 0) | . as $w |
-                  (if ($n | contains($w)) then 2 else 0 end) +
-                  (if ($desc | contains($w)) then 1 else 0 end)
-                 ] | add // 0)
-           else 0 end)
-        )}
-   ] | sort_by(-.score) | unique_by(.slug) | .[0:$n] | [.[].name]' \
-  "$REGISTRY" 2>/dev/null)
-
-# Select technical angle specialists
-CATEGORIES="engineering development architecture"
-tech_agents=$(jq \
-  --arg cats "$CATEGORIES" \
-  --argjson n 3 \
-  '[ (.agents // [])[] | select(.deprecated != true)
-     | select(.category as $c | ($cats | split(" ") | any(. == $c)))
-     | {name: .name, slug: .slug}
-   ] | unique_by(.slug) | .[0:$n] | [.[].name]' \
-  "$REGISTRY" 2>/dev/null)
-
-# Merge: take top 6 from market/ops + top 2 from tech (cap at 8 total)
-# Both variables hold JSON arrays (no -r flag) — use jq -s add to merge properly
+
+# The shared agent index: Jev when configured, keyword ranking otherwise. It
+# only returns agents that exist.
+# Local only — never npx. Accept a binary only when its pick output is the
+# unified index (skill entries carry `source`); see mastermind-agent-select.
+mmpick() { for c in monomind ./node_modules/.bin/monomind; do
+    command -v "$c" >/dev/null 2>&1 || continue
+    out=$("$c" pick "$@" --json 2>/dev/null) || continue
+    printf '%s' "$out" | jq -e '[.skills.ranked[]? | has("source")] | (length > 0 and all)' \
+      >/dev/null 2>&1 && { printf '%s\n' "$out"; return 0; }
+  done; return 127; }
+pick_names() { mmpick -t "$1" --categories "$2" --top "$3" \
+    | jq -c '[.agents.ranked[].name]' 2>/dev/null; }
+
+# User/market/ops angle specialists, then technical angle specialists
+user_market_agents=$(pick_names "$PROMPT" "marketing specialized design testing" 6)
+tech_agents=$(pick_names "$PROMPT" "engineering architecture core specialized" 2)
+
+# Merge: top 6 market/ops + top 2 tech (cap at 8 total)
 specialist_list=$(jq -s 'add // [] | unique | .[0:8]' \
-  <(printf '%s' "$user_market_agents") \
-  <(printf '%s' "$tech_agents") 2>/dev/null)
+  <(printf '%s' "${user_market_agents:-[]}") \
+  <(printf '%s' "${tech_agents:-[]}") 2>/dev/null)
 
-# Fallback if registry missing or returned an empty array — need at least 2 specialists
+# Fallback if picking is unavailable or returned too few — need at least 2 specialists
 specialist_count=$(echo "$specialist_list" | jq 'length // 0' 2>/dev/null || echo 0)
-[ "$specialist_count" -lt 2 ] && specialist_list='["researcher","Trend Researcher","Growth Hacker","UX Researcher","Content Creator","Account Strategist"]'
+[ "${specialist_count:-0}" -lt 2 ] && specialist_list='["researcher","Launch Strategist","CRO Specialist","Competitive Content Strategist","Software Architect","Pricing Strategist"]'
 
 echo "Selected specialists: $specialist_list"
 ```
@@ -244,7 +223,7 @@ STEP 2 — SPAWN SPECIALISTS
 Spawn one Task agent per angle (all in parallel, mesh topology). Each agent receives the
 angle description, brain context, and project context, and must return a JSON array of ideas.
 
-The following specialist agents have been pre-selected from the registry as best-fit for this prompt.
+The following specialist agents have been pre-selected from the shared agent index as best-fit for this prompt.
 Spawn ALL of them in one message, assigning each a distinct angle:
 
 SPECIALISTS: ${specialist_list}
@@ -326,7 +305,7 @@ ideas_list=$(echo "$ideas_output_json" | jq -r \
 **CRITICAL — Variable substitution required for Step 5 Task call:**
 Before constructing the Task prompt below, read the literal UUID values from the `=== IDEA BOARD LITERAL VALUES ===` echo block (Step 3) and embed them as hard-coded strings. Also embed the full `brain_context`, `prompt`, and `ideas_list` (built above) as literal text. Replace every `${BOARD_ID}`, `${COL_EVALUATED}`, `${COL_ICED}`, `${COL_REJECTED}`, `${brain_context}`, `${prompt}`, `${project_name}`, `${date}`, and `${ideas_list}` with its actual value before calling Task — the agent receives unsubstituted `${...}` strings verbatim and silently skips every board update.
 
-Spawn a single `general-purpose` agent via the Task tool. Do NOT use `Product Manager` — that agent type lacks Bash tool access and cannot execute `monotask` CLI commands. The evaluator agent produces verdicts and executes all board updates directly via Bash.
+Spawn a single `general-purpose` agent via the Task tool. Do NOT substitute a specialist whose definition restricts `tools:` without Bash — it cannot execute `monotask` CLI commands. The evaluator agent produces verdicts and executes all board updates directly via Bash.
 
 ```javascript
 Task({
@@ -463,7 +442,7 @@ Spawn two agents in parallel via Task tool:
 ```javascript
 // Agent 1 — code explorer
 Task({
-  subagent_type: "feature-dev:code-explorer",
+  subagent_type: "Explore",
   description: "Elaboration: codebase constraints for dev ideas",
   run_in_background: true,
   prompt: `SAFETY CHECK: You are an elaboration agent. Do NOT call monotask board create, space create, or column create. Your only job is producing an ELABORATION_OUTPUT block — the outer skill writes to the board.
@@ -547,9 +526,10 @@ ELABORATION_OUTPUT
 END_ELABORATION_OUTPUT`
 })
 
-// Agent 2 — Product Manager
+// Agent 2 — feasibility assessor: mcp__monomind__pick({task: "feasibility assessment: <ops ideas>", kind: "agents", top: 1}) -> agents.ranked[0].name
+//   (no MCP: mmpick -t "feasibility assessment: <ops ideas>" --top 1 | jq -r '.agents.ranked[0].name'; fallback "general-purpose")
 Task({
-  subagent_type: "Product Manager",
+  subagent_type: "<picked agent>",
   description: "Elaboration: feasibility assessment for ops ideas",
   run_in_background: true,
   prompt: `SAFETY CHECK: You are an elaboration agent. Do NOT call monotask board create, space create, or column create. Your only job is producing an ELABORATION_OUTPUT block — the outer skill writes to the board.
@@ -725,52 +705,32 @@ After applying all user instructions, proceed to Step 6c with the remaining idea
 
 #### 6c. Task Decomposition
 
-**Select decomposition agents from the registry** before spawning. Run this selection once per track:
+**Select decomposition agents from the shared agent index** before spawning. With `mcp__monomind__pick`, call it once per track (`kind: "agents"`, `top: 1`, the categories below as an array) and use `agents.ranked[0].name`; otherwise run this selection once per track:
 
 ```bash
-REGISTRY=".monomind/registry.json"
-
-# Dev decomposition agent — pick the most relevant engineering/architecture specialist
-dev_decomp_agent=$(jq -r \
-  '[ (.agents // [])[] | select(.deprecated != true)
-     | select(.category == "engineering" or .category == "architecture")
-     | {name: .name,
-        score: (.name | ascii_downcase |
-                if contains("architect") then 3
-                elif contains("backend") then 2
-                elif contains("mobile") then 2
-                elif contains("frontend") then 2
-                elif contains("security") then 2
-                elif contains("data") then 2
-                else 1 end
-               )}
-   ] | sort_by(-.score) | .[0].name // "Software Architect"' \
-  "$REGISTRY" 2>/dev/null)
+# The shared agent index picks the best decomposer for each track.
+# Local only — never npx. Accept a binary only when its pick output is the
+# unified index (skill entries carry `source`); see mastermind-agent-select.
+mmpick() { for c in monomind ./node_modules/.bin/monomind; do
+    command -v "$c" >/dev/null 2>&1 || continue
+    out=$("$c" pick "$@" --json 2>/dev/null) || continue
+    printf '%s' "$out" | jq -e '[.skills.ranked[]? | has("source")] | (length > 0 and all)' \
+      >/dev/null 2>&1 && { printf '%s\n' "$out"; return 0; }
+  done; return 127; }
+pick_one() { mmpick -t "$1" --categories "$2" --top 1 \
+    | jq -r '.agents.ranked[0].name // empty' 2>/dev/null; }
+
+dev_decomp_agent=$(pick_one "decompose into engineering tasks: $dev_ideas_list" "engineering architecture")
 dev_decomp_agent="${dev_decomp_agent:-Software Architect}"
 
-# Ops decomposition agent — pick the most relevant strategy/sales/product specialist
-ops_decomp_agent=$(jq -r \
-  '[ (.agents // [])[] | select(.deprecated != true)
-     | select(.category == "strategy" or .category == "sales" or .category == "product" or .category == "marketing")
-     | {name: .name,
-        score: (.name | ascii_downcase |
-                if contains("product manager") then 4
-                elif contains("launch") then 3
-                elif contains("outbound") then 3
-                elif contains("deal") then 3
-                elif contains("pricing") then 3
-                elif contains("growth") then 2
-                else 1 end
-               )}
-   ] | sort_by(-.score) | .[0].name // "Product Manager"' \
-  "$REGISTRY" 2>/dev/null)
-ops_decomp_agent="${ops_decomp_agent:-Product Manager}"
+ops_decomp_agent=$(pick_one "decompose into go-to-market and operations tasks: $ops_ideas_list" "marketing specialized")
+ops_decomp_agent="${ops_decomp_agent:-Launch Strategist}"
 
 echo "Dev decomp: $dev_decomp_agent | Ops decomp: $ops_decomp_agent"
 ```
 
 **CRITICAL — Variable substitution required for Step 6c Task calls:**
-Before constructing each Task prompt, replace `${brain_context}`, `${prompt}`, `${project_name}`, `${dev_ideas_elaborated}`, and `${ops_ideas_elaborated}` with actual literal text. Also substitute the `subagent_type` values: replace `dev_decomp_agent` and `ops_decomp_agent` with the string values echoed by the registry selection above (e.g. `"Software Architect"`). Build those lists from the VERDICTS_OUTPUT and ELABORATION_OUTPUT results:
+Before constructing each Task prompt, replace `${brain_context}`, `${prompt}`, `${project_name}`, `${dev_ideas_elaborated}`, and `${ops_ideas_elaborated}` with actual literal text. Also substitute the `subagent_type` values: replace `dev_decomp_agent` and `ops_decomp_agent` with the string values echoed by the selection above (e.g. `"Software Architect"`). Build those lists from the VERDICTS_OUTPUT and ELABORATION_OUTPUT results:
 
 ```bash
 # Collect IDs of cards iced during elaboration (blocking_issue was set) — exclude from decomposition.
@@ -804,7 +764,7 @@ ops_ideas_elaborated=$(echo "$verdicts_output_json" | jq -r \
 ```javascript
 // Dev decomposition agent (only if dev_ideas_elaborated is non-empty)
 Task({
-  subagent_type: dev_decomp_agent,  // value from registry selection above
+  subagent_type: dev_decomp_agent,  // value from the selection above
   description: "Task decomposition: dev ideas for " + project_name,
   run_in_background: true,
   prompt: `SAFETY CHECK: You are a decomposition agent. You must NOT call monotask board create, space create, or column create. Your only job is producing a TASKS_OUTPUT block — the outer skill creates the cards. If you are unsure of any card ID, list it as "UNKNOWN" rather than inventing a value.
@@ -843,7 +803,7 @@ END_TASKS_OUTPUT`
 
 // Ops decomposition agent (only if ops_ideas_elaborated is non-empty)
 Task({
-  subagent_type: ops_decomp_agent,  // value from registry selection above
+  subagent_type: ops_decomp_agent,  // value from the selection above
   description: "Task decomposition: ops ideas for " + project_name,
   run_in_background: true,
   prompt: `SAFETY CHECK: You are a decomposition agent. You must NOT call monotask board create, space create, or column create. Your only job is producing a TASKS_OUTPUT block — the outer skill creates the cards. If you are unsure of any card ID, list it as "UNKNOWN" rather than inventing a value.

package/.claude/skills/mastermind-import/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-import
 description: Mastermind import — import an org from a portable ZIP archive exported by mastermind:export. Previews the archive contents, shows agent plans (create/update/skip), lets you choose a collision strategy, and applies the import to the local .monomind/orgs/ directory. Mirrors CompanyImport.tsx.
 type: domain-skill
 default_mode: confirm
+pick: low
 ---
 
 # Mastermind Import
 
-This skill is invoked by `mastermind:import` or directly via `/mastermind:import`.
+This skill is invoked by `mastermind:import` or directly via `/mastermind-import`.
 
 ---
 

package/.claude/skills/mastermind-inbox/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-inbox
 description: Mastermind inbox — unified view of everything that needs human attention across all orgs: pending approvals, running heartbeats, active task assignments, and budget alerts. The single place to check before starting work.
 type: domain-skill
 default_mode: auto
+pick: low
 ---
 
 # Mastermind Inbox
 
-This skill is invoked by `mastermind:inbox` or directly via `/mastermind:inbox`.
+This skill is invoked by `mastermind:inbox` or directly via `/mastermind-inbox`.
 
 ---
 
@@ -196,7 +197,7 @@ From the inbox, the user can directly:
 /mastermind:approvev1 --org <org> --action approve --approval-id <id>
 
 # Stop a running agent:
-/mastermind:agents --org <org> --action pause --agent-id <id>
+/mastermind-agents --org <org> --action pause --agent-id <id>
 
 # Check costs:
 /mastermind:costs --org <org> --action report

package/.claude/skills/mastermind-instance/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-instance
 description: Mastermind instance — global instance-level settings including scheduler heartbeat management across all orgs, system-wide configuration, and cross-org health overview.
 type: domain-skill
 default_mode: auto
+pick: low
 ---
 
 # Mastermind Instance
 
-This skill is invoked by `mastermind:instance` or directly via `/mastermind:instance`.
+This skill is invoked by `mastermind:instance` or directly via `/mastermind-instance`.
 
 ---
 
@@ -213,7 +214,7 @@ echo "  Running agents:   $total_running"
 echo "  Pending approvals:$total_pending"
 echo ""
 [ "$total_running" -gt 0 ] && echo "  ✓ System is active." || echo "  ◌ No agents running."
-[ "$total_pending" -gt 0 ] && echo "  ⚠ $total_pending approval(s) need attention. Run /mastermind:inbox."
+[ "$total_pending" -gt 0 ] && echo "  ⚠ $total_pending approval(s) need attention. Run /mastermind-inbox."
 ```
 
 ---

package/.claude/skills/mastermind-invite-landing/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-invite-landing
 description: Mastermind invite-landing — accept an org invite as a human member or as an agent. Validates the invite token, presents org/role info, and processes join as human (name/email) or as an agent (adapter type, model, agent name, config). Mirrors InviteLanding.tsx.
 type: domain-skill
 default_mode: confirm
+pick: low
 ---
 
 # Mastermind Invite Landing
 
-This skill is invoked by `mastermind:invite-landing` or directly via `/mastermind:invite-landing`.
+This skill is invoked by `mastermind:invite-landing` or directly via `/mastermind-invite-landing`.
 
 ---
 
@@ -196,7 +197,7 @@ echo "  Adapter:     $adapterType / $modelId"
 echo "  Org:         $org_name"
 echo "  Joined at:   $ts"
 echo ""
-echo "  View agent: /mastermind:agent-detail --org $org_name --agent-id $agentId"
+echo "  View agent: /mastermind-agent-detail --org $org_name --agent-id $agentId"
 ```
 
 ### status

package/.claude/skills/mastermind-invites/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-invites
 description: Mastermind invites — manage org invitations and join request queue. Create/revoke invites with role assignment, view invite history, review pending join requests (human and agent), and approve or reject them. Merges CompanyInvites and JoinRequestQueue pages.
 type: domain-skill
 default_mode: confirm
+pick: low
 ---
 
 # Mastermind Invites
 
-This skill is invoked by `mastermind:invites` or directly via `/mastermind:invites`.
+This skill is invoked by `mastermind:invites` or directly via `/mastermind-invites`.
 
 ---
 
@@ -214,7 +215,7 @@ jq --arg id "$request_id" --arg role "$reqRole" --arg ts "$ts" \
 
 echo "Join request '$request_id' approved."
 echo "  Role: $reqRole  |  Joined: $ts"
-echo "  Member added. View members: /mastermind:access --org $org_name --action list"
+echo "  Member added. View members: /mastermind-access --org $org_name --action list"
 ```
 
 ### reject-join

package/.claude/skills/mastermind-issue-detail/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-issue-detail
 description: Mastermind issue-detail — deep per-issue/task inspection and management. Show thread summary, run history, comments, sub-issues, file attachments, assign, close, and recovery actions for a single task within an org.
 type: domain-skill
 default_mode: auto
+pick: low
 ---
 
 # Mastermind Issue Detail
 
-This skill is invoked by `mastermind:issue-detail` or directly via `/mastermind:issue-detail`.
+This skill is invoked by `mastermind:issue-detail` or directly via `/mastermind-issue-detail`.
 
 ---
 
@@ -52,7 +53,7 @@ orgFile=".monomind/orgs/${org_name}.json"
 [ ! -f "$orgFile" ] && { echo "ERROR: Org '${org_name}' not found."; exit 1; }
 
 issuesFile=".monomind/orgs/${org_name}-issues.json"
-[ ! -f "$issuesFile" ] && { echo "ERROR: No issues file for org '$org_name'. Create issues via /mastermind:issues --action create."; exit 1; }
+[ ! -f "$issuesFile" ] && { echo "ERROR: No issues file for org '$org_name'. Create issues via /mastermind-issues --action create."; exit 1; }
 
 issueDef=$(jq -r --arg id "$issue_id" '(.issues // [])[] | select(.id == $id or .slug == $id)' "$issuesFile")
 [ -z "$issueDef" ] && { echo "ERROR: Issue '$issue_id' not found in org '$org_name'."; exit 1; }
@@ -210,7 +211,7 @@ jq -r --arg pid "$resolvedId" '(.issues // [])[] | select(.parentId == $pid) |
 done
 
 echo ""
-echo "To create a sub-issue: /mastermind:issues --org $org_name --action create --title '<title>' --parent-id $issue_id"
+echo "To create a sub-issue: /mastermind-issues --org $org_name --action create --title '<title>' --parent-id $issue_id"
 ```
 
 ### attachments

package/.claude/skills/mastermind-issues/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-issues
 description: Mastermind issues — list, create, update, and close org-level issues (tasks/tickets) with search, assignee, status, and workspace filters. Mirrors Issues.tsx. For personal assigned issues use mastermind:my-issues; for issue detail use mastermind:issue-detail.
 type: domain-skill
 default_mode: auto
+pick: low
 ---
 
 # Mastermind Issues
 
-This skill is invoked by `mastermind:issues` or directly via `/mastermind:issues`.
+This skill is invoked by `mastermind:issues` or directly via `/mastermind-issues`.
 
 ---
 
@@ -132,8 +133,8 @@ print(f"\n  Showing {len(issues)} issue(s).")
 PYEOF
 
 echo ""
-echo "  Create: /mastermind:issues --org $org_name --action create --title 'My Issue'"
-echo "  Detail: /mastermind:issue-detail --org $org_name --issue-id <id>"
+echo "  Create: /mastermind-issues --org $org_name --action create --title 'My Issue'"
+echo "  Detail: /mastermind-issue-detail --org $org_name --issue-id <id>"
 ```
 
 ### search

package/.claude/skills/mastermind-join-queue/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-join-queue
 description: Mastermind join-queue — lists pending join requests for an org, approves or rejects them, and filters by request type (human/agent/all) and status. Mirrors JoinRequestQueue.tsx.
 type: domain-skill
 default_mode: auto
+pick: low
 ---
 
 # Mastermind Join Queue
 
-This skill is invoked by `mastermind:join-queue` or directly via `/mastermind:join-queue`.
+This skill is invoked by `mastermind:join-queue` or directly via `/mastermind-join-queue`.
 
 ---
 
@@ -54,7 +55,7 @@ echo "────────────────────────
 if [ ! -f "$joinFile" ]; then
   echo "  No join requests found."
   echo ""
-  echo "  Approve: /mastermind:join-queue --org $org_name --action approve --request-id <id>"
+  echo "  Approve: /mastermind-join-queue --org $org_name --action approve --request-id <id>"
   exit 0
 fi
 
@@ -86,8 +87,8 @@ print(f"\n  Total: {len(filtered)} request(s) (status={status_f}, type={type_f})
 PYEOF
 
 echo ""
-echo "  Approve: /mastermind:join-queue --org $org_name --action approve --request-id <id>"
-echo "  Reject:  /mastermind:join-queue --org $org_name --action reject  --request-id <id>"
+echo "  Approve: /mastermind-join-queue --org $org_name --action approve --request-id <id>"
+echo "  Reject:  /mastermind-join-queue --org $org_name --action reject  --request-id <id>"
 ```
 
 ### approve

package/.claude/skills/mastermind-liveness/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-liveness
 description: Mastermind liveness — enforce the non-terminal issue liveness contract for agent-owned work. Checks if every in_progress/blocked/in_review issue has a valid action path (active run, queued wake, explicit blocker, or recovery action). Can checkout an issue to an agent run, release checkout, trigger wakeup decisions, and file explicit recovery actions for stalled issues. Based on Paperclip's execution-semantics.md liveness contract.
 type: domain-skill
 default_mode: auto
+pick: low
 ---
 
 # Mastermind Liveness
 
-This skill is invoked by `mastermind:liveness` or directly via `/mastermind:liveness`.
+This skill is invoked by `mastermind:liveness` or directly via `/mastermind-liveness`.
 
 ---
 
@@ -230,7 +231,7 @@ if stalled:
         print(f"    {iid}: [{s}] {t}")
         print(f"      → {p}")
     print()
-    print("  Fix: /mastermind:liveness --org <org> --action recover --issue-id <id> --reason 'execution path lost'")
+    print("  Fix: /mastermind-liveness --org <org> --action recover --issue-id <id> --reason 'execution path lost'")
 else:
     print("  ✓ No stalled issues.")
 
@@ -265,7 +266,7 @@ for iss in issues:
         existing = iss.get("checkoutRunId")
         if existing and existing != runId:
             print(f"  CONFLICT: Issue already checked out by run {existing}")
-            print(f"  Release first: /mastermind:liveness --org <org> --action release --issue-id {iid}")
+            print(f"  Release first: /mastermind-liveness --org <org> --action release --issue-id {iid}")
             sys.exit(1)
         iss["checkoutRunId"]  = runId
         iss["executionRunId"] = runId
@@ -430,7 +431,7 @@ for iss in issues:
         print(f"  Issue {iid} → status: blocked (pending recovery)")
         print(f"  Owner: {owner}")
         print(f"  Cause: {cause}")
-        print(f"  Resolve with: /mastermind:liveness --org <org> --action checkout --issue-id {iid} --agent-id <id> --run-id <id>")
+        print(f"  Resolve with: /mastermind-liveness --org <org> --action checkout --issue-id {iid} --agent-id <id> --run-id <id>")
         sys.exit(0)
 
 print(f"  ERROR: Issue '{iid}' not found.")

package/.claude/skills/mastermind-monitor/SKILL.md

@@ -7,7 +7,7 @@ default_mode: confirm
 
 # Mastermind Monitor
 
-Invoked via `mastermind:monitor` or `/mastermind:monitor`.
+Invoked via `mastermind:monitor` or `/mastermind-monitor`.
 
 A monitor is a named, forever-running task executor. It polls one or more task sources on a configurable interval, claims matching tasks, hands them off to a Claude agent for execution, posts back results as comments/status updates, and self-reschedules via `ScheduleWakeup`.
 
@@ -99,7 +99,7 @@ cat > "$cfg" <<EOF
 EOF
 
 echo "Monitor '$name' created."
-echo "Add sources with: /mastermind:monitor --action add-source --name $name --source linear ..."
+echo "Add sources with: /mastermind-monitor --action add-source --name $name --source linear ..."
 echo "Then start the tick loop."
 ```
 
@@ -107,7 +107,7 @@ After creating the config, if at least one source was provided (via `--source` +
 
 Then **immediately call `ScheduleWakeup`** with:
 - `delaySeconds`: 10 (first tick almost immediately)
-- `prompt`: `/mastermind:monitor --action tick --name <name>`
+- `prompt`: `/mastermind-monitor --action tick --name <name>`
 - `reason`: `First tick for monitor: <name>`
 
 ---
@@ -138,7 +138,7 @@ echo "Monitor '$name' is now: $new_status"
 
 If `action=resume`, call `ScheduleWakeup`:
 - `delaySeconds`: 10
-- `prompt`: `/mastermind:monitor --action tick --name <name>`
+- `prompt`: `/mastermind-monitor --action tick --name <name>`
 - `reason`: `Resuming monitor: <name>`
 
 ---
@@ -339,7 +339,7 @@ in_flight_count=${in_flight_count:-0}
 if [ "$in_flight_count" -ge "$max_concurrent" ]; then
   echo "[$name] In-flight ($in_flight_count) >= max_concurrent ($max_concurrent) — skipping claim this tick."
   # Reschedule next tick — do this BEFORE exit so the loop survives
-  # ScheduleWakeup: delaySeconds=poll_interval, prompt="/mastermind:monitor --action tick --name <name>",
+  # ScheduleWakeup: delaySeconds=poll_interval, prompt="/mastermind-monitor --action tick --name <name>",
   #   reason="Monitor <name> in-flight throttle — will retry next tick"
   exit 0
 fi
@@ -1068,7 +1068,7 @@ Always the last step, regardless of whether a task was found/executed.
 
 Call `ScheduleWakeup` with:
 - `delaySeconds`: value of `poll_interval` from config (default 120)
-- `prompt`: `/mastermind:monitor --action tick --name <name>`
+- `prompt`: `/mastermind-monitor --action tick --name <name>`
 - `reason`: `Monitor <name> polling every <poll_interval>s (<N sources>)`
 
 This is what makes the monitor run forever. The only way to stop it is to set `status=stopped` or `status=paused` — the tick checks this at the top of Step 2.
@@ -1198,38 +1198,38 @@ If `caller` is not "command", follow `mastermind-protocol/SKILL.md` Brain Write
 
 ```bash
 # Create a monitor watching GitHub issues assigned to you
-/mastermind:monitor --action start --name dev-watcher \
+/mastermind-monitor --action start --name dev-watcher \
   --source github --project monoes/monomind --user nokhodian \
   --label ai-agent --agent coder --interval 120
 
 # Add a Linear source to an existing monitor
-/mastermind:monitor --action add-source --name dev-watcher \
+/mastermind-monitor --action add-source --name dev-watcher \
   --source linear --team ENG --user your@email.com \
   --state Todo --label ai-agent
 
 # Add a monotask board source
-/mastermind:monitor --action add-source --name dev-watcher \
+/mastermind-monitor --action add-source --name dev-watcher \
   --source monotask --project monomind-tasks-dev \
   --state Todo --label role:ai-agent
 
 # Add a filesystem folder source
-/mastermind:monitor --action add-source --name dev-watcher \
+/mastermind-monitor --action add-source --name dev-watcher \
   --source filesystem --folder ./tasks
 
 # Check status
-/mastermind:monitor --action status --name dev-watcher
+/mastermind-monitor --action status --name dev-watcher
 
 # List all monitors
-/mastermind:monitor
+/mastermind-monitor
 
 # Pause (stops auto-rescheduling after current tick)
-/mastermind:monitor --action pause --name dev-watcher
+/mastermind-monitor --action pause --name dev-watcher
 
 # Resume (re-enters the tick loop)
-/mastermind:monitor --action resume --name dev-watcher
+/mastermind-monitor --action resume --name dev-watcher
 
 # Stop permanently
-/mastermind:monitor --action stop --name dev-watcher
+/mastermind-monitor --action stop --name dev-watcher
 ```
 
 ---

package/.claude/skills/mastermind-my-issues/SKILL.md

@@ -3,11 +3,12 @@ name: mastermind-my-issues
 description: Mastermind my-issues — filtered issue queue scoped to the current operator or a specific assignee. Lists open and in-progress issues, supports self-assign and unassign. Mirrors MyIssues.tsx.
 type: domain-skill
 default_mode: auto
+pick: low
 ---
 
 # Mastermind My Issues
 
-This skill is invoked by `mastermind:my-issues` or directly via `/mastermind:my-issues`.
+This skill is invoked by `mastermind:my-issues` or directly via `/mastermind-my-issues`.
 
 ---