opencode-gemiterm-skills 0.5.1 → 0.6.1

package/AGENTS.md

@@ -1,10 +1,11 @@
 # AGENTS.md - opencode-gemiterm-skills
 
 <critical_rules priority="highest">
-1. The bundled `debate-with-gemini` skill depends on the `gemiterm` Python CLI being installed and authenticated on the host.
+1. The bundled `debate-with-gemini` skill depends on the `gemiterm` Bun-native CLI being installed (or available via `bunx gemiterm`) and authenticated on the host.
 2. This package ships a real installer (`src/installer.ts`) that copies skill assets to the consumer's `.opencode/skills/` and registers them in `opencode.json`. The `src/cli.ts` is the CLI entry point (install/uninstall/status subcommands), resolved by `package.json#bin`. Only add code under `src/` that supports the install/uninstall/status commands.
-3. Skill frontmatter is the source of truth. Do not edit `assets/skills/*/SKILL.md` frontmatter in ways that break the `name` / `description` contract.
-4. The `metadata.requires: gemiterm` link on `debate-with-gemini` must remain so consumers know to install the Python CLI first.
+3. Skill frontmatter is the source of truth. Do not edit `skills/*/SKILL.md` frontmatter in ways that break the `name` / `description` contract.
+4. The `metadata.requires: gemiterm` link on `debate-with-gemini` must remain so consumers know to install the CLI first.
+5. GemiTerm is a Bun-native CLI — all skill documents assume Bun as the runtime. Do not reference Python, `pipx`, or `pip` install paths.
 </critical_rules>
 
 <context_hierarchy>
@@ -21,13 +22,13 @@
 </role>
 
 <bundled_skills>
-<skill name="gemiterm" path="assets/skills/gemiterm/SKILL.md" requires="Python CLI gemiterm" />
-<skill name="debate-with-gemini" path="assets/skills/debate-with-gemini/SKILL.md" requires="gemiterm skill + Python CLI gemiterm" />
+<skill name="gemiterm" path="skills/gemiterm/SKILL.md" requires="Bun-native CLI gemiterm" />
+<skill name="debate-with-gemini" path="skills/debate-with-gemini/SKILL.md" requires="gemiterm skill + Bun-native CLI gemiterm" />
 </bundled_skills>
 
 <self_config>
 <location>.opencode/opencode.json</location>
-<purpose>Register assets/skills/ as a skill path and pre-allow both skills</purpose>
+<purpose>Register skills/ as a skill path and pre-allow both skills</purpose>
 <pointer_in_package_json>opencode.plugin → .opencode/opencode.json</pointer_in_package_json>
 </self_config>
 
@@ -53,7 +54,7 @@
 <use_case>Local development against a checkout of this repo</use_case>
 </file_fallback>
 <prerequisites>
-  - pip install gemiterm
+  - bun install gemiterm -g
   - gemiterm install-browser
   - gemiterm auth
 </prerequisites>

package/CHANGELOG.md

@@ -4,6 +4,27 @@ All notable changes to `opencode-gemiterm-skills` will be documented in this fil
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.6.1] - 2026-06-12
+
+### Changed
+- Fixed frontmatter for `debate-with-gemini` skill.
+
+## [0.6.0] - 2026-06-10
+
+### Changed
+- **GemiTerm is now a Bun-native CLI** — the underlying `gemiterm` CLI has been rewritten to run on Bun instead of Python. All skill documents updated to reflect the new runtime: skills first check for a global `gemiterm` install, fall back to `bunx gemiterm` for transparent npx-style invocation, and if Bun itself is missing emit platform-aware install instructions (`curl -fsSL https://bun.sh/install | bash` on macOS/Linux, `powershell -c "irm bun.sh/install.ps1 | iex"` on Windows) before erroring out.
+- Added `metadata.runtime: bun` to both skill frontmatter entries.
+- Updated `debate-with-gemini` REFERENCE.md subagent template to mention `bunx gemiterm` fallback for every command and added `bunx gemiterm *` to the permissions block.
+- **Rewrote both skill documents** — `gemiterm` and `debate-with-gemini` SKILL.md and REFERENCE.md now contain richer, more structured content: the `debate-with-gemini` skill includes tactical patterns (Concede-and-Counter, Force Concrete Example, Decision Matrix, Reframe the Question, Line-in-the-Sand), explicit stopping criteria, and a structured debate-report format; the `gemiterm` skill has an expanded command reference with detailed flags and common automation patterns.
+- **Directory restructure** — moved `assets/skills/{gemiterm,debate-with-gemini}` → `skills/{gemiterm,debate-with-gemini}` so both skills sit at the standard `skills/<name>/SKILL.md` path recognized by Vercel's `skills` CLI (and the broader skills ecosystem).
+- `.claude-plugin/plugin.json` and `.opencode/opencode.json` updated to reference the new `./skills` path; `package.json#files` now whitelists `skills` instead of `assets`.
+- `src/installer.ts` and `tests/skills.test.ts` source-path constants updated accordingly.
+- Docs (`AGENTS.md`, `CONTRIBUTING.md`) updated to reflect the new layout.
+
+### Removed
+- `assets/` directory (no longer needed; skills moved to repo root).
+- All references to `pipx install gemiterm` and Python-based install paths.
+
 ## [0.5.1] - 2026-06-07
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-gemiterm-skills",
-  "version": "0.5.1",
+  "version": "0.6.1",
   "type": "module",
   "module": "index.ts",
   "description": "AI agent skills for Google Gemini — list, search, export Gemini chats and run structured debates with Gemini. Works with OpenCode, Claude Code, and any skill-compatible AI agent.",
