@amsterdamdatalabs/enact-extensions 0.1.5 → 0.1.8

package/extensions/cmux/skills/cmux/SKILL.md

@@ -1,82 +0,0 @@
----
-name: cmux
-description: End-user control of cmux topology and routing (windows, workspaces, panes/surfaces, focus, moves, reorder, identify, trigger flash). Use when automation needs deterministic placement and navigation in a multi-pane cmux layout.
----
-
-# cmux Core Control
-
-Use this skill to control non-browser cmux topology and routing.
-
-## Core Concepts
-
-- Window: top-level macOS cmux window.
-- Workspace: tab-like group within a window.
-- Pane: split container in a workspace.
-- Surface: a tab within a pane (terminal or browser panel).
-
-## Fast Start
-
-```bash
-# identify current caller context
-cmux identify --json
-
-# list topology
-cmux list-windows
-cmux list-workspaces
-cmux list-panes
-cmux list-pane-surfaces --pane pane:1
-
-# create/focus/move
-cmux new-workspace
-cmux new-split right --panel pane:1
-cmux move-surface --surface surface:7 --pane pane:2 --focus true
-cmux split-off --surface surface:7 right
-cmux reorder-surface --surface surface:7 --before surface:3
-
-# attention cue
-cmux trigger-flash --surface surface:7
-```
-
-## Settings and Docs
-
-Use `cmux docs settings` before changing cmux-owned settings. It prints the docs URL, schema URL, raw GitHub resources, cmux.json paths, and reload command.
-
-```bash
-cmux docs settings
-cmux settings path
-```
-
-cmux-owned settings live in `~/.config/cmux/cmux.json`. Legacy `~/.config/cmux/settings.json` and `~/Library/Application Support/com.cmuxterm.app/settings.json` files are read only as fallback for missing keys. Before editing, copy any existing `cmux.json` file to a timestamped `.bak` next to it so the user can revert. Edit the user file, then reload:
-
-```bash
-cmux reload-config
-```
-
-`cmux reload-config` reloads both `cmux.json` and Ghostty config (`~/.config/ghostty/config`) and refreshes terminals in place. No app restart needed.
-
-Use cmux settings for app behavior, sidebar, notifications, browser behavior, automation, workspace colors, and cmux-owned shortcuts. Terminal rendering settings such as font, cursor style, theme, scrollback, background transparency (`background-opacity`), and blur (`background-blur`) belong in Ghostty config at `~/.config/ghostty/config`.
-
-Open the UI when useful:
-
-```bash
-cmux settings
-cmux settings cmux-json
-cmux settings shortcuts
-```
-
-## Handle Model
-
-- Default output uses short refs: `window:N`, `workspace:N`, `pane:N`, `surface:N`.
-- UUIDs are still accepted as inputs.
-- Request UUID output only when needed: `--id-format uuids|both`.
-
-## Deep-Dive References
-
-| Reference | When to Use |
-|-----------|-------------|
-| [references/handles-and-identify.md](references/handles-and-identify.md) | Handle syntax, self-identify, caller targeting |
-| [references/windows-workspaces.md](references/windows-workspaces.md) | Window/workspace lifecycle and reorder/move |
-| [references/panes-surfaces.md](references/panes-surfaces.md) | Splits, surfaces, move/reorder, focus routing |
-| [references/trigger-flash-and-health.md](references/trigger-flash-and-health.md) | Flash cue and surface health checks |
-
-Use the bundled `cmux-workspace` companion skill when the task is workspace-scoped terminal automation or sibling-surface coordination rather than global topology control. The broader cmux project also ships browser, settings, markdown, and diagnostics companion skills that can be vendored into this bundle separately.

package/extensions/cmux/skills/cmux/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "cmux Core"
-  short_description: "Control windows/workspaces/panes/surfaces and routing with cmux CLI."
-  default_prompt: "Use this skill to inspect and manipulate cmux topology: identify context, target handles, create/focus/move/reorder windows/workspaces/panes/surfaces, and use trigger-flash for visual confirmation."

