メニュー
Establish the current EDT-MCP server surface, exact 1C project, and safe route before business-project work. Not for developing the EDT-MCP plugin.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/DitriXNew/EDT-MCP --skill edt-mcp-project-sessionコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
How to write and run black-box end-to-end (e2e) tests for the EDT-MCP server. Covers the architecture (shared harness + one file per tool + orchestrator), the git-fixture isolation protocol, happy-path AND negative coverage, error-quality assertions, and the anti-cheat rules. An agent that has never seen this project should be able to write a correct, non-cheating test after reading this.
How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration. One reference per tool under references/<family>/, each with the exact MCP call, the real expected result, and gotchas. Use when validating an MCP tool end-to-end by actually calling it (for build/unit tests see edt-mcp-build-test).
Investigate 1C BSL behavior, dependencies, impact, and implementation differences through EDT-MCP. Read-only by default; not for plugin development.
SKILL.md を表示中
| name | edt-mcp-project-session |
| description | Establish the current EDT-MCP server surface, exact 1C project, and safe route before business-project work. Not for developing the EDT-MCP plugin. |
Use this skill to establish the exact EDT-MCP route, project, and required capability before another business-project workflow begins.
Read and apply the common operating rules before this workflow.
Discover only facts needed for the current 1C project task. Do not use this skill for EDT-MCP plugin development or repeat preflight whose evidence remains current.
get_edt_version -> list_projects ->
get_configuration_properties -> get_problem_summary, then
list_subsystems only when project navigation needs it. Resolve the exact
project and kind before continuing.router_status; use get_server_status
only when installed surface or EDT state affects the task.list_toolsets and use
enable_toolset only as current help permits. Follow the client's supported
catalog-refresh or reconnect route; do not assume either behavior.get_tool_guide for the selected unfamiliar, destructive, or cascading
operation rather than preloading unrelated guides.Name, never by localized synonym. Only
the FQN type token is bilingual (for example Catalog/Справочник).Discovery does not authorize project mutation, destructive operations, runtime effects, optional Git/Workmate use, or substitution of a different project.
Stop when project ownership or route is ambiguous, the required capability remains unavailable, or the next operation lacks a proven target or authority.
Record the selected project, project kind when relevant, routed server surface, required visible capability, chosen task skill, and any unresolved ambiguity.