Agent skill

Edt MCP Project Metadata

Inspect and safely change 1C metadata, including roles, rights, and RLS, through current EDT-MCP structured operations.

AGPL-3.0Auto-check passedAgent Workflows

Install Edt MCP Project Metadata

skills CLI

$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-project-metadata -a claude-code

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

GitHub CLI

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

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-project-metadata -a codex

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

GitHub CLI

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

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

GitHub CLI

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

--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-project-metadata -a gemini-cli

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

GitHub CLI

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

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

At a glance

Inspect and safely change 1C metadata, including roles, rights, and RLS, through current EDT-MCP structured operations.

Works in 6 steps: Resolve metadata by programmatic Name,… → Use find_references only for targets… → Consult the current guide, preview… → …
Tasks that involve MCP servers
SKILL.md covers Purpose and trigger, Operating rule, Task boundary and Primary workflow, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Edt MCP Project Metadata is an agent skill from DitriXNew/EDT-MCP. Inspect and safely change 1C metadata, including roles, rights, and RLS, through current EDT-MCP structured operations. Not for raw XML edits or plugin development.

Its SKILL.md is about 690 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 Hooks and plugins. It works with Model Context Protocol. The licence is AGPL-3.0.

When your agent uses it

Tasks that involve MCP servers
Tasks that involve Hooks and plugins

Example prompts

“/edt-mcp-project-metadata”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Resolve metadata by programmatic Name, never by localized synonym. Only
Use find_references only for targets supported by its current help; use the
Consult the current guide, preview destructive or cascading effects, then
For roles and RLS, follow the current guide's ordering and effective-rights
For extension work, identify the base and exact extension project. Call
Re-read the target, validate it, and re-check relevant references. Use an

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 Project Metadata loads about 685 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 315 words of instructions outside code blocks.

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

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). 315 words, ~685 tokens.

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

name: edt-mcp-project-metadata
description: Inspect and safely change 1C metadata, including roles, rights, and RLS, through current EDT-MCP structured operations. Not for raw XML edits or plugin development.

EDT-MCP metadata workflow

Purpose and trigger

Use this skill to inspect or change exact 1C metadata objects, members, roles, rights, RLS, or extension composition through structured EDT-MCP operations.

Operating rule

Read and apply the common operating rules before this workflow.

Task boundary

Resolve the exact project and metadata FQN. Use edt-mcp-project-forms for managed-form structure and edt-mcp-project-query-dcs for DCS content; never edit metadata XML to bypass the structured surface.

Primary workflow

Resolve metadata by programmatic Name, never by localized synonym. Only the FQN type token is bilingual (for example Catalog/Справочник). Read the target with get_metadata_details, including the current writable surface when needed.
Use find_references only for targets supported by its current help; use the relevant mutation preview and bounded consumer checks for other targets.
Consult the current guide, preview destructive or cascading effects, then use the smallest create_metadata, modify_metadata, rename_metadata_object, delete_metadata, or adopt_metadata_object operation.
For roles and RLS, follow the current guide's ordering and effective-rights model, re-read the complete affected state, and treat partial application as possible until readback proves otherwise.
For extension work, identify the base and exact extension project. Call adopt_metadata_object with the base as projectName and an explicit extensionProjectName when more than one extension is possible. Adoption covers the metadata object; route BSL override/interception work to edt-mcp-project-local-fix and validate the extension afterward.
Re-read the target, validate it, and re-check relevant references. Use an authorized runtime test when effective access or RLS behavior is acceptance.

Authority rule

Rename, delete, cascade, force, adoption, rights/RLS changes, and rollback need authority for their exact targets and consequences. A preview is not approval.

Stop rule

Stop on ambiguous FQN, unsupported mutation, incomplete destructive preview, missing authority, failed persistence/readback, or required runtime proof that cannot be performed safely.

Completion signal

Return the exact metadata target, confirmed structured diff and persistence, targeted validation/reference evidence, effective-rights evidence when applicable, and explicit runtime or completeness gaps.

