Agent skill

Edt MCP Tool Conventions

Cross-tool consistency contract for EDT-MCP tools — parameter naming, error shape, output format, pagination, not-found semantics, schema/README alignment.

AGPL-3.0Auto-check passedAgent Workflows

Install Edt MCP Tool Conventions

skills CLI

$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-tool-conventions -a claude-code

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

GitHub CLI

$ gh skill install DitriXNew/EDT-MCP edt-mcp-tool-conventions --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-tool-conventions .claude/skills/edt-mcp-tool-conventions && 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/

Paste into Claude Code

Install the "edt-mcp-tool-conventions" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-tool-conventions into .claude/skills/edt-mcp-tool-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-tool-conventions", 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

$skill-installer install https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-tool-conventions

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

skills CLI

$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-tool-conventions -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install DitriXNew/EDT-MCP edt-mcp-tool-conventions --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/edt-mcp-tool-conventions .agents/skills/edt-mcp-tool-conventions && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "edt-mcp-tool-conventions" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-tool-conventions into .agents/skills/edt-mcp-tool-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-tool-conventions", 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.

skills CLI

$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-tool-conventions -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install DitriXNew/EDT-MCP edt-mcp-tool-conventions --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/edt-mcp-tool-conventions .cursor/skills/edt-mcp-tool-conventions && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "edt-mcp-tool-conventions" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-tool-conventions into .cursor/skills/edt-mcp-tool-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-tool-conventions", 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

$ gemini skills install https://github.com/DitriXNew/EDT-MCP.git --path .claude/skills/edt-mcp-tool-conventions

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-tool-conventions -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install DitriXNew/EDT-MCP edt-mcp-tool-conventions --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/edt-mcp-tool-conventions .gemini/skills/edt-mcp-tool-conventions && rm -rf skills-src

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

Paste into Gemini CLI

Install the "edt-mcp-tool-conventions" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-tool-conventions into .gemini/skills/edt-mcp-tool-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-tool-conventions", 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.

GitHub CLI

$ gh skill install DitriXNew/EDT-MCP edt-mcp-tool-conventions

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

skills CLI

$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-tool-conventions -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

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

Paste into GitHub Copilot

Install the "edt-mcp-tool-conventions" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-tool-conventions into .github/skills/edt-mcp-tool-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-tool-conventions", 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.

skills CLI

$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-tool-conventions -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install DitriXNew/EDT-MCP edt-mcp-tool-conventions --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/edt-mcp-tool-conventions .opencode/skills/edt-mcp-tool-conventions && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "edt-mcp-tool-conventions" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-tool-conventions into .opencode/skills/edt-mcp-tool-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-tool-conventions", 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: edt-mcp-tool-conventions
GitHub stars: 296
Token cost: ~1.2k tokens
SKILL.md length: 500 words
Files: 1
Skills in repo: 24
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Cross-tool consistency contract for EDT-MCP tools — parameter naming, error shape, output format, pagination, not-found semantics, schema/README alignment.

Editing any class under tools/impl
SKILL.md covers Parameter naming, Read parameters typed, Error contract and Output format, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Adding a parameter

What it does

Edt MCP Tool Conventions is an agent skill from DitriXNew/EDT-MCP. Cross-tool consistency contract for EDT-MCP tools — parameter naming, error shape, output format, pagination, not-found semantics, schema/README alignment. Use when editing any class under tools/impl, adding a parameter, changing a tool's output, or reviewing a tool for consistency.

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 Technical documentation. The licence is AGPL-3.0.

When your agent uses it

Editing any class under tools/impl
Adding a parameter
Changing a tools output
Reviewing a tool for consistency

Example prompts

“/edt-mcp-tool-conventions”

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 Tool Conventions loads about 1.2k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 500 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~77
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). 500 words, ~1,187 tokens.