package/extensions/cmux/skills/cmux/references/handles-and-identify.md

@@ -1,35 +0,0 @@
-# Handles and Identify
-
-Use `identify` and short handles for deterministic automation targeting.
-
-## Handle Inputs
-
-Most v2-backed commands accept:
-- UUID
-- short ref (`window:N`, `workspace:N`, `pane:N`, `surface:N`)
-- index (where legacy/index-based commands still allow it)
-
-## Self Identify
-
-```bash
-cmux identify --json
-```
-
-Returns current focused topology plus optional caller resolution.
-
-## Caller Override
-
-```bash
-cmux identify --workspace workspace:2
-cmux identify --workspace workspace:2 --surface surface:8
-```
-
-Useful for agents that need to route relative actions from a known caller anchor.
-
-## Output Shaping
-
-```bash
-cmux --json identify
-cmux --json --id-format both identify
-cmux --json --id-format uuids identify
-```

package/extensions/cmux/skills/cmux/references/panes-surfaces.md

@@ -1,37 +0,0 @@
-# Panes and Surfaces
-
-Split layout, surface creation, focus, move, and reorder.
-
-## Inspect
-
-```bash
-cmux list-panes
-cmux list-pane-surfaces --pane pane:1
-```
-
-## Create Splits/Surfaces
-
-```bash
-cmux new-split right --panel pane:1
-cmux new-surface --type terminal --pane pane:1
-cmux new-surface --type browser --pane pane:1 --url https://example.com
-```
-
-## Focus and Close
-
-```bash
-cmux focus-pane --pane pane:2
-cmux focus-panel --panel surface:7
-cmux close-surface --surface surface:7
-```
-
-## Move/Reorder Surfaces
-
-```bash
-cmux move-surface --surface surface:7 --pane pane:2 --focus true
-cmux move-surface --surface surface:7 --workspace workspace:2 --window window:1 --after surface:4
-cmux split-off --surface surface:7 right
-cmux reorder-surface --surface surface:7 --before surface:3
-```
-
-Surface identity is stable across move, reorder, and split-off operations. Layout commands are focus-neutral by default; pass `--focus true` only when you want the moved or created surface selected.

package/extensions/cmux/skills/cmux/references/trigger-flash-and-health.md

@@ -1,23 +0,0 @@
-# Trigger Flash and Surface Health
-
-Operational checks useful in automation loops.
-
-## Trigger Flash
-
-Flash a surface or workspace to provide visual confirmation in UI:
-
-```bash
-cmux trigger-flash --surface surface:7
-cmux trigger-flash --workspace workspace:2
-```
-
-## Surface Health
-
-Use health output to detect hidden, detached, or non-windowed surfaces:
-
-```bash
-cmux surface-health
-cmux surface-health --workspace workspace:2
-```
-
-Use this before routing focused input if UI state may be stale.

package/extensions/cmux/skills/cmux/references/windows-workspaces.md

@@ -1,31 +0,0 @@
-# Windows and Workspaces
-
-Window and workspace lifecycle and ordering operations.
-
-## Inspect
-
-```bash
-cmux list-windows
-cmux current-window
-cmux list-workspaces
-cmux current-workspace
-```
-
-## Create/Focus/Close
-
-```bash
-cmux new-window
-cmux focus-window --window window:2
-cmux close-window --window window:2
-
-cmux new-workspace
-cmux select-workspace --workspace workspace:4
-cmux close-workspace --workspace workspace:4
-```
-
-## Reorder and Move
-
-```bash
-cmux reorder-workspace --workspace workspace:4 --before workspace:2
-cmux move-workspace-to-window --workspace workspace:4 --window window:1
-```

package/extensions/cmux/skills/cmux-vm-monitor/SKILL.md