Files

Just SKILL.md in agent/skills/edt-mcp-project-metadata of DitriXNew/EDT-MCP.

Open the folder on GitHubat commit 6d18531

Compare with similar skills

Edt MCP Project Metadata 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 Project Metadata compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Edt MCP Project Metadata this skillDitriXNew/EDT-MCP	295	—	~685	Automated safety check: Pass	AGPL-3.0	2 days ago
MCP Integration for Pluginsanthropics/claude-plugins-official	38k	11 repos	~3.1k	Automated safety check: Pass	Apache-2.0	yesterday
Crush Configurationcharmbracelet/crush	29k	—	~3.7k	Automated safety check: Pass	Custom licence	today
OpenpetsOpenPetsHQ/openpets	1.3k	—	~2.1k	Automated safety check: Pass	MIT	yesterday
Claude Automation Recommenderanthropics/claude-plugins-official	38k	3 repos	~2.7k	Automated safety check: Notes	Apache-2.0	yesterday
Mistral Vibe Plugin Creatormistralai/mistral-vibe	5.1k	—	~3.1k	Automated safety check: Pass	Apache-2.0	2 days ago

Similar skills

MCP Integration for Plugins
anthropics/claude-plugins-official
Official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
38k GitHub starsUsed in 11 repos~3.1k tokens
Agent WorkflowsAuto-check passed
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
29k GitHub stars~3.7k tokensUpdated today
Agent WorkflowsAuto-check passed
Openpets
OpenPetsHQ/openpets
A skill your agent uses whenever the user wants to build, extend, debug, test, validate, locally load, package, or publish an OpenPets plugin; work with the OpenPets Plugin SDK v3, plugin manifest…
1.3k GitHub stars~2.1k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Claude Automation Recommender
anthropics/claude-plugins-official
Official
Scans a codebase and suggests which Claude Code hooks, subagents, skills, plugins and MCP servers fit its stack, without changing any files.
38k GitHub starsUsed in 3 repos~2.7k tokens
Agent WorkflowsAuto-check: notes
Mistral Vibe Plugin Creator
mistralai/mistral-vibe
Official
Shows how to build a Vibe plugin package in the Agent Plugins 1.0 format, with a plugin.json manifest and optional skills, MCP servers, hooks and other components.
5.1k GitHub stars~3.1k tokensUpdated 2 days ago
Agent WorkflowsAuto-check passed
Agent Setup Health Audit
tw93/Waza
Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.
7.2k GitHub stars~5.2k tokensUpdated today
Agent WorkflowsAuto-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 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

Model Context Protocol

Questions about Edt MCP Project Metadata

What does Edt MCP Project Metadata do?

Inspect and safely change 1C metadata, including roles, rights, and RLS, through current EDT-MCP structured operations. Edt MCP Project Metadata is an agent skill from DitriXNew/EDT-MCP. Inspect and safely change 1C metadata, including roles, rights, and RLS, through current EDT-MCP structured operations.

When should I use Edt MCP Project Metadata?

Edt MCP Project Metadata fits situations like: tasks that involve MCP servers; tasks that involve Hooks and plugins.

How do I install Edt MCP Project Metadata in Claude Code?

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

How do I install Edt MCP Project Metadata in Codex?

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

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

What does Edt MCP Project Metadata need to run?

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

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

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

About 685 tokens (SKILL.md is roughly 2.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 Project Metadata?

Skills that share tags, products or a category with Edt MCP Project Metadata: MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars), Crush Configuration (charmbracelet/crush, 29k stars), Openpets (OpenPetsHQ/openpets, 1.3k stars) and Claude Automation Recommender (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Edt MCP Project Metadata?

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.

Install Edt MCP Project Metadata

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

EDT-MCP metadata workflow

Purpose and trigger

Operating rule

Task boundary

Primary workflow

Authority rule

Stop rule

Completion signal

Files

Compare with similar skills

Similar skills

More from DitriXNew/EDT-MCP

Related

Questions about Edt MCP Project Metadata