@@ -26,7 +26,7 @@
     "index.ts",
     "plugin.ts",
     "src",
-    "assets",
+    "skills",
     "README.md",
     "AGENTS.md",
     "CHANGELOG.md",

package/{assets/skills → skills}/debate-with-gemini/REFERENCE.md

@@ -2,6 +2,8 @@
 
 Subagent prompt template, tactical patterns, and report format for the `debate-with-gemini` skill.
 
+> **Runtime note:** GemiTerm is a Bun-native CLI. Replace every `gemiterm` invocation with `bunx gemiterm` if the tool is not globally installed. See execution-loop details below.
+
 ---
 
 ## Subagent Prompt Template
@@ -30,14 +32,17 @@ For each turn:
 1. Send your message:
    gemiterm continue "{{GEMINI_CHAT_ID}}" "your message here"
 
+   If gemiterm is not globally installed, use:
+   bunx gemiterm continue "{{GEMINI_CHAT_ID}}" "your message here"
+
    Wait for Gemini's response written to the console.
 2. Analyze the response — concessions? New arguments? Weaknesses?
 3. Craft next response using Tactical Patterns below
 4. Repeat until turn limit or stop condition
 
-Prefer `gemiterm continue` because it returns Gemini's last response inline and avoids an extra round-trip.
+Prefer `gemiterm continue` (or `bunx gemiterm continue`) because it returns Gemini's last response inline and avoids an extra round-trip.
 
-Use `gemiterm fetch "{{GEMINI_CHAT_ID}}" --format json` ONLY if console output has parsing issues or times out.
+Use `gemiterm fetch "{{GEMINI_CHAT_ID}}" --format json` (or `bunx gemiterm fetch ...`) ONLY if console output has parsing issues or times out.
 
 ## Stopping Criteria
 - {{TURN_LIMIT}} turns completed
@@ -108,12 +113,13 @@ If the opencode config lacks bash permissions for `gemiterm`, add:
 {
   "permission": {
     "bash": {
-      "gemiterm *": "allow"
+      "gemiterm *": "allow",
+      "bunx gemiterm *": "allow"
     }
   }
 }
 ```
 
-This allows the subagent to run `gemiterm new`, `gemiterm continue`, `gemiterm fetch`, and `gemiterm list` without prompting.
+This allows the subagent to run `gemiterm new`, `gemiterm continue`, `gemiterm fetch`, `gemiterm list`, and their `bunx gemiterm` equivalents without prompting.
 
 Drop this into the top-level `permission` object in `opencode.json`. For per-agent override, nest it under `agent.<name>.permission`.

package/{assets/skills → skills}/debate-with-gemini/SKILL.md

@@ -1,11 +1,12 @@
 ---
 name: debate-with-gemini
-description: Conduct structured multi-turn technical debates with Gemini AI via gemiterm CLI. Delegates a subagent to argue a position (for/against) autonomously for up to N turns. Use when user says "debate gemini", "argue with gemini", "have gemini defend/attack X", "continue debate", or wants a technical position stress-tested against Gemini. Triggers on: debate, argue, gemini, position, for/against, stress-test, counter-argument. Requires gemiterm CLI installed and authenticated.
+description: 'Conduct structured multi-turn technical debates with Gemini AI via the gemiterm CLI. Delegates a subagent to argue a position (for or against) autonomously for up to N turns. Use when the user says - debate gemini, argue with gemini, have gemini defend or attack X, continue debate, or wants a technical position stress-tested against Gemini. Requires the gemiterm CLI to be installed and authenticated.'
 license: MIT
 compatibility: opencode, claude-code, and any skill-compatible agent
 metadata:
   tool: gemiterm
   workflow: debate
+  runtime: bun
 ---
 
 # Debate with Gemini
@@ -16,7 +17,7 @@ metadata:
 User: "Debate gemini on for/against using X. Context: docs/arch.md. 5 turns."
 
 1. skill("gemiterm")                              — load CLI commands
-2. gemiterm status                                — verify auth
+2. gemiterm status                                — verify auth (or bunx gemiterm status)
 3. Read docs/arch.md, build seeding prompt
 4. gemiterm new "You argue AGAINST X. [context]"  — seed Gemini, capture chat_id
 5. Build opening argument for the FOR position
@@ -26,11 +27,24 @@ User: "Debate gemini on for/against using X. Context: docs/arch.md. 5 turns."
 
 ## Prerequisites
 
+GemiTerm is a **Bun-native** CLI. Before running any commands, resolve the executable:
+
+1. `gemiterm --version` — if this succeeds, use `gemiterm` directly.
+2. If not found, use `bunx gemiterm` as a transparent fallback for all commands.
+3. If `bun` is not installed, print the platform-appropriate install command and stop:
+
+| Platform | Command |
+|----------|---------|
+| macOS / Linux | `curl -fsSL https://bun.sh/install \| bash` |
+| Windows | `powershell -c "irm bun.sh/install.ps1 \| iex"` |
+
+Then:
+
 ```bash
 gemiterm status
 ```
 
