Claude Skill MartBrowse skillsWhat is a Skill?
 
← Back to list

opencode QA Toolkit

A QA-focused skill for smoke-testing opencode's CLI, HTTP server, plugin hooks/events and TUI, plus read-only session DB investigation.

Dev & CodingAdvanced★ 67,531⑂ 5,507AI score 7/10Last updated: Aug 9, 2026

What it does

This skill QAs the opencode coding agent itself. It maps every QA need onto one of four cases, each backed by a tested helper script and a deep reference doc.

  • Case A – CLI: assert on opencode run --format json line-delimited events for non-interactive runs.
  • Case B – Server / hooks / events: open the /event SSE stream to prove a specific event (and therefore a plugin hook) fired; smoke-test /global/health, /doc, and 401 auth behavior.
  • Case C – TUI: boot the TUI under tmux in an isolated sandbox, confirm render and key delivery, plus an xterm.js web-terminal recipe for true-color screenshot evidence.
  • Case D – DB investigation: read-only SQLite lookups of sessions by id, title, or message text, and full-session JSON export.

Every script ships a --self-test, and anything that spawns opencode uses an isolated XDG sandbox so the real session DB is never polluted.

Who it's for

  • Contributors and fork maintainers who need repeatable regression checks on opencode.
  • Plugin authors who must prove a hook actually fires end to end.
  • Anyone digging through a multi-GB opencode session database for a specific conversation.

Examples

  1. "Prove my plugin's message.part.updated hook fires" → attach the SSE probe to a real server, fire a prompt_async request, and capture the event.
  2. "Find sessions from the last 7 days containing 'permission denied'" → db-session-by-text.sh --since "7 days", then export the matching session as JSON.
  3. "Does the TUI still boot on this build?" → tui-smoke.sh --self-test, then compare the real DB session count before and after to confirm isolation.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .agents/skills/opencode-qa folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/opencode-qa/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/code-yeongyu/oh-my-openagent.git && mkdir -p ~/.claude/skills && cp -r oh-my-openagent/.agents/skills/opencode-qa ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Install prerequisites: opencode, sqlite3, curl, jq, and tmux (on macOS: brew install sqlite jq tmux).
  2. Clone the repo: git clone https://github.com/code-yeongyu/oh-my-openagent.git
  3. Copy the skill folder: mkdir -p ~/.claude/skills && cp -r oh-my-openagent/.agents/skills/opencode-qa ~/.claude/skills/
  4. Restart Claude Code and confirm opencode-qa appears in your skill list.
  5. Verify the harness: cd ~/.claude/skills/opencode-qa && bash scripts/lib/common.sh --self-check
  6. Check your version with opencode --version (docs target v1.17.7), then invoke the skill with a prompt like "QA opencode's event stream".
  7. Note: DB reads are safe, but always run opencode-spawning QA through the bundled scripts so it uses the isolated sandbox.
View source on GitHub ↗License: NOASSERTION