@conductor-oss/conductor-skills 1.4.2

package/bin/conductor-skills.js

@@ -0,0 +1,135 @@
+#!/usr/bin/env node
+/*
+ * conductor-skills — npm wrapper for the Conductor Skills installer.
+ *
+ * Detects the platform, then invokes the bundled install.sh (Unix) or
+ * install.ps1 (Windows) with CONDUCTOR_SKILLS_LOCAL_DIR pointing at the
+ * package root. The shell scripts read that env var and use the bundled
+ * files instead of fetching from GitHub.
+ */
+
+'use strict';
+
+const { spawnSync } = require('child_process');
+const path = require('path');
+const fs = require('fs');
+
+const PKG_ROOT = path.resolve(__dirname, '..');
+const IS_WINDOWS = process.platform === 'win32';
+const args = process.argv.slice(2);
+
+function showHelp() {
+  const version = readVersion();
+  console.log(`@conductor-oss/conductor-skills v${version}
+
+Install the Conductor Skills for your AI coding agent.
+
+Usage:
+  conductor-skills --all                        Install for all detected agents
+  conductor-skills --agent <name>               Install for a specific agent
+  conductor-skills --all --upgrade              Upgrade all installed agents
+  conductor-skills --agent <name> --uninstall   Remove an installation
+  conductor-skills --agent <name> --global      Global install (where supported)
+  conductor-skills --check                      Dry run — show planned changes
+  conductor-skills --version                    Print version
+  conductor-skills --help                       This help
+
+Supported agents:
+  claude, codex, gemini, cursor, windsurf, cline, aider,
+  copilot, amazonq, opencode, roo, amp
+
+Examples:
+  npx @conductor-oss/conductor-skills --agent claude
+  npx @conductor-oss/conductor-skills --all
+  conductor-skills --agent cursor --uninstall
+
+Docs: https://github.com/conductor-oss/conductor-skills
+`);
+}
+
+function readVersion() {
+  try {
+    return fs.readFileSync(path.join(PKG_ROOT, 'VERSION'), 'utf8').trim();
+  } catch {
+    return 'unknown';
+  }
+}
+
+function runUnix() {
+  const sh = path.join(PKG_ROOT, 'install.sh');
+  if (!fs.existsSync(sh)) {
+    console.error(`error: install.sh not found at ${sh}`);
+    process.exit(1);
+  }
+  const r = spawnSync('bash', [sh, ...args], {
+    stdio: 'inherit',
+    env: { ...process.env, CONDUCTOR_SKILLS_LOCAL_DIR: PKG_ROOT },
+  });
+  process.exit(r.status === null ? 1 : r.status);
+}
+
+function runWindows() {
+  const ps1 = path.join(PKG_ROOT, 'install.ps1');
+  if (!fs.existsSync(ps1)) {
+    console.error(`error: install.ps1 not found at ${ps1}`);
+    process.exit(1);
+  }
+  // Translate POSIX-style flags ("--agent claude") into PowerShell
+  // parameters ("-Agent claude"). The PowerShell script declares each
+  // parameter in PascalCase, so explicit kebab-case → PascalCase mapping
+  // is required — naive capitalize-first-letter breaks multi-word flags
+  // like --project-dir (which must become -ProjectDir, not -Project-dir).
+  const POSIX_TO_PS = {
+    'agent': 'Agent',
+    'all': 'All',
+    'global': 'Global',
+    'project-dir': 'ProjectDir',
+    'upgrade': 'Upgrade',
+    'check': 'Check',
+    'force': 'Force',
+    'uninstall': 'Uninstall',
+    'version': 'Version',
+    'help': 'Help',
+  };
+  const psArgs = [];
+  for (let i = 0; i < args.length; i++) {
+    const a = args[i];
+    if (a.startsWith('--')) {
+      const name = a.slice(2);
+      const psName = POSIX_TO_PS[name];
+      if (!psName) {
+        console.error(`error: unknown flag --${name}. Run with --help for usage.`);
+        process.exit(2);
+      }
+      psArgs.push('-' + psName);
+    } else {
+      psArgs.push(a);
+    }
+  }
+  const r = spawnSync(
+    'powershell',
+    ['-NoProfile', '-ExecutionPolicy', 'Bypass', '-File', ps1, ...psArgs],
+    {
+      stdio: 'inherit',
+      env: { ...process.env, CONDUCTOR_SKILLS_LOCAL_DIR: PKG_ROOT },
+    }
+  );
+  process.exit(r.status === null ? 1 : r.status);
+}
+
+// Argument parsing — fast paths first.
+if (args.length === 0 || args.includes('--help') || args.includes('-h')) {
+  showHelp();
+  process.exit(0);
+}
+
+if (args.includes('--version') || args.includes('-v')) {
+  console.log(readVersion());
+  process.exit(0);
+}
+
+if (IS_WINDOWS) {
+  runWindows();
+} else {
+  runUnix();
+}