-If not connected: `pipx install gemiterm && gemiterm install-browser && gemiterm auth`
+If not connected: install gemiterm globally (`bun install gemiterm -g`), then `gemiterm install-browser && gemiterm auth`.
 
 ## Inputs
 

package/{assets/skills → skills}/gemiterm/REFERENCE.md

@@ -2,6 +2,8 @@
 
 Complete command reference for GemiTerm CLI. Loaded on demand by [SKILL.md](SKILL.md).
 
+> **Runtime note:** GemiTerm is a Bun-native application. All commands below assume `gemiterm` is available. If not globally installed, prefix every command with `bunx` (e.g. `bunx gemiterm list --format json`). See [SKILL.md](SKILL.md) > "Install & invocation" for the full resolution flow.
+
 ## Contents
 
 - [Commands](#commands)

package/{assets/skills → skills}/gemiterm/SKILL.md

@@ -1,26 +1,55 @@
 ---
 name: gemiterm
-description: Google Gemini Terminal CLI wrapper for listing chats, fetching transcripts, exporting conversations, and managing profiles via the gemiterm Python CLI. Use when the user asks to read, list, export, or interact with Gemini chat history from a terminal, or invokes "gemiterm" commands.
+description: Google Gemini Terminal CLI wrapper for listing chats, fetching transcripts, exporting conversations, and managing profiles via the gemiterm Bun-native CLI. Use when the user asks to read, list, export, or interact with Gemini chat history from a terminal, or invokes "gemiterm" commands.
 license: MIT
 compatibility: opencode, claude-code, and any skill-compatible agent
 metadata:
   tool: gemiterm
+  runtime: bun
 ---
 
 # GemiTerm — Google Gemini Terminal CLI
 
 GemiTerm provides terminal access to Google Gemini chat history: list, fetch, export, delete, and manage profiles. Commands that emit `--format json` are automation-friendly; `auth` and `continue` require interactive flows.
 
-## Install check
+## Install & invocation
+
+GemiTerm is a **Bun-native** CLI. All `gemiterm` commands below assume the tool is available. The agent must resolve the executable at runtime:
+
+### 1. Check if globally installed
 
 ```bash
 gemiterm --version
 ```
 
-If missing:
+If this succeeds, use `gemiterm` directly for all commands.
+
+### 2. Fallback: `bunx gemiterm`
+
+If not globally installed, use `bunx gemiterm` as a transparent fallback. This downloads and runs the latest version on first use:
+
+```bash
+bunx gemiterm --version
+bunx gemiterm list --format json
+bunx gemiterm auth
+# … etc — prefix every command with "bunx"
+```
+
+### 3. Bun not installed
+
+If `bun` is not available either, print the appropriate install command for the user's platform and stop:
+
+| Platform | Command |
+|----------|---------|
+| macOS / Linux | `curl -fsSL https://bun.sh/install \| bash` |
+| Windows | `powershell -c "irm bun.sh/install.ps1 \| iex"` |
+
+After the user installs Bun, re-run from step 1. Auto-detect the platform from `$OSTYPE`, `uname`, or `process.platform`.
+
+**To install gemiterm globally (optional):**
 
 ```bash
-pipx install gemiterm
+bun install gemiterm -g
 gemiterm install-browser
 gemiterm auth
 ```

package/src/installer.ts

@@ -169,7 +169,7 @@ export async function install(
   }
 
   for (const name of SKILL_NAMES) {
-    const srcSkillDir = join(pkgDir, "assets", "skills", name);
+    const srcSkillDir = join(pkgDir, "skills", name);
     const destSkillDir = join(configBase, "skills", name);
     await copyDir(srcSkillDir, destSkillDir);
     skillPaths.push(destSkillDir);