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 Architecture

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

AGPL-3.0Auto-check passedAgent Workflows

Install Edt MCP Architecture

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

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

GitHub CLI
$ gh skill install DitriXNew/EDT-MCP edt-mcp-architecture --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-architecture .claude/skills/edt-mcp-architecture && 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-architecture
GitHub stars
295
Token cost
~1.2k tokens
SKILL.md length
466 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
AGPL-3.0

At a glance

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.

  • Starting work in this plugin
  • SKILL.md covers Package layout, Canonical shared APIs (use,…, What NOT to do (anti-patterns) and Related
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Deciding where new code belongs

What it does

Edt MCP Architecture is an agent skill from 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. Use when starting work in this plugin, deciding where new code belongs, or before adding/refactoring an MCP tool.

Its SKILL.md is about 1.2k 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 Agent Workflows, covering MCP servers and Refactoring. It works with Model Context Protocol and Java. The licence is AGPL-3.0.

When your agent uses it

  • Starting work in this plugin
  • Deciding where new code belongs
  • Before adding/refactoring an MCP tool

Example prompts

  • “/edt-mcp-architecture”

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

    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

Edt MCP Architecture loads about 1.2k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 466 words of instructions outside code blocks.

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

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). 466 words, ~1,238 tokens.

Download SKILL.mdSave it as .claude/skills/edt-mcp-architecture/SKILL.md (or your agent's skills folder).
name
edt-mcp-architecture
description
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. Use when starting work in this plugin, deciding where new code belongs, or before adding/refactoring an MCP tool.

EDT-MCP — target architecture

A 1C:EDT plugin with an MCP server (~62 tools). This skill maps how it should be (the project is mid-refactor toward shared helpers). If a helper below does not yet exist in code, it is a refactor task — see the card in .devtool/features/.

Package layout

Root: mcp/bundles/com.ditrix.edt.mcp.server/src/com/ditrix/edt/mcp/server

PackageHoldsRule
tools/impl/one class per MCP tool (implements IMcpTool)registered tools only; no utilities/bases here
tools/IMcpTool, McpToolRegistrythe contract and the registry
tools/metadata/metadata formattersoutput rendering for read tools
utils/shared helpersreusable pieces go here
protocol/MCP/JSON-RPC layer: ToolResult, JsonUtils, JsonSchemaBuilderresponse/schema assembly
tags/, groups/two Navigator featuresmust share a common base (see below)
McpServer.java, Activator.javatransport and OSGi lifecyclenot a tool catalog

Canonical shared APIs (use, don't duplicate)

All helpers below exist in code. Verify the exact method name before calling (grep/Read).

  • Project resolution → ProjectContext.of(projectName) (.exists(), .project(), .notFoundMessage(name)). Do not repeat ResourcesPlugin.getWorkspace()... by hand. (Metadata write tools get project+config via AbstractMetadataWriteTool.resolveProjectAndConfig.)
  • BM model access → BmTransactions.read(model, name, op) / write(model, name, op). Reads in a read boundary, writes in a write boundary. Persist a metadata write to disk via BmTransactions.forceExportToDisk(project, [topFqn, configFqn]) (a bare write only enqueues the async export).
  • Tool parameters → JsonUtils.extractStringArgument/extractIntArgument/extractBooleanArgument/extractObjectArray + JsonUtils.requireArguments(params, ...). Don't parse the Map by hand. (There is no ToolParams class.)
  • Canonical key names → McpKeys (protocol/McpKeys.java) for the param/result keys shared across many tools: PROJECT_NAME, APPLICATION_ID, MODULE_PATH, LIMIT (input params) and MESSAGE, ACTION, PROJECT, ERROR (result keys). Use these in getInputSchema()/execute()/result-building instead of bare "projectName" literals; file-specific keys stay as private static final String constants in the tool. (error/success are owned by ToolResult — only hand-built error fields outside it use McpKeys.ERROR.)
  • Metadata object/type resolution (bilingual) → MetadataTypeUtils (findObject, normalizeFqn); an existing node/member by FQN — MetadataNodeResolver.resolveExisting/resolveForCreate; a form — FormStructureReader.resolveMdForm. These are the shared bilingual resolvers — don't write your own.
  • Synonym language → MetadataLanguageUtils.resolveLanguageCode(config, explicit) + getSynonymForLanguage(map, code). The synonym key is the language code (getLanguageCode()), NOT getName().
  • Result/error → ToolResult: ToolResult.success().put(...) / ToolResult.error(...). Errors only via ToolResult.error(...).toJson(), never a bare string, never an exception escaping the tool.
  • Pagination → the shared Pagination (utils/Pagination.java; one limit/offset, one "truncated" format).
  • Markdown tables → the shared builder (escapes |/newline), not a per-tool StringBuilder.
  • Tool registration → BuiltInToolRegistrar, not a list inside McpServer. EDT services — via Activator.getDefault().getXxx() or ServiceAccess.get(IFoo.class) (+ the package in MANIFEST Import-Package).
Show full SKILL.md (95 more words)Show less

What NOT to do (anti-patterns)

  • Don't copy project/module/BM resolution into each tool — call the shared helper.
  • Don't put utilities or abstract bases in tools/impl/ — only IMcpTool classes (move-nontool-helpers-out-of-impl).
  • Don't grow god-classes: RenameMetadataObjectTool/FindReferencesTool share MetadataReferenceLocator (extract-metadata-reference-locator); McpServer is being split (decompose-mcpserver).
  • tags/* and groups/* — don't copy a third such stack; both features should inherit a common association-storage/service/refactoring base (extract-tags-groups-shared-base).
  • Two-language (ru/en) correctness — the edt-mcp-bilingual skill.
  • Cross-tool contract (parameter naming, errors, output) — the edt-mcp-tool-conventions skill.
  • Adding a new tool — the edt-mcp-new-tool skill.
  • Build and tests — the edt-mcp-build-test skill.
  • The full refactor task list — the .devtool/features/*.md board.

© 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-architecture of DitriXNew/EDT-MCP.

Open the folder on GitHubat commit 6d18531

Compare with similar skills

Edt MCP Architecture 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 Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Edt MCP Architecture this skillDitriXNew/EDT-MCP295—~1.2kAutomated safety check: PassAGPL-3.0
Idea MCPdtprj/dongting208—~698Automated safety check: PassApache-2.0
Harness Engineering LifecycleArenukvern/mcp_flutter386—~1.6kAutomated safety check: PassMIT
Eclipse Editgradusnikov/eclipse-chatgpt-plugin172—~1.1kAutomated safety check: PassMIT
Verify Multilang Supportjohnhuang316/code-index-mcp1k—~908Automated safety check: PassMIT
MCP Debuggerdebugmcp/mcp-debugger172—~3.8kAutomated safety check: PassMIT

Similar skills

  • Idea MCP

    dtprj/dongting

    IntelliJ IDEA MCP for Java code analysis, testing, refactoring, and project navigation.

    208 GitHub stars~698 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Harness Engineering Lifecycle

    Arenukvern/mcp_flutter

    Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists.

    386 GitHub stars~1.6k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed

  • Eclipse Edit

    gradusnikov/eclipse-chatgpt-plugin

    Edit files in Eclipse projects using MCP tools. An agent skill from gradusnikov/eclipse-chatgpt-plugin.

    172 GitHub stars~1.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Verify Multilang Support

    johnhuang316/code-index-mcp

    A skill your agent uses when validating code-index-mcp language strategies, tree-sitter symbol extraction, calledby or import baselines, or sample projects under test/sample-projects after parser…

    1k GitHub stars~908 tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed

  • MCP Debugger

    debugmcp/mcp-debugger

    A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…

    172 GitHub stars~3.8k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Amplicode Install

    Amplicode/spring-skills

    Installs the Amplicode IntelliJ plugin into IntelliJ IDEA (Ultimate/Community) and GigaIDE on the user's machine.

    126 GitHub stars~2.6k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

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 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.

    295 GitHub stars~1.4k 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

Works with

Categories

Questions about Edt MCP Architecture

What does Edt MCP Architecture do?

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. Edt MCP Architecture is an agent skill from 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.

When should I use Edt MCP Architecture?

Edt MCP Architecture fits situations like: starting work in this plugin; deciding where new code belongs; before adding/refactoring an MCP tool.

How do I install Edt MCP Architecture in Claude Code?

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

How do I install Edt MCP Architecture in Codex?

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

Can I use Edt MCP Architecture 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-architecture -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-architecture, .gemini/skills/edt-mcp-architecture, .github/skills/edt-mcp-architecture and .opencode/skills/edt-mcp-architecture in your project.

What does Edt MCP Architecture need to run?

SKILL.md names no scripts, command-line tools or credentials: Edt MCP Architecture is instructions for the agent only.

Does Edt MCP Architecture 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 Edt MCP Architecture 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 Architecture use?

Edt MCP Architecture 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 Architecture use?

About 1.2k tokens (SKILL.md is roughly 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 Architecture?

Skills that share tags, products or a category with Edt MCP Architecture: Idea MCP (dtprj/dongting, 208 stars), Harness Engineering Lifecycle (Arenukvern/mcp_flutter, 386 stars), Eclipse Edit (gradusnikov/eclipse-chatgpt-plugin, 172 stars) and Verify Multilang Support (johnhuang316/code-index-mcp, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Edt MCP Architecture?

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.