cfe-validate — Claude Code skill: what it does, how to install
Validates 1C configuration extension (CFE) source files, checking XML structure, role permissions, and borrowed objects before database loading.
/plugin marketplace add Nikolay-Shirokov/cc-1c-skills
/plugin install 1c-skills@cc-1c-skillsWhat cfe-validate does
This skill validates unpacked 1C extension source files. It scans Configuration.xml and metadata structure directly in source format using the cfe-validate.ps1 PowerShell script.
Setting -ConfigPath checks borrowed objects and main language against the source configuration. If the argument is omitted, the skill inspects .v8-project.json in the root folder to resolve configSrc. Without the base configuration, reference discrepancies might pass validation unnoticed.
PowerShell execution is mandatory because the runner calls powershell.exe. The tool checks structural integrity only; actual runtime compatibility with an infobase requires a separate /db-cfe-admin check call after loading.
What it helps with
- Validate XML structure and metadata properties of 1C CFE extensions
- Verify borrowed objects and language alignment against the base configuration
- Detect invalid role permissions prior to infobase import
- Limit the error output count using the
-MaxErrorsflag
Example prompts for the agent
- Validate the extension located at
src/cfe/myext - Run detailed validation on
src/cfe/myextmatching againstsrc/cf - Check
src/cfe/myext/Configuration.xmland stop after 30 errors
How to install cfe-validate
1Plugin marketplace
/plugin marketplace add Nikolay-Shirokov/cc-1c-skills/plugin install 1c-skills@cc-1c-skillsThis installs the whole 1c-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add Nikolay-Shirokov/cc-1c-skills --skill cfe-validate -a claude-code3Manually: put the files in place
~/.claude/skills/cfe-validate/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cfe-validate/
1Skills CLI (Vercel)
npx skills add Nikolay-Shirokov/cc-1c-skills --skill cfe-validate -a codex2Manually: put the files in place
.agents/skills/cfe-validate/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/cfe-validate/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Nikolay-Shirokov/cc-1c-skills cfe-validate2Manually: put the files in place
.github/skills/cfe-validate/SKILL.mdPlatform CLI
gemini skills install https://github.com/Nikolay-Shirokov/cc-1c-skills --path .claude/skills/cfe-validateManually: put the files in place
.devin/skills/cfe-validate/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cfe-validate
How to install cfe-validate in Claude Code?
Register the marketplace via /plugin marketplace add Nikolay-Shirokov/cc-1c-skills and install the package with /plugin install 1c-skills@cc-1c-skills.
What does cfe-validate do?
It inspects 1C configuration extension source files to catch XML issues, incorrect properties, and invalid borrowed objects before deployment.
Why pass the base configuration path via ConfigPath?
Comparing borrowed elements and the primary language against the base configuration avoids failures when applying the extension in the 1C platform.
Source text
SKILL.md · MIT
---
name: cfe-validate
description: Валидация расширения конфигурации 1С (CFE). Используй после создания или модификации расширения для проверки корректности
argument-hint: <ExtensionPath> [-ConfigPath <ConfigDir>] [-Detailed] [-MaxErrors 30]
allowed-tools:
- Bash
- Read
- Glob
---
# /cfe-validate — валидация расширения конфигурации (CFE)
Проверяет структурную корректность расширения: XML-формат, свойства, состав, заимствованные объекты, права ролей. Аналог `/cf-validate`, но для расширений.
Проверяются исходники. Применимость — уже после загрузки в базу: `/db-cfe-admin check`.
## Параметры
| Параметр | Обяз. | Умолч. | Описание |
|---------------|:-----:|---------|-------------------------------------------------|
| ExtensionPath | да | — | Путь к каталогу или Configuration.xml расширения |
| ConfigPath | нет | — | Каталог конфигурации, из которой заимствованы объекты |
| Detailed | нет | — | Подробный вывод (все проверки, включая успешные) |
| MaxErrors | нет | 30 | Остановиться после N ошибок |
| OutFile | нет | — | Записать результат в файл |
### ConfigPath
Указывай всегда, когда конфигурация-источник доступна: по ней сверяется связь заимствованных объектов с объектами конфигурации и основной язык. Без неё такие расхождения не ловятся, и расширение может пройти валидацию, а потом быть отвергнутым платформой.
Если пользователь не указал путь — определи сам:
1. Прочитай `.v8-project.json` из корня проекта
2. Разреши целевую базу (по имени, ветке или `default`)
3. Возьми её поле `configSrc`
## Команда
```powershell
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/cfe-validate.ps1" -ExtensionPath "src\cfe\extname"
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/cfe-validate.ps1" -ExtensionPath "src\cfe\extname\Configuration.xml"
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/cfe-validate.ps1" -ExtensionPath "src\cfe\extname" -ConfigPath "src\cf"
```
© Nikolay Shirokov · MIT · Nikolay-Shirokov/cc-1c-skills