@@ -1,122 +0,0 @@
----
-name: cmux-vm-monitor
-description: >-
-  Runs a remote VM pane with local monitoring and steering via cmux. Use when
-  the user wants SSH into a VM, launch work in a dedicated pane, send a long
-  autonomous goal, and schedule local periodic check-ins that inspect the VM
-  pane and wake the local steering pane without moving the actual coding off
-  the VM.
----
-
-# cmux VM monitor
-
-Use this skill when the user wants:
-
-- actual coding and building on a VM
-- the current local machine to remain the monitor and steering surface
-- cmux-driven pane automation instead of manual switching
-- periodic local check-ins against the remote Codex pane
-
-## Contract
-
-- The VM does the coding.
-- The local machine does the scheduling, pane inspection, and steering.
-- The local monitor does not talk to the VM pane. It only wakes the local pane with an instruction to inspect the VM and act.
-- Prefer `cmux send` followed by `cmux send-key tab` for local wake injection as plain queued text, not as a shell wrapper like `printf`.
-- Do not assume pane ids are stable. Re-identify the workspace, pane, and surface before acting.
-- Keep the wake message explicit enough that the local agent gets the exact cmux command sequence to run: inspect VM, ask for summary, decide `nothing | steer | stop`.
-
-## Layout pattern
-
-1. Identify the current workspace and panes.
-2. Reuse an existing right-side helper pane when possible.
-3. SSH into the VM inside that pane.
-4. Start `codex` in the target repo on the VM.
-5. Send the long-form goal from the local machine into the VM Codex pane.
-6. Run a local monitor loop that inspects the VM pane every N minutes and wakes the local pane.
-
-## Fast start
-
-```bash
-# 1) Find the active workspace and right pane
-cmux identify --json
-cmux list-panes --workspace workspace:1 --json
-cmux list-pane-surfaces --workspace workspace:1 --pane pane:2 --json
-
-# 2) Inspect the remote pane
-cmux capture-pane --workspace workspace:1 --surface surface:2 --lines 120
-
-# 3) Drive the pane
-cmux send --workspace workspace:1 --surface surface:2 "cd /root/Documents/enact-agent && codex --yolo"
-cmux send-key --workspace workspace:1 --surface surface:2 enter
-```
-
-## Monitor loop
-
-Use the bundled script:
-
-```bash
-extensions/skills/cmux-vm-monitor/scripts/codex_vm_monitor.sh
-```
-
-Default behavior:
-
-- captures the VM Codex pane locally
-- appends a local log entry
-- injects a wake message into the local pane with the exact follow-up cmux commands
-- does not send any command to the VM pane
-
-Environment variables:
-
-- `CMUX_MONITOR_WORKSPACE`
-- `CMUX_MONITOR_SURFACE`
-- `CMUX_MONITOR_LINES`
-- `CMUX_MONITOR_LOG`
-- `CMUX_MONITOR_WAKE_MESSAGE`
-
-Example one-shot run:
-
-```bash
-CMUX_MONITOR_WORKSPACE=workspace:1 \
-CMUX_MONITOR_SURFACE=surface:2 \
-bash extensions/skills/cmux-vm-monitor/scripts/codex_vm_monitor.sh
-```
-
-Example local scheduler:
-
-```bash
-nohup bash -lc 'sleep 300; while true; do \
-  bash extensions/skills/cmux-vm-monitor/scripts/codex_vm_monitor.sh; \
-  sleep 1800; \
-done' >/tmp/codex_vm_monitor.runner.log 2>&1 &
-```
-
-This is intentionally local. Do not install the scheduler on the VM unless the user explicitly asks.
-
-## Wake contract
-
-The monitor is intentionally simple:
-
-- capture the VM pane
-- log what it saw locally
-- wake the local pane with a precise instruction
-- include the exact `cmux capture-pane`, `cmux send`, and `cmux send-key Enter` sequence for the target VM surface
-- let the local agent decide whether to do `nothing`, `steer`, or `stop`
-
-Do not put VM-side steering logic into the monitor script itself.
-
-## Long-goal injection pattern
-
-Send the goal text as a single paste payload, then submit separately:
-
-```bash
-cmux send --workspace workspace:1 --surface surface:2 "<goal text>"
-cmux send-key --workspace workspace:1 --surface surface:2 enter
-```
-
-After submission, confirm the pane moved into an active state with `cmux capture-pane`.
-
-## References
-
-- Use [references/cmux-commands.md](references/cmux-commands.md) for the exact commands that worked in this pattern.
-- Use [scripts/codex_vm_monitor.sh](scripts/codex_vm_monitor.sh) instead of retyping the monitor loop.