Download SKILL.mdSave it as .claude/skills/edt-mcp-tool-conventions/SKILL.md (or your agent's skills folder).

name: edt-mcp-tool-conventions
description: Cross-tool consistency contract for EDT-MCP tools — parameter naming, error shape, output format, pagination, not-found semantics, schema/README alignment. Use when editing any class under tools/impl, adding a parameter, changing a tool's output, or reviewing a tool for consistency.

EDT-MCP — tool contract (consistency)

The same concept must behave the same way across every tool. This skill is the canon to hold to.

Parameter naming

Concept	Canonical	Anti-example
Project	`projectName`	`project`
Module	`modulePath` (from `src/`; the resolver also accepts an absolute path)	`module`, or a decomposed `objectName+moduleType+formName+commandName`
Fully-qualified name	`fqn`	—
Object name	`objectName`	—
Synonym / language	`synonym` / `language`	—
Limit / offset	`limit` / `offset`	`maxResults`, `maxDepth`

Parameter names are lowerCamelCase — ToolContractConsistencyTest fails snake_case. When renaming a parameter, accept the old name as a documented alias for one release, then deprecate.

Read parameters typed

Read arguments via JsonUtils.extractStringArgument/extractIntArgument/extractBooleanArgument/extractObjectArray; check required ones via JsonUtils.requireArguments(params, "a", "b") (returns a ready error-JSON or null). Don't parse a raw Map<String,String> by hand. (There is no typed ToolParams class — JsonUtils is the canon.)

Every parameter read in execute() must be declared in getInputSchema() (otherwise it is invisible to schema-driven clients) and vice versa.

Error contract

Errors only via ToolResult.error(...) (machine-readable: success=false + message/code). Never return a bare "Error: …" / "Project not found" string, never let an exception escape the tool.
"project not found" — one text/shape through the shared ProjectContext resolver.

Output format

Similar tools use the same format (don't make one JSON and another markdown without a reason). The plugin default is markdown (see IMcpTool.ResponseType).
JSON fields use one style (don't mix camelCase/snake_case in similar responses).
not-found — one semantics: an empty list for "list", an error for "get a specific one". Don't mix null/empty/error.

Show full SKILL.md (267 more words)Show less

Response format policy (Markdown vs JSON)

structuredContent/JSON is for the client to consume (UI rendering, verbatim round-trip of identifiers, a future outputSchema), NOT for the agent to read. MARKDOWN is the default (token-efficient, readable).

A tool returns JSON only when its result carries:

(a) round-trip IDs another tool consumes;
(b) machine-structured positions (e.g. error line/column);
(c) a declared outputSchema;
(d) UI-rendered data.

Action/confirmation/status results with none of these return MARKDOWN. write_module_source is the reference MARKDOWN action tool; AbstractMetadataWriteTool subclasses stay JSON because they return the created object's round-trip FQN.

Tool families that stay JSON, and why:

metadata-writes (create_metadata, modify_metadata, delete_metadata) → addressed by FQN (a);
debug / profiling tools → launch / application / breakpoint IDs + live session state (a);
validate_query → error line/col (b);
list_configurations → config identities (a);
clean_project, update_database → destructive status whose JSON shape is consumed by e2e (d-like).

Markdown action tools (revalidate_objects, export_configuration_to_xml, import_configuration_from_xml, write_module_source) emit status + paths/counts only — no round-trip data. Build the body with FrontMatter + a markdown summary; any table goes through MarkdownUtils (escapes every cell); errors still via ToolResult.error(...).

Pagination

Use the shared Pagination (utils/Pagination.java: one limit/offset, one truncation-notice format). Don't invent a per-tool scheme.

Result / markdown assembly

Through ToolResult/JsonUtils and the shared markdown-table builder, not a hand-rolled StringBuilder.

Schema ↔ code ↔ README

BuiltInToolRegistrar is the source of truth for the tool set; the README catalog + the e2e golden (tests/e2e/tools_list.golden.json) must match it. A new tool changes the golden → regenerate (EDT_MCP_UPDATE_GOLDEN=1).
Every tool: a non-empty meaningful description and a description for every parameter.

Class placement

tools/impl/ holds IMcpTool classes only. Utilities/abstract bases go in utils//tools/base/. Project/model resolution goes through the shared helpers (skill edt-mcp-architecture). ru/en correctness — skill edt-mcp-bilingual.

Files

Just SKILL.md in .claude/skills/edt-mcp-tool-conventions of DitriXNew/EDT-MCP.

Open the folder on GitHubat commit 6d18531

Compare with similar skills

Edt MCP Tool Conventions 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 Tool Conventions compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Edt MCP Tool Conventions this skillDitriXNew/EDT-MCP	296	—	~1.2k	Automated safety check: Pass	AGPL-3.0	2 days ago
Claude Docs Consultantcentminmod/my-claude-code-setup	2.7k	—	~959	Automated safety check: Pass	MIT	2 days ago
MCP Documentation Standardpatsnap/mcp	113	—	~1.2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Olore Claude Code Latestolorehq/olore	104	—	~901	Automated safety check: Pass	MIT	today
Researching With Deepwikiaiskillstore/marketplace	433	—	~1.2k	Automated safety check: Pass	None	today
Typescript Styletjx666/vscode-mcp	105	—	~961	Automated safety check: Pass	Custom licence	2 mo ago

Similar skills

Claude Docs Consultant
centminmod/my-claude-code-setup
Consult official Claude Code documentation from code.claude.com using selective fetching.
2.7k GitHub stars~959 tokensUpdated 2 days ago
Agent WorkflowsAuto-check passed
MCP Documentation Standard
patsnap/mcp
Create or update Patsnap MCP catalog documentation in this repository.
113 GitHub stars~1.2k tokensUpdated 1 mo ago
Agent WorkflowsAuto-check passed
Olore Claude Code Latest
olorehq/olore
Local claude-code documentation reference (latest). An agent skill from olorehq/olore.
104 GitHub stars~901 tokensUpdated today
Agent WorkflowsAuto-check passed
Researching With Deepwiki
aiskillstore/marketplace
Research GitHub, GitLab, and Bitbucket repositories using DeepWiki MCP server.
433 GitHub stars~1.2k tokensUpdated today
Agent WorkflowsAuto-check passed
Typescript Style
tjx666/vscode-mcp
TypeScript code style and repo conventions for VSCode MCP — inference vs explicit types, ESM import suffixes, zod schema contracts, async VSCode/Node APIs, JSON-safe IPC results, JSDoc for public…
105 GitHub stars~961 tokensUpdated 2 mo ago
DevelopmentAuto-check passed
Score Harness
ruvnet/metaharness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness.
696 GitHub stars~613 tokensUpdated today
DevelopmentAuto-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 →…
296 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.
296 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…
296 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…
296 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.
296 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.
296 GitHub stars~2.1k tokensUpdated 2 days ago
Auto-check passed

Questions about Edt MCP Tool Conventions

What does Edt MCP Tool Conventions do?

Cross-tool consistency contract for EDT-MCP tools — parameter naming, error shape, output format, pagination, not-found semantics, schema/README alignment. Edt MCP Tool Conventions is an agent skill from DitriXNew/EDT-MCP. Cross-tool consistency contract for EDT-MCP tools — parameter naming, error shape, output format, pagination, not-found semantics, schema/README alignment.

When should I use Edt MCP Tool Conventions?

Edt MCP Tool Conventions fits situations like: editing any class under tools/impl; adding a parameter; changing a tools output; reviewing a tool for consistency.

How do I install Edt MCP Tool Conventions in Claude Code?

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

How do I install Edt MCP Tool Conventions in Codex?

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

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

What does Edt MCP Tool Conventions need to run?

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

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

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

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

Skills that share tags, products or a category with Edt MCP Tool Conventions: Claude Docs Consultant (centminmod/my-claude-code-setup, 2.7k stars), MCP Documentation Standard (patsnap/mcp, 113 stars), Olore Claude Code Latest (olorehq/olore, 104 stars) and Researching With Deepwiki (aiskillstore/marketplace, 433 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Edt MCP Tool Conventions?

DitriXNew (a GitHub user) maintains it in DitriXNew/EDT-MCP, which has 296 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.

Install Edt MCP Tool Conventions

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

EDT-MCP — tool contract (consistency)

Parameter naming

Read parameters typed

Error contract

Output format

Response format policy (Markdown vs JSON)

Pagination

Result / markdown assembly

Schema ↔ code ↔ README

Class placement

Files

Compare with similar skills

Similar skills

More from DitriXNew/EDT-MCP

Related

Questions about Edt MCP Tool Conventions