New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Edt MCP Build Test

by DitriXNew in 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.

AGPL-3.0Auto-check passedTesting & QA

Install Edt MCP Build Test

skills CLI
$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-build-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install DitriXNew/EDT-MCP edt-mcp-build-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/edt-mcp-build-test .claude/skills/edt-mcp-build-test && rm -rf skills-src

Use ~/.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/

Facts

Skill name
edt-mcp-build-test
GitHub stars
295
Token cost
~1.4k tokens
SKILL.md length
641 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
AGPL-3.0

At a glance

How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo.

  • Building the plugin
  • SKILL.md covers Layout, Build, Live redeploy (Tier 2 — the… and Unit tests — conventions, plus 4 more sections
  • Calls bash, mvn and npx
  • Verifying a change before committing

What it does

Edt MCP Build Test is an agent skill from 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. Use when building the plugin, running or writing tests, or verifying a change before committing.

Its SKILL.md is about 1.4k 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 MCP servers, End-to-end testing and Unit testing. It works with Model Context Protocol and Java. The licence is AGPL-3.0.

When your agent uses it

  • Building the plugin
  • Verifying a change before committing

Example prompts

  • “/edt-mcp-build-test”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 6d18531. 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:

    • bash
    • mvn
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, 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

Edt MCP Build Test loads about 1.4k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 641 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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 DitriXNew/EDT-MCP at commit 6d18531, republished under its AGPL-3.0 licence (© DitriXNew). 641 words, ~1,378 tokens.

Download SKILL.mdSave it as .claude/skills/edt-mcp-build-test/SKILL.md (or your agent's skills folder).
name
edt-mcp-build-test
description
How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo. Use when building the plugin, running or writing tests, or verifying a change before committing.

EDT-MCP — build and tests

Layout

  • Maven/Tycho reactor: mcp/ (bom, bundles, features, repositories, targets, tests).
  • Unit tests: mcp/tests/com.ditrix.edt.mcp.server.tests/src (JUnit4, a plug-in fragment).
  • E2E: tests/e2e/run_all.py + tools/test_<tool>.py (Python; runs the MCP server against TestConfiguration/).

Build

A Tycho build from mcp/ (Maven, JDK 25 - Tycho 5 needs 21+ and the EDT 2026.2 platform is Java 25; the bundle itself still compiles to release 17). The artifact is a p2 update-site in repositories/com.ditrix.edt.mcp.server.repository/target.

A local build is available — use it to validate Java edits (don't claim "verified by review/grep only"). The canonical script is source/compile.sh (it reproduces the CI flow mvn clean verify -T 1C from .github/workflows/build.yml):

bash
# from the repo root: compile + unit tests
bash source/compile.sh
# compile only (no Surefire) — faster
bash source/compile.sh --skip-tests
  • The toolchain (JDK 25 + Maven 3.9+) is often not on PATH — pass it explicitly: --java-home <JDK25 home> --maven-home <maven home> (or env JAVA_HOME/MAVEN_HOME). The exact paths are machine-specific — discover them on the spot, don't hardcode into committed files. Exact options are in README "Building from source".
  • The first build is slow: Tycho pulls the EDT p2 repository (edt.1c.ru) + the Eclipse SDK (hundreds of MB). Once the caches are warm (~/.m2/repository/p2, .cache/tycho) it runs in ~1 minute. If the caches are absent and there's no network, the build legitimately can't run — say so, don't fake "green".
  • Unit tests need the target platform too (Mockito/JUnit come from the p2 target, not plain Maven Central) — a green compile.sh is the real proof for Java edits; grep only catches anchor/text problems.

Live redeploy (Tier 2 — the only proof of runtime behaviour)

A green build proves Java logic; only a redeploy proves a tool's schema, description, response and behaviour. The loop itself (non-elevated EDT copy, edt-redeploy.ps1, MCP server UP on 8765, exit 1 ≠ failure, anti-stale jar check, kill + -clean when EDT wedges) is in edt-mcp-testing and edt-mcp-ready-to-deploy. The traps that belong to the build:

  • Redeploy without a -Build flag only swaps the LAST built jar — run compile.sh first (or pass -Build), else you ship stale code and validate the previous build.
  • Kill the whole stand before swapping: taskkill /IM 1cedt.exe /T /F, plus 1cv8.exe if an infobase is running. Terminate both again when done.
  • Inspect payloads with Invoke-RestMethod (PowerShell), not curl — curl mangles nested JSON. Tools with a JSON responseType put the data in result.structuredContent; content[0].text is only a Done/Error placeholder. Do the handshake first: the server validates its session, so a cold tools/call answers 400 — send initialize, keep the Mcp-Session-Id it returns and put that header on every later request (the e2e harness client does this for you).
  • Infobase-dependent tools (debug / run / YAXUnit / profiling) need the infobase (or a launch) started first.
Show full SKILL.md (221 more words)Show less

Unit tests — conventions

  • One XxxToolTest per tool (tools/impl/), JUnit4.
  • Base pattern: tool.execute(params) + a sentinel-message check (e.g. "Project not found") for argument validation. Reference: WriteModuleSourceToolTest.
  • Bilingual invariant: for tools that resolve metadata/code, a case with a Russian identifier/synonym (reference WriteModuleSourceToolTest.testResolveRussianObjectName). See skill edt-mcp-bilingual.

Coverage gate

BuiltInToolTestCoverageTest (unit) fails the build if a registered tool has no XxxToolTest; the e2e coverage ratchet (tools/test_coverage_ratchet.py) fails the suite if a tools/list tool has no test_<tool>.py. Adding a tool without a test fails the build.

E2E

tests/e2e/run_all.py (+ tools/test_<tool>.py, one per tool) runs scenarios against the live server and TestConfiguration/ with git-fixture isolation. The round-trip of Cyrillic synonyms and the synonym-keyed-by-language-code check live in test_create_metadata.py / test_get_metadata_details.py. A new tool — add tools/test_<tool>.py. Full guide: edt-mcp-e2e-testing (and tests/e2e/SKILL.md).

Protocol conformance

A separate gate from the e2e business-logic suite: the official modelcontextprotocol/conformance suite validates the SERVER against the MCP wire spec (handshake, capabilities, session-id, isError, ping, SSE). Lives in tests/conformance/ (baseline.yml pins the intentional gaps; README.md explains the layer split). Run: npx @modelcontextprotocol/conformance@latest server --url http://127.0.0.1:8765/mcp --spec-version 2025-11-25 --expected-failures tests/conformance/baseline.yml.

Before committing

  • Build passes
  • Unit tests green; a new/changed tool has a test
  • If metadata/code resolution is touched — a bilingual case exists
  • (if applicable) the e2e scenario is updated
  • For a finished piece of work, run the full edt-mcp-ready-to-deploy checklist (build → README → live redeploy → golden → full e2e → conformance → clean tree)

© DitriXNew, AGPL-3.0. 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/edt-mcp-build-test of DitriXNew/EDT-MCP.

Open the folder on GitHubat commit 6d18531

Compare with similar skills

Edt MCP Build 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.

Edt MCP Build Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Edt MCP Build Test this skillDitriXNew/EDT-MCP295—~1.4kAutomated safety check: PassAGPL-3.0
Frontmcp Testingagentfront/frontmcp146—~10kAutomated safety check: NotesApache-2.0
Qwen Code E2E TestingQwenLM/qwen-code28k—~2.1kAutomated safety check: PassApache-2.0
Adding LLM MCP ToolsTriliumNext/Trilium38k—~2.5kAutomated safety check: PassAGPL-3.0
Glance TestDebugBase/glance156—~827Automated safety check: PassMIT
Playwright Testingchongdashu/vibejam-starter-pack149—~2.2kAutomated safety check: PassNone

Similar skills

  • Frontmcp Testing

    agentfront/frontmcp

    A skill your agent uses for anything about testing FrontMCP servers: writing or running unit, integration, and E2E tests and reaching the 95%+ coverage bar.

    146 GitHub stars~10k tokensUpdated 3 days ago
    Testing & QAAuto-check: notes

  • Qwen Code E2E Testing

    QwenLM/qwen-code

    Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.

    28k GitHub stars~2.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Adding LLM MCP Tools

    TriliumNext/Trilium

    A skill your agent uses when adding, changing, or reviewing an LLM/MCP tool in Trilium (the defineTools definitions under packages/trilium-core/src/services/llm/tools/ —…

    38k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Glance Test

    DebugBase/glance

    Run E2E browser tests on any web application using Glance MCP.

    156 GitHub stars~827 tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.2k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Frontend Playwright E2E

    ansible/ansible-ui

    Write, run, and debug Playwright E2E / integration / live tests.

    113 GitHub stars~2.5k tokensUpdated yesterday
    Testing & QAAuto-check: notes

More from DitriXNew/EDT-MCP

All 24 skills in this repo

  • Edt MCP Autopilot

    DitriXNew/EDT-MCP

    Autonomous, spec-driven, multi-agent pipeline that takes an EDT-MCP task or issue end-to-end — research → critics → architect → parallel development → review loop → tests → live-stand check →…

    295 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed

  • Edt MCP E2E Testing

    DitriXNew/EDT-MCP

    How to write/run the AUTOMATED black-box e2e suite (tests/e2e/) that covers every EDT-MCP tool (62 today) against a live server with git-fixture isolation, happy + negative + error-quality coverage…

    295 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Edt MCP Tool Descriptions

    DitriXNew/EDT-MCP

    How to size, write and A/B-test the text of a tool — its description and its inputSchema parameter prose — so that cutting it does not cost call quality, and so that a tool that IS getting called…

    295 GitHub stars~3k tokensUpdated 2 days ago
    Auto-check passed

  • Edt MCP Yaxunit

    DitriXNew/EDT-MCP

    How to write and run YAXUnit unit tests for a 1C configuration through 1C:EDT + the EDT-MCP runyaxunittests / debugyaxunittests tools.

    295 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed

  • Edt MCP Testing

    DitriXNew/EDT-MCP

    How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration.

    295 GitHub stars~2.1k tokensUpdated 2 days ago
    Auto-check passed

  • Edt MCP Architecture

    DitriXNew/EDT-MCP

    Map of the EDT-MCP plugin's target architecture — where the shared helpers live, the layering rules, and the canonical way to do project/metadata/code resolution.

    295 GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Edt MCP Build Test

What does Edt MCP Build Test do?

How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo. Edt MCP Build Test is an agent skill from 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.

When should I use Edt MCP Build Test?

Edt MCP Build Test fits situations like: building the plugin; verifying a change before committing.

How do I install Edt MCP Build Test in Claude Code?

Run `npx skills add DitriXNew/EDT-MCP --skill edt-mcp-build-test -a claude-code`. Or copy the skill folder (.claude/skills/edt-mcp-build-test in DitriXNew/EDT-MCP) into .claude/skills/edt-mcp-build-test in your project. Claude Code loads it when a task matches its description.

How do I install Edt MCP Build Test in Codex?

Run `npx skills add DitriXNew/EDT-MCP --skill edt-mcp-build-test -a codex`. Or copy the skill folder (.claude/skills/edt-mcp-build-test in DitriXNew/EDT-MCP) into .agents/skills/edt-mcp-build-test in your project. Codex loads it when a task matches its description.

Can I use Edt MCP Build 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 DitriXNew/EDT-MCP --skill edt-mcp-build-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/edt-mcp-build-test, .gemini/skills/edt-mcp-build-test, .github/skills/edt-mcp-build-test and .opencode/skills/edt-mcp-build-test in your project.

What does Edt MCP Build Test need to run?

Going by SKILL.md and its folder, Edt MCP Build Test needs the command-line tools its instructions call (bash, mvn and npx). Our summary lists: Node.js.

Does Edt MCP Build Test access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Edt MCP Build 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 Edt MCP Build Test use?

Edt MCP Build Test is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Edt MCP Build Test use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Edt MCP Build Test?

Skills that share tags, products or a category with Edt MCP Build Test: Frontmcp Testing (agentfront/frontmcp, 146 stars), Qwen Code E2E Testing (QwenLM/qwen-code, 28k stars), Adding LLM MCP Tools (TriliumNext/Trilium, 38k stars) and Glance Test (DebugBase/glance, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Edt MCP Build Test?

DitriXNew (a GitHub user) maintains it in DitriXNew/EDT-MCP, which has 295 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.

Source: DitriXNew/EDT-MCP on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.