package/commands/conductor-optimize.md

@@ -0,0 +1,18 @@
+---
+description: Review and optimize an existing Conductor workflow
+---
+
+Run the optimization checklist in [skills/conductor/references/optimization.md](../skills/conductor/references/optimization.md) against a workflow the user names.
+
+## Procedure
+
+1. **Identify the target.** Ask the user: a JSON file path, or a registered workflow name (+ optional version)? If they don't say, ask once.
+2. **Load the definition.**
+   - File: `Read` the JSON.
+   - Registered: `conductor workflow get {name}` (omit `--version` for latest).
+3. **Load each SIMPLE task's definition.** Timeouts, retry policy, rate limits, and `concurrentExecLimit` live on the task definition, not on the workflow task. Run `conductor taskDef get {name}` for every distinct SIMPLE task type referenced.
+4. **Walk every checklist item.** Categories A–E (A1–A7, B1–B7, C1–C5, D1–D3, E1–E3). Don't skip any — record findings as INFO if the item is fine, just to show coverage.
+5. **Report findings grouped by severity** (CRITICAL / WARN / INFO). Use the report template in optimization.md. See [skills/conductor/examples/review-workflow.md](../skills/conductor/examples/review-workflow.md) for the expected shape.
+6. **Offer fixes one at a time.** Don't apply changes silently. For each fix, describe what you'd change before doing it. Some findings (e.g. `failureWorkflow` design, retry semantics) need user input before you can implement.
+
+If the user wants only a quick scan, prioritize CRITICAL items and skip the INFO-only output. Otherwise, full report.

package/commands/conductor-scaffold-worker.md

@@ -0,0 +1,19 @@
+---
+description: Generate a Conductor worker stub for a SIMPLE task in your language of choice
+---
+
+Scaffold a worker using the SDK pattern in [skills/conductor/references/workers.md](../skills/conductor/references/workers.md).
+
+## Procedure
+
+1. **Ask for language.** Supported: Python, JavaScript / TypeScript, Java, Go, C#, Ruby, Rust. If the user has a workspace open, default to whatever language is dominant in the repo.
+2. **Ask for the task type.** This must match the `name` field of the SIMPLE task in the workflow definition. If the user has a specific workflow in mind, offer to read it (`conductor workflow get` or a JSON file) and pull the task name(s) directly.
+3. **Generate the worker stub** from the matching SDK template in workers.md. Include:
+   - Install command for the SDK (e.g. `pip install conductor-python`).
+   - The worker function with input parameter mapping and output shape.
+   - The runner / poller setup.
+   - **A comment noting the worker must be idempotent** — Conductor may redeliver on failure or timeout.
+4. **Show how to start it** — the actual command/entry point in that language.
+5. **Mention the worker gate.** If the workflow that uses this task type isn't registered yet, remind the user to register both the workflow and the task definition (`conductor taskDef create taskdef.json`) so the runtime knows about it.
+
+If the user has a workflow JSON file or registered workflow handy, also offer to verify the task type appears as a SIMPLE task there.

package/commands/conductor-setup.md

@@ -0,0 +1,15 @@
+---
+description: First-time Conductor setup — install the CLI, choose a server, configure auth
+---
+
+Walk the user through Conductor first-time setup using [skills/conductor/references/setup.md](../skills/conductor/references/setup.md). Steps 1–4 in order.
+
+Don't skip checks. Specifically:
+
+- Run `conductor --version` first; if missing, prefer `npx @conductor-oss/conductor-cli` over global install.
+- **Confirm with the user before** running `npm install -g @conductor-oss/conductor-cli` — it's a system-modifying action.
+- Ask the user whether they want a local server (Option A) or to point at an existing one (Option B); don't assume.
+- Only ask for credentials *after* `conductor workflow list` returns 401/403 — many servers don't need auth.
+- Never echo auth tokens, keys, or secrets in output.
+
+End with `conductor workflow list` to confirm connectivity, and report the result.

package/commands/conductor.md

@@ -0,0 +1,15 @@
+---
+description: Conductor command menu — pick a structured action or describe what you want
+---
+
+The user invoked `/conductor` without a sub-action. Show the three structured subcommands and ask what they want to do.
+
+**Structured commands** (each is a guided procedure):
+
+- `/conductor-setup` — first-time setup: install the CLI, point at a server, configure auth.
+- `/conductor-optimize` — review an existing workflow against the optimization checklist and report findings (CRITICAL / WARN / INFO).
+- `/conductor-scaffold-worker` — generate a worker stub for a SIMPLE task.
+
+For everything else (run, status, schedule, retry, signal, visualize, create, modify), the user can just describe it in plain English — the `conductor` skill ([SKILL.md](../skills/conductor/SKILL.md)) handles it.
+
+After listing the three subcommands, ask: **"What would you like to do?"** and proceed based on their answer.