Mps Run Configurations
JetBrains/MPS
Create and execute IDE run configurations for MPS root nodes via MPS MCP — Java Application for IMainClass / ClassConcept with main, JUnit Tests for ITestCase.
Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods.
Install Eclipse Test
$ npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-test --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/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/eclipse-test .claude/skills/eclipse-test && 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 "eclipse-test" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-test into .claude/skills/eclipse-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-test", 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/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-testType 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 gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/eclipse-test .agents/skills/eclipse-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "eclipse-test" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-test into .agents/skills/eclipse-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-test", 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 gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/eclipse-test .cursor/skills/eclipse-test && 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 "eclipse-test" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-test into .cursor/skills/eclipse-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-test", 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/gradusnikov/eclipse-chatgpt-plugin.git --path .claude/skills/eclipse-test--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 gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/eclipse-test .gemini/skills/eclipse-test && 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 "eclipse-test" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-test into .gemini/skills/eclipse-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-test", 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 gradusnikov/eclipse-chatgpt-plugin eclipse-testInstalls 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 gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/eclipse-test .github/skills/eclipse-test && 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 "eclipse-test" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-test into .github/skills/eclipse-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-test", 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 gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gradusnikov/eclipse-chatgpt-plugin eclipse-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/eclipse-test .opencode/skills/eclipse-test && 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 "eclipse-test" agent skill from https://github.com/gradusnikov/eclipse-chatgpt-plugin/tree/main/.claude/skills/eclipse-test into .opencode/skills/eclipse-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eclipse-test", 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
eclipse-test- GitHub stars
- 171
- Token cost
- ~1k tokens
- SKILL.md length
- 389 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods.
- Works in 5 steps: Find test classes → Run specific test after code change → Run all tests before committing → …
- Tasks that involve Unit testing
- SKILL.md covers Test Tools, PDE Harness Tests, Build Tools and Typical Workflow, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Eclipse Test is an agent skill from gradusnikov/eclipse-chatgpt-plugin. Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods. Also build Maven projects.
Its SKILL.md is about 1k 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 Testing & QA, covering Unit testing. It works with JUnit, Model Context Protocol and Java. The repository describes itself as: Eclipse IDE as an MCP Server for AI Agents. The licence is MIT.
When your agent uses it
- Tasks that involve Unit testing
Example prompts
- “/eclipse-test”
Requirements
- Pre-approved tools (allowed-tools): mcp__eclipse-ide__runAllTests, mcp__eclipse-ide__runPackageTests, mcp__eclipse-ide__runClassTests, mcp__eclipse-ide__runTestMethod, mcp__eclipse-ide__findTestClasses, mcp__eclipse-ide__runMavenBuild, mcp__eclipse-ide__getConsoleOutput, mcp__eclipse-ide__getEffectivePom, mcp__eclipse-ide__listMavenProjects, mcp__eclipse-ide__getProjectDependencies, mcp__eclipse-ide__getCompilationErrors, mcp__eclipse-pde__runJUnitPluginTests, mcp__eclipse-pde__runJUnitPluginTestClass, mcp__eclipse-pde__runJUnitPluginTestClasses, mcp__eclipse-pde__getActiveTarget, mcp__eclipse-pde__reloadTarget
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Find test classes
- Run specific test after code change
- Run all tests before committing
- Build with Maven
- Check build output
What it can do on your machine
Read from SKILL.md and the folder at commit b789344. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
mcp__eclipse-ide__runAllTestsmcp__eclipse-ide__runPackageTestsmcp__eclipse-ide__runClassTestsmcp__eclipse-ide__runTestMethodmcp__eclipse-ide__findTestClassesmcp__eclipse-ide__runMavenBuildmcp__eclipse-ide__getConsoleOutputmcp__eclipse-ide__getEffectivePommcp__eclipse-ide__listMavenProjectsmcp__eclipse-ide__getProjectDependencies
…and 6 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Eclipse Test loads about 1k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 389 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
The full file from gradusnikov/eclipse-chatgpt-plugin at commit b789344, republished under its MIT licence (© gradusnikov). 389 words, ~1,026 tokens.
Download SKILL.mdSave it as
.claude/skills/eclipse-test/SKILL.md (or your agent's skills folder).- name
- eclipse-test
- description
- Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods. Also build Maven projects.
- allowed-tools
- mcp__eclipse-ide__runAllTests, mcp__eclipse-ide__runPackageTests, mcp__eclipse-ide__runClassTests, mcp__eclipse-ide__runTestMethod, mcp__eclipse-ide__findTestClasses, mcp__eclipse-ide__runMavenBuild, mcp__eclipse-ide__getConsoleOutput, mcp__eclipse-ide__getEffectivePom, mcp__eclipse-ide__listMavenProjects, mcp__eclipse-ide__getProjectDependencies, mcp__eclipse-ide__getCompilationErrors, mcp__eclipse-pde__runJUnitPluginTests, mcp__eclipse-pde__runJUnitPluginTestClass, mcp__eclipse-pde__runJUnitPluginTestClasses, mcp__eclipse-pde__getActiveTarget, mcp__eclipse-pde__reloadTarget
- argument-hint
- [project] [class or package]
Run Tests & Build in Eclipse
Execute JUnit tests and Maven builds using Eclipse's built-in infrastructure.
Test Tools
- runAllTests — Run all tests in a project. Provide
projectNameand optionaltimeout(default: 60s). - runPackageTests — Run tests in a specific package. Provide
projectNameandpackageName. - runClassTests — Run all tests in a specific test class. Provide
projectNameandclassName(fully qualified). - runTestMethod — Run a single test method. Provide
projectName,className, andmethodName. - findTestClasses — Find and classify tests as plain JUnit or PDE harness tests. PDE tests must use the
*PDETest.javanaming convention; likely harness-dependent misnamed tests are reported as warnings.
PDE Harness Tests
- runJUnitPluginTests — Run all plug-in tests in the PDE harness. Use for the classes listed under
PDE harness tests (*PDETest). - runJUnitPluginTestClass — Run one fully qualified
*PDETestclass. - runJUnitPluginTestClasses — Run a comma-separated set of fully qualified
*PDETestclasses in one PDE launch. Prefer it after a change touches several harness tests because Eclipse workbench startup is paid only once. The initial batch tool does not provide coverage; use the single-class or whole-project tools when coverage is required. - getActiveTarget / reloadTarget — Inspect or refresh the target platform when plug-in dependencies cannot resolve.
- Keep ordinary unit tests named
*Test.java; any test using Eclipse workspace, JDT, UI, platform, or OSGi runtime services must be named*PDETest.javaso discovery routes it to the PDE harness.
Show full SKILL.md (184 more words)Show less
Build Tools
- runMavenBuild — Run Maven the way Run As > Maven build does. Provide
projectNameandgoalswritten exactly as aftermvn(e.g.,clean install -DskipTests -pl module); optionalprofiles,properties,pomDirectory,offline,skipTests, andtimeout(seconds to wait before an operationId is returned). The result carries the exit code, every[ERROR]line and the tail of the log; the full log is in the console namedlaunchName. - getEffectivePom — Get the effective POM for a Maven project.
- listMavenProjects — List all Maven projects in the workspace.
- getProjectDependencies — Get Maven dependencies for a project.
Typical Workflow
Find test classes:
findTestClasses(projectName="myapp")Run specific test after code change:
runClassTests(projectName="myapp", className="com.example.MyServiceTest", timeout="60")Run all tests before committing:
runAllTests(projectName="myapp", timeout="120")Build with Maven:
runMavenBuild(projectName="myapp", goals="clean verify -DskipTests", timeout="300")Check build output:
getConsoleOutput()
Notes
- Tests run using JUnit 5 by default
- Run plain tests with
runClassTests/runAllTests; run*PDETestclasses with theeclipse-pdeharness tools - Test results include pass/fail status, execution time, and failure traces
- Use
getCompilationErrorsfirst to ensure code compiles before running tests - Maven build output goes to the Eclipse console — use
getConsoleOutputto retrieve it
© gradusnikov, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/eclipse-test of gradusnikov/eclipse-chatgpt-plugin.
Open the folder on GitHubat commit b789344
Compare with similar skills
Eclipse Test 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 |
|---|---|---|---|---|---|---|
| Eclipse Test this skillgradusnikov/eclipse-chatgpt-plugin | 171 | — | ~1k | Automated safety check: Pass | MIT | |
| Mps Run ConfigurationsJetBrains/MPS | 1.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Mps TestsJetBrains/MPS | 1.7k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Edt MCP Build TestDitriXNew/EDT-MCP | 295 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Debug Surefireeclipse-rdf4j/rdf4j | 420 | — | ~2.4k | Automated safety check: Pass | BSD-3-Clause | |
| Minecraft TestingJahrome907/minecraft-agent-skills | 166 | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Mps Tests
JetBrains/MPS
A skill your agent uses when writing or modifying tests inside MPS @tests models — NodesTestCase (typesystem, constraints, scopes, dataflow, generator output), EditorTestCase (intentions, actions…
Edt MCP Build Test
DitriXNew/EDT-MCP
How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo.
Debug Surefire
eclipse-rdf4j/rdf4j
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…
Minecraft Testing
Jahrome907/minecraft-agent-skills
Design and implement automated tests for current Minecraft 26.x or legacy 1.21.x mods and plugins using JUnit, MockBukkit, NeoForge Game Tests, or Fabric Game Tests.
Unit Testing
Leavesfly/Jimi
Java单元测试编写指南（基于JUnit和Mockito）
More from gradusnikov/eclipse-chatgpt-plugin
Eclipse Analyze
gradusnikov/eclipse-chatgpt-plugin
Analyze Java code using Eclipse JDT tools — type hierarchy, find references, call hierarchy, compilation errors, quick fixes, and import suggestions.
Eclipse Debug
gradusnikov/eclipse-chatgpt-plugin
Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes.
Eclipse Edit
gradusnikov/eclipse-chatgpt-plugin
Edit files in Eclipse projects using MCP tools. An agent skill from gradusnikov/eclipse-chatgpt-plugin.
Eclipse Run
gradusnikov/eclipse-chatgpt-plugin
Launch and stop Java applications in Eclipse. An agent skill from gradusnikov/eclipse-chatgpt-plugin.
Related
Works with
Categories
Questions about Eclipse Test
What does Eclipse Test do?
Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods. Eclipse Test is an agent skill from gradusnikov/eclipse-chatgpt-plugin. Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods.
When should I use Eclipse Test?
Eclipse Test fits situations like: tasks that involve Unit testing.
How do I install Eclipse Test in Claude Code?
Run `npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a claude-code`. Or copy the skill folder (.claude/skills/eclipse-test in gradusnikov/eclipse-chatgpt-plugin) into .claude/skills/eclipse-test in your project. Claude Code loads it when a task matches its description.
How do I install Eclipse Test in Codex?
Run `npx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a codex`. Or copy the skill folder (.claude/skills/eclipse-test in gradusnikov/eclipse-chatgpt-plugin) into .agents/skills/eclipse-test in your project. Codex loads it when a task matches its description.
Can I use Eclipse Test 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 gradusnikov/eclipse-chatgpt-plugin --skill eclipse-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eclipse-test, .gemini/skills/eclipse-test, .github/skills/eclipse-test and .opencode/skills/eclipse-test in your project.
What does Eclipse Test need to run?
SKILL.md names no scripts, command-line tools or credentials: Eclipse Test is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__eclipse-ide__runAllTests, mcp__eclipse-ide__runPackageTests, mcp__eclipse-ide__runClassTests, mcp__eclipse-ide__runTestMethod, mcp__eclipse-ide__findTestClasses, mcp__eclipse-ide__runMavenBuild, mcp__eclipse-ide__getConsoleOutput, mcp__eclipse-ide__getEffectivePom, mcp__eclipse-ide__listMavenProjects, mcp__eclipse-ide__getProjectDependencies, mcp__eclipse-ide__getCompilationErrors, mcp__eclipse-pde__runJUnitPluginTests, mcp__eclipse-pde__runJUnitPluginTestClass, mcp__eclipse-pde__runJUnitPluginTestClasses, mcp__eclipse-pde__getActiveTarget, mcp__eclipse-pde__reloadTarget.
Does Eclipse Test access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Eclipse Test 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 Eclipse Test use?
Eclipse Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Eclipse Test use?
About 1k tokens (SKILL.md is roughly 4.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 Eclipse Test?
Skills that share tags, products or a category with Eclipse Test: Mps Run Configurations (JetBrains/MPS, 1.7k stars), Mps Tests (JetBrains/MPS, 1.7k stars), Edt MCP Build Test (DitriXNew/EDT-MCP, 295 stars) and Debug Surefire (eclipse-rdf4j/rdf4j, 420 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eclipse Test?
gradusnikov (a GitHub user) maintains it in gradusnikov/eclipse-chatgpt-plugin, which has 171 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 28, 2026.
Source: gradusnikov/eclipse-chatgpt-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.