package/extensions/cmux/skills/cmux-vm-monitor/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "cmux VM Codex Monitor"
-  short_description: "Run Codex on a VM pane and monitor it locally through cmux."
-  default_prompt: "Use this skill to drive a Codex session running on a remote VM pane through cmux, send a long goal into the VM pane, and set up a local periodic monitor that captures the pane and only nudges for a summary when Codex is idle."

package/extensions/cmux/skills/cmux-vm-monitor/references/cmux-commands.md

@@ -1,66 +0,0 @@
-# cmux commands for local-monitor / VM-Codex runs
-
-## Topology and targeting
-
-```bash
-cmux identify --json
-cmux list-panes --workspace workspace:1 --json
-cmux list-pane-surfaces --workspace workspace:1 --pane pane:2 --json
-```
-
-Use these before every mutating step. Pane and surface refs can change across sessions.
-
-## Inspect the VM pane
-
-```bash
-cmux capture-pane --workspace workspace:1 --surface surface:2 --lines 120
-```
-
-Use for:
-
-- checking whether SSH is already connected
-- checking whether Codex is in the TUI
-- checking whether Codex is busy or idle
-- reading the latest progress snapshot from the VM
-
-## Send text, then submit separately
-
-Preferred pattern:
-
-```bash
-cmux send --workspace workspace:1 --surface surface:2 "cd /root/Documents/enact-agent && codex --yolo"
-cmux send-key --workspace workspace:1 --surface surface:2 enter
-```
-
-This is safer than depending on embedded trailing newlines in the payload.
-
-## Launch or relaunch the VM task
-
-```bash
-cmux send --workspace workspace:1 --surface surface:2 "ssh root@srv1349818.walrus-morray.ts.net"
-cmux send-key --workspace workspace:1 --surface surface:2 enter
-
-cmux send --workspace workspace:1 --surface surface:2 "cd /root/Documents/enact-agent && codex --yolo"
-cmux send-key --workspace workspace:1 --surface surface:2 enter
-```
-
-## Local wake follow-up loop
-
-```bash
-cmux capture-pane --workspace workspace:1 --surface surface:2 --lines 120
-
-cmux send --workspace workspace:1 --surface surface:2 "Status check from the local 30-minute monitor. In 8 lines max, summarize: current phase, current file or slice, last completed step, last red proof, last green proof, blocker if any, next exact action, and whether OVERNIGHT_MERGE_STATUS.md is updated."
-cmux send-key --workspace workspace:1 --surface surface:2 enter
-
-cmux capture-pane --workspace workspace:1 --surface surface:2 --lines 120
-```
-
-Use this exact sequence when the local wake lands. Inspect first, ask for the summary second, then inspect again before deciding `nothing`, `steer`, or `stop`.
-
-## Optional right-pane creation
-
-```bash
-cmux new-pane --workspace workspace:1 --type terminal --direction right --focus false
-```
-
-Use only when no helper pane already exists.

package/extensions/cmux/skills/cmux-vm-monitor/scripts/codex_vm_monitor.sh

