Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Drive and inspect the running VCell desktop client (Swing) through the debug bridge — launch it from a source build, read the live UI as JSON, click/type/select, and verify a fix against the real app.
Install Swing Debug
$ npx skills add virtualcell/vcell --skill swing-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install virtualcell/vcell swing-debug --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/swing-debug .claude/skills/swing-debug && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "swing-debug" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/swing-debug into .claude/skills/swing-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swing-debug", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/virtualcell/vcell/tree/master/.claude/skills/swing-debugType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add virtualcell/vcell --skill swing-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install virtualcell/vcell swing-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/swing-debug .agents/skills/swing-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "swing-debug" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/swing-debug into .agents/skills/swing-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swing-debug", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add virtualcell/vcell --skill swing-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install virtualcell/vcell swing-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/swing-debug .cursor/skills/swing-debug && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "swing-debug" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/swing-debug into .cursor/skills/swing-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swing-debug", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/virtualcell/vcell.git --path .claude/skills/swing-debug--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add virtualcell/vcell --skill swing-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install virtualcell/vcell swing-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/swing-debug .gemini/skills/swing-debug && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "swing-debug" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/swing-debug into .gemini/skills/swing-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swing-debug", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install virtualcell/vcell swing-debugInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add virtualcell/vcell --skill swing-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/swing-debug .github/skills/swing-debug && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "swing-debug" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/swing-debug into .github/skills/swing-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swing-debug", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add virtualcell/vcell --skill swing-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install virtualcell/vcell swing-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/swing-debug .opencode/skills/swing-debug && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "swing-debug" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/swing-debug into .opencode/skills/swing-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swing-debug", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
swing-debug- GitHub stars
- 140
- Token cost
- ~1.8k tokens
- SKILL.md length
- 862 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Drive and inspect the running VCell desktop client (Swing) through the debug bridge — launch it from a source build, read the live UI as JSON, click/type/select, and verify a fix against the real app.
- Fixing a vcell-client UI bug
- SKILL.md covers The loop, Selectors: prefer name=, Verifying a fix — the part… and Known limits, plus 3 more sections
- Calls java, mvn and git
- Reproducing a user-reported desktop problem
What it does
Swing Debug is an agent skill from virtualcell/vcell. Drive and inspect the running VCell desktop client (Swing) through the debug bridge — launch it from a source build, read the live UI as JSON, click/type/select, and verify a fix against the real app. Use when investigating or fixing a vcell-client UI bug, reproducing a user-reported desktop problem, or when a change needs checking in the running client rather than only in tests.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. The repository describes itself as: Virtual Cell Framework.
When your agent uses it
- Fixing a vcell-client UI bug
- Reproducing a user-reported desktop problem
- A change needs checking in the running client rather than only in tests
Example prompts
- “/swing-debug”
What it can do on your machine
Read from SKILL.md and the folder at commit 340d6ee. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
javamvngitjavac
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Swing Debug loads about 1.8k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 862 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 862 words (~1,785 tokens).
“The client ships a dev-only HTTP control surface — the Swing analogue of a DOM inspector plus Playwright. It is off unless -Dvcell.debugBridge=true and binds to loopback only.”
- name
- swing-debug
Files
Just SKILL.md in .claude/skills/swing-debug of virtualcell/vcell.
Open the folder on GitHubat commit 340d6ee
Compare with similar skills
Swing Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Swing Debug this skillvirtualcell/vcell | 140 | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
More from virtualcell/vcell
Deploy
virtualcell/vcell
Cut a VCell release and deploy it — pick the next version, write the changelog, tag + GitHub release (triggers the CI-full image build), then CD-sites to a site (alpha→dev namespace, rel→prod…
Related
Categories
Questions about Swing Debug
What does Swing Debug do?
Drive and inspect the running VCell desktop client (Swing) through the debug bridge — launch it from a source build, read the live UI as JSON, click/type/select, and verify a fix against the real app. Swing Debug is an agent skill from virtualcell/vcell. Drive and inspect the running VCell desktop client (Swing) through the debug bridge — launch it from a source build, read the live UI as JSON, click/type/select, and verify a fix against the real app.
When should I use Swing Debug?
Swing Debug fits situations like: fixing a vcell-client UI bug; reproducing a user-reported desktop problem; A change needs checking in the running client rather than only in tests.
How do I install Swing Debug in Claude Code?
Run `npx skills add virtualcell/vcell --skill swing-debug -a claude-code`. Or copy the skill folder (.claude/skills/swing-debug in virtualcell/vcell) into .claude/skills/swing-debug in your project. Claude Code loads it when a task matches its description.
How do I install Swing Debug in Codex?
Run `npx skills add virtualcell/vcell --skill swing-debug -a codex`. Or copy the skill folder (.claude/skills/swing-debug in virtualcell/vcell) into .agents/skills/swing-debug in your project. Codex loads it when a task matches its description.
Can I use Swing Debug in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add virtualcell/vcell --skill swing-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swing-debug, .gemini/skills/swing-debug, .github/skills/swing-debug and .opencode/skills/swing-debug in your project.
What does Swing Debug need to run?
Going by SKILL.md and its folder, Swing Debug needs the command-line tools its instructions call (java, mvn, git and javac).
Does Swing Debug access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Swing Debug safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Swing Debug use?
Swing Debug has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Swing Debug use?
About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Swing Debug?
Skills that share tags, products or a category with Swing Debug: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Swing Debug?
virtualcell (a GitHub organization) maintains it in virtualcell/vcell, which has 140 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.
Source: virtualcell/vcell on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.