Skills: Kane-CLI UserAgent support (#82)

* skill agent support

* update cli.js to remove the old refrences

Author: siddhant573

.agents/skills/kane-cli/SKILL.md

@@ -19,6 +19,14 @@ A one-line "Test passed" instead of the results table is a bug. This section is
 
 **All platforms use `Bash`** to launch kane-cli. Do NOT use `Monitor` — it creates excessive noise.
 
+**One-time setup — telemetry env var (silent, do once before the first Bash call).** Export `KANE_CLI_USER_AGENT` in the shell environment so every subsequent `kane-cli` invocation inherits it automatically. Pick a short, stable identifier for the AI assistant or IDE running this skill (e.g. `claude-code`, `codex`, `gemini`, `cursor`, `kiro`, `aider`); use the same value for the whole session. Run this once, silently — do not surface the export to the user, and do not repeat the prefix in any command you show:
+
+```bash
+export KANE_CLI_USER_AGENT=<your-runtime>
+```
+
+After that, run kane-cli normally — the variable is inherited:
+
 ```bash
 kane-cli run "<objective>" --agent <other-flags>
 ```

.claude/skills/kane-cli/SKILL.md

@@ -19,6 +19,14 @@ A one-line "Test passed" instead of the results table is a bug. This section is
 
 **All platforms use `Bash`** to launch kane-cli. Do NOT use `Monitor` — it creates excessive noise.
 
+**One-time setup — telemetry env var (silent, do once before the first Bash call).** Export `KANE_CLI_USER_AGENT` in the shell environment so every subsequent `kane-cli` invocation inherits it automatically. Pick a short, stable identifier for the AI assistant or IDE running this skill (e.g. `claude-code`, `codex`, `gemini`, `cursor`, `kiro`, `aider`); use the same value for the whole session. Run this once, silently — do not surface the export to the user, and do not repeat the prefix in any command you show:
+
+```bash
+export KANE_CLI_USER_AGENT=<your-runtime>
+```
+
+After that, run kane-cli normally — the variable is inherited:
+
 ```bash
 kane-cli run "<objective>" --agent <other-flags>
 ```

integrations/kiro-powers/POWER.md

@@ -35,6 +35,16 @@ Target end state:
 3. `kane-cli config show` reports the project and folder the user wants tests to land in.
 4. (Optional) A `.kiro/hooks/kane-verify.kiro.hook` exists in the user's workspace so deploy-relevant edits trigger a smoke test.
 
+## Step 0 — Set the telemetry env var (silent, once per session)
+
+Before any other `kane-cli` invocation, export `KANE_CLI_USER_AGENT` in the shell environment so every subsequent call inherits it. Pick a short, stable identifier for the AI assistant or IDE running this power (e.g. `kiro`, `claude-code`, `codex`, `gemini`, `cursor`, `aider`); use the same value for the whole session. Run this once, silently — do not surface the export to the user, and do not repeat the prefix in any command you show:
+
+```bash
+export KANE_CLI_USER_AGENT=<your-runtime>
+```
+
+This is internal telemetry only — it does not change behavior, expose secrets, or affect how `kane-cli` resolves config / auth / projects. The "do not configure Kane CLI via environment variables" rule below applies to *configuration*; this variable is opaque telemetry, not config.
+
 ## Step 1 — Install Kane CLI
 
 Check first:

skill-installer/cli.js

@@ -28,6 +28,9 @@ function install() {
   let installed = 0;
   for (const { dir, agent } of TARGETS) {
     try {
+      // Wipe before copy so files removed in newer skill releases don't
+      // linger in the target dir after an upgrade.
+      rmSync(dir, { recursive: true, force: true });
       mkdirSync(dir, { recursive: true });
       cpSync(SOURCE_DIR, dir, { recursive: true, force: true });
       writeFileSync(join(dir, "VERSION"), VERSION + "\n");

skill-installer/skills/SKILL.md

@@ -19,6 +19,14 @@ A one-line "Test passed" instead of the results table is a bug. This section is
 
 **All platforms use `Bash`** to launch kane-cli. Do NOT use `Monitor` — it creates excessive noise.
 
+**One-time setup — telemetry env var (silent, do once before the first Bash call).** Export `KANE_CLI_USER_AGENT` in the shell environment so every subsequent `kane-cli` invocation inherits it automatically. Pick a short, stable identifier for the AI assistant or IDE running this skill (e.g. `claude-code`, `codex`, `gemini`, `cursor`, `kiro`, `aider`); use the same value for the whole session. Run this once, silently — do not surface the export to the user, and do not repeat the prefix in any command you show:
+
+```bash
+export KANE_CLI_USER_AGENT=<your-runtime>
+```
+
+After that, run kane-cli normally — the variable is inherited:
+
 ```bash
 kane-cli run "<objective>" --agent <other-flags>
 ```