@@ -1,45 +0,0 @@
-#!/bin/bash
-set -euo pipefail
-
-WORKSPACE_REF="${CMUX_MONITOR_WORKSPACE:-workspace:1}"
-SURFACE_REF="${CMUX_MONITOR_SURFACE:-surface:2}"
-RELAY_WORKSPACE_REF="${CMUX_MONITOR_RELAY_WORKSPACE:-workspace:1}"
-RELAY_SURFACE_REF="${CMUX_MONITOR_RELAY_SURFACE:-surface:1}"
-LINES="${CMUX_MONITOR_LINES:-180}"
-LOG_FILE="${CMUX_MONITOR_LOG:-/tmp/codex_vm_monitor.log}"
-LOCAL_WAKE_MESSAGE_TEMPLATE="${CMUX_MONITOR_WAKE_MESSAGE:-[VM monitor __TIMESTAMP__] 30-minute check. Use exact cmux commands against __WORKSPACE__/__SURFACE__: 1) cmux capture-pane --workspace __WORKSPACE__ --surface __SURFACE__ --lines 120 2) cmux send --workspace __WORKSPACE__ --surface __SURFACE__ \"Status check from the local monitor. In exactly 8 lines, summarize: current phase, current file or slice, last completed step, last red proof, last green proof, blocker if any, next exact action, and whether OVERNIGHT_MERGE_STATUS.md is updated.\" 3) cmux send-key --workspace __WORKSPACE__ --surface __SURFACE__ Enter 4) cmux capture-pane --workspace __WORKSPACE__ --surface __SURFACE__ --lines 120 Then decide nothing | steer | stop.}"
-
-timestamp() {
-  date -u +"%Y-%m-%dT%H:%M:%SZ"
-}
-
-capture() {
-  cmux capture-pane --workspace "$WORKSPACE_REF" --surface "$SURFACE_REF" --lines "$LINES"
-}
-
-relay_local() {
-  local message="$1"
-  cmux send --workspace "$RELAY_WORKSPACE_REF" --surface "$RELAY_SURFACE_REF" "$message"
-  cmux send-key --workspace "$RELAY_WORKSPACE_REF" --surface "$RELAY_SURFACE_REF" tab
-}
-
-snapshot="$(capture 2>&1 || true)"
-
-{
-  printf '=== %s ===\n' "$(timestamp)"
-  printf 'workspace=%s surface=%s\n' "$WORKSPACE_REF" "$SURFACE_REF"
-  printf '%s\n' "$snapshot"
-  printf '\n'
-} >> "$LOG_FILE"
-
-if grep -q "Error: not_found\\|ERROR: Surface not found" <<<"$snapshot"; then
-  printf '[%s] monitor: surface missing\n' "$(timestamp)" >> "$LOG_FILE"
-  relay_local "[VM monitor $(timestamp)] surface missing for $WORKSPACE_REF/$SURFACE_REF"
-  exit 0
-fi
-
-wake_message="${LOCAL_WAKE_MESSAGE_TEMPLATE/__TIMESTAMP__/$(timestamp)}"
-wake_message="${wake_message//__WORKSPACE__/$WORKSPACE_REF}"
-wake_message="${wake_message//__SURFACE__/$SURFACE_REF}"
-printf '[%s] monitor: local wake injected; vm pane captured only\n' "$(timestamp)" >> "$LOG_FILE"
-relay_local "$wake_message"

package/extensions/cmux/skills/cmux-workspace/SKILL.md

