troubleshooting
Skill4 starsChanged 17 days agoMITView on GitHub
Uses Swing MCP and its documentation to troubleshoot server, agent, and session issues on Swing or JavaFX targets. Trigger this skill when launch_app or attach_to_app fail, when tools report no active session, or when the server initialization fails.
29 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- vmoranv/jshookmcptheir own version, first seen Nov 15, 2026
- ceilidhboy/skillstheir own version, first seen Nov 15, 2026
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- oivanfelipe/claude-skillsedited, first seen Nov 8, 2026
- onelastcommit/noctratheir own version, first seen Nov 8, 2026
- zakirkun/slayerclawtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use task-breakdown and architecture.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ttmouseSkilltask-breakdown
专业的任务拆解器,将复杂需求拆分成"独立可运行与可演示"的最小闭环任务卡。严格按照纵向切片、单一数据变化、单一入口原则,确保每张任务卡都能在单回合实现并验证。当用户说"帮我拆解一下任务"、"用任务拆解器分析"、"按规范拆分"或需要将一个大的开发需求拆分成可执行的小任务时使用。输出格式严格按照[src/renderer/TODO.md]标准存储。
Also in 3 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- ChromeDevTools/chrome-devtools-mcp★ 57k18% same
- kschiavo-beep/claude-skills★ 017% same
- oivanfelipe/claude-skills★ 017% same
Wrote their own version · 26
- cartography-cncf/cartography★ 4.2ksame name
- vmoranv/jshookmcp★ 2.1ksame name
- jasonkneen/kiro★ 753same name
- nanvix/nanvix★ 318same name
- duyet/clickhouse-monitoring★ 303same name
- davidYichengWei/agentic-engineering-framework★ 158same name
- projectbluefin/finpilot★ 131same name
- mycelium-io/mycelium★ 128same name
- NVIDIA/elements★ 119same name
- emanueleielo/ciana-parrot★ 77same name
16 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- swing-mcpSkill
- swing-ui-testingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 7 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If you find a configuration file, read and interpret it to identify potential issues such as:
- Distinctive: line 20
If you cannot find any of these files, only then should you ask the user to provide their configuration file content.
- Distinctive: line 24
Before reading documentation or suggesting configuration changes, check if the failure matches one of the following common patterns.
- Very specific: line 30
Verify the Java version: java -version (must be 21 or newer).
- Very specific: line 31
If multiple JDKs are installed, use an absolute path to the JDK 21+ java binary in the MCP configuration instead of relying on PATH.
- Very specific: line 38
Check that SWING_MCP_AGENT_JAR (or the swing.mcp.agent-jar property) is set in the MCP server configuration's env block.
- Distinctive: line 40
Ask the user to restart the MCP server (or their AI client) after fixing the configuration.
- Very specific: line 44
Verify the PID belongs to a Java process running a Swing or JavaFX UI (jps -l lists candidate JVMs).
- Very specific: line 45
If take_snapshot reports no window on an application you can see, the toolkit may not have started yet — JavaFX windows only exist once …
- Very specific: line 52
Call app_status and list_sessions — the session may have died (alive: false) or another session may be active.
- Very specific: line 55
If the target application blocks its UI thread (the Event Dispatch Thread for Swing, the JavaFX Application Thread for JavaFX — e.g.
- Distinctive: line 69
Read docs/installation.md (per-client setup and the Troubleshooting section) and docs/tools/README.md (server configuration properties) to …
- Distinctive: line 89
After updating, the user must restart the MCP server (or their AI client) for the change to take effect.
- Distinctive: line 93
If the issue is still unclear, run diagnostic commands to test the setup directly:
- Very specific: line 99
Test against the bundled demo app: launch_app with java -jar /path/to/swing-mcp-demo-1.4.0.jar, then take_snapshot.
- Very specific: line 103
If the documentation does not cover the specific error, check if the gh (GitHub CLI) tool is available in the environment.
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Troubleshooting Wizard
You are acting as a troubleshooting wizard to help the user configure and fix their Swing MCP server setup. When this skill is triggered (e.g., because launch_app or attach_to_app failed, tools report that no session is connected, or the server wouldn't start), follow this step-by-step diagnostic process:
Step 1: Find and Read Configuration
Your first action should be to locate and read the MCP configuration file. Search for the following files in the user's workspace: .mcp.json, .vscode/mcp.json, .claude/settings.json, .cursor/mcp.json, or the client's global MCP settings.
If you find a configuration file, read and interpret it to identify potential issues such as:
- A relative or wrong path to the
swing-mcp-serverjar. - A missing or wrong
SWING_MCP_AGENT_JARenvironment variable (must be an absolute path to the shadedswing-mcp-agentjar). - A
javacommand that resolves to an old JDK.
If you cannot find any of these files, only then should you ask the user to provide their configuration file content.
Step 2: Triage Common Errors
Before reading documentation or suggesting configuration changes, check if the failure matches one of the following common patterns.
Symptom: Server doesn't start / no tools listed
The server requires JDK 21+. Some GUI clients don't inherit the shell PATH.
- Verify the Java version:
java -version(must be 21 or newer). - If multiple JDKs are installed, use an absolute path to the JDK 21+
javabinary in the MCP configuration instead of relying onPATH. - Remember that the server logs to
${java.io.tmpdir}/swing-mcp-server.log(e.g./tmp/swing-mcp-server.log) — console logging is disabled because stdout is reserved for the MCP stdio transport. Read this log for startup errors.
Error: launch_app / attach_to_app fails with a missing agent jar
The server needs the agent jar to preload (launch_app) or dynamically attach (attach_to_app) it.
- Check that
SWING_MCP_AGENT_JAR(or theswing.mcp.agent-jarproperty) is set in the MCP server configuration'senvblock. - Confirm the path is absolute and the file exists (e.g.
/path/to/swing-mcp/swing-mcp-agent/target/swing-mcp-agent-1.4.0.jaraftermvn verify). - Ask the user to restart the MCP server (or their AI client) after fixing the configuration.
Symptom: attach_to_app fails against a running JVM
- Verify the PID belongs to a Java process running a Swing or JavaFX UI (
jps -llists candidate JVMs). Iftake_snapshotreports no window on an application you can see, the toolkit may not have started yet — JavaFX windows only exist onceApplication.starthas run. - JVMs started with
-XX:+DisableAttachMechanismcannot be attached to — relaunch the app vialaunch_appinstead. - The target JVM and the MCP server should run as the same OS user; attaching across users fails.
Symptom: Session connects but tools time out or report no session
- Call
app_statusandlist_sessions— the session may have died (alive: false) or another session may be active; useselect_sessionto switch. - The agent binds a loopback-only port in the
swing.mcp.agent-port-min..maxrange (default 40000–40100). Check that a local firewall or sandbox does not block localhost connections in this range, or change the range. - Long-running UI operations may exceed the round-trip timeout — increase
swing.mcp.tool-timeout-ms(default 30000). - If the target application blocks its UI thread (the Event Dispatch Thread for Swing, the JavaFX Application Thread for JavaFX — e.g. a long computation running on it), commands cannot execute; use
wait_forwithEDT_IDLEor fix the application.
Symptom: a JavaFX application snapshots as empty, or uids are comp- only
- The toolkit loads reflectively — JavaFX must be on the target app's class/module path (the agent bundles no JavaFX runtime of its own). Check
list_windows: each window carries atoolkitfield, so atoolkit: "swing"-only (or empty) result on a JavaFX app points here. - Attach (or launch) only after
Application.starthas run — JavaFX windows don't exist before that, so an early snapshot legitimately finds none. dragandevaluate_javaare Swing-only; their error message says so when called against a JavaFX-only target.
Symptom: evaluate_java returns "disabled"
evaluate_java (arbitrary code execution in the target JVM) is disabled by default for security. Enable it explicitly with swing.mcp.evaluate.enabled=true in the server configuration, and only when the user understands the implications.
Step 3: Read the Documentation
Read docs/installation.md (per-client setup and the Troubleshooting section) and docs/tools/README.md (server configuration properties) to map the error to a known issue.
Step 4: Formulate a Configuration
Based on the exact error and the user's environment (OS, MCP client), formulate the correct MCP configuration snippet, for example:
{
"mcpServers": {
"swing": {
"command": "java",
"args": ["-jar", "/absolute/path/to/swing-mcp-server-1.4.0.jar"],
"env": {
"SWING_MCP_AGENT_JAR": "/absolute/path/to/swing-mcp-agent-1.4.0.jar"
}
}
}
}After updating, the user must restart the MCP server (or their AI client) for the change to take effect.
Step 5: Run Diagnostic Commands
If the issue is still unclear, run diagnostic commands to test the setup directly:
java -versionto verify the JDK is 21+.java -jar /path/to/swing-mcp-server-*.jarfrom a terminal to see startup errors directly.- Inspect
${java.io.tmpdir}/swing-mcp-server.logfor stack traces of the server itself. - For the launched application's own stdout/stderr (its stack traces and log lines), call
get_app_output. - Test against the bundled demo app:
launch_appwithjava -jar /path/to/swing-mcp-demo-1.4.0.jar, thentake_snapshot.
Step 6: Check GitHub for Existing Issues
If the documentation does not cover the specific error, check if the gh (GitHub CLI) tool is available in the environment. If so, search the repository for similar issues:
gh issue list --repo crosstech-solutions-bv/swing-mcp --search "<error snippet>" --state all
Alternatively, recommend that the user checks https://github.com/crosstech-solutions-bv/swing-mcp/issues for help.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