@@ -1,93 +0,0 @@
----
-name: cmux-workspace
-description: This skill should be used when work should stay inside the current cmux workspace and terminal, including workspace-scoped pane or surface inspection, non-disruptive terminal automation, and sibling-surface coordination messages.
----
-
-# cmux Workspace
-Use this skill when work should stay scoped to the caller's cmux workspace and surface.
-
-## Default Rule
-Scope actions to the current caller workspace unless the user explicitly names another workspace, tab, or window.
-
-Start by resolving the live caller context:
-```bash
-printf 'workspace=%s\nsurface=%s\nsocket=%s\n' \
-  "${CMUX_WORKSPACE_ID:-}" \
-  "${CMUX_SURFACE_ID:-}" \
-  "${CMUX_SOCKET_PATH:-}"
-cmux identify --json
-```
-
-If the env vars are empty, use `cmux identify --json` and be explicit that you are falling back to the currently focused cmux context.
-
-## Non-Disruptive Automation
-Never change visible focus unless the user explicitly asked for it.
-
-Do not call these speculatively:
-- `cmux select-workspace`
-- `cmux focus-pane`
-- `cmux focus-panel`
-
-Prefer explicit `--workspace` and `--surface` flags for mutating actions.
-
-## Messaging Pattern
-For sibling-surface coordination, the default submission pattern is:
-
-```bash
-cmux send --workspace workspace:N --surface surface:N "<message>"
-cmux send-key --workspace workspace:N --surface surface:N Enter
-cmux capture-pane --workspace workspace:N --surface surface:N --lines 120
-```
-
-Rules:
-- Use `cmux send` plus `cmux send-key Enter` as the default pattern.
-- Always verify delivery with `cmux capture-pane`; do not trust `OK` from `cmux send` alone.
-- If the pane is busy, expect the message to remain queued in the composer. Report that exact state instead of claiming the message was accepted.
-- Only interrupt a busy pane if the user explicitly wants immediate submission.
-
-## Coordination Prefixes
-When you send a coordination message yourself, prefix it so direction is obvious:
-
-- `[sidecar -> enact-agent-config]`
-- `[enact-agent-config -> sidecar]`
-
-Rules:
-- Prefix only the coordination messages you send or relay.
-- Do not assume the user's own plain-text messages already carry a prefix.
-- Keep coordination updates short and operational: owner, current status, blocker, next step.
-
-## Caller Terminal
-Treat the caller surface as the safest anchor for relative operations:
-
-```bash
-cmux send --surface "${CMUX_SURFACE_ID:-}" "git status"
-cmux send-key --surface "${CMUX_SURFACE_ID:-}" Enter
-```
-
-## Inspect Workspace State
-Useful inspection commands:
-
-```bash
-cmux identify --json
-cmux list-workspaces --json
-cmux list-panes --workspace "${CMUX_WORKSPACE_ID:-}" --json
-cmux list-pane-surfaces --workspace "${CMUX_WORKSPACE_ID:-}" --json
-cmux capture-pane --workspace "${CMUX_WORKSPACE_ID:-}" --surface "${CMUX_SURFACE_ID:-}" --lines 120
-```
-
-## Right-Side Helper Policy
-When auxiliary work is needed in the caller workspace:
-- reuse an existing non-caller helper pane if one already exists
-- otherwise create exactly one helper pane to the right
-- avoid creating extra splits when a new surface in the helper pane is enough
-
-Example:
-```bash
-cmux new-pane --workspace "${CMUX_WORKSPACE_ID:-}" --type terminal --direction right --focus false
-```
-
-## Stop Conditions
-Stop and report instead of guessing when:
-- the target workspace or surface cannot be identified confidently
-- the pane stays busy and the message remains queued
-- a command would require focus-changing behavior the user did not request

package/extensions/devops/.agents/plugin.json

@@ -1,36 +0,0 @@
-{
-  "name": "devops",
-  "version": "0.1.0",
-  "description": "DevOps skills for Enact: Azure DevOps CLI workflows and CI pipeline strategy for branch, build, and release operations.",
-  "author": {
-    "name": "Amsterdam Data Labs"
-  },
-  "license": "UNLICENSED",
-  "keywords": [
-    "devops",
-    "azure-devops",
-    "ci",
-    "pipeline",
-    "release"
-  ],
-  "targets": [
-    "claude",
-    "codex",
-    "cursor"
-  ],
-  "skills": "./skills/",
-  "interface": {
-    "displayName": "DevOps",
-    "shortDescription": "Azure DevOps CLI and CI pipeline strategy skills.",
-    "developerName": "Amsterdam Data Labs",
-    "category": "Developer Tools",
-    "capabilities": [
-      "azure devops cli",
-      "ci pipeline strategy"
-    ]
-  },
-  "factory": {
-    "firstParty": true,
-    "operatorScope": "global"
-  }
-}