1C Configuration Validation

VerifiedSafe

Validates the structure of a 1C configuration's Configuration.xml file, checking XML well-formedness, properties, child objects, language references, and file/directory existence. Use after creating or modifying a configuration to catch structural errors.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#1c#configuration-validation#xml#powershell

Recommended for

Automated summary

Validates 1C configuration files for structural errors in Configuration.xml, including XML well-formedness, property values, child objects, and language files.

Strengths

  • Checks both XML structure and semantic rules (e.g., valid enum values, language references).
  • Provides clear error/warning output with exit codes for automation.
  • Supports limiting the number of reported errors with -MaxErrors parameter.
  • Can output results to a file for later review.

Limitations

  • Requires PowerShell execution environment, limiting cross-platform use.
  • Only checks configuration metadata, not business logic or code syntax.
  • Limited to specific 1C version formats (2.17/2.20).
When to use it

Use after creating or modifying a 1C configuration to ensure structural correctness before deployment or further development.

When not to use it

Do not use for validating runtime behavior, business logic, or code-level errors; for those use 1C's built-in syntax checker.

Security analysis

Safe
Quality score90/100

The skill runs a local PowerShell script for XML validation, with no destructive, exfiltrating, or obfuscated actions. The script path is fixed and arguments are user-provided paths, posing no injection or remote execution risk.

No concerns found

How this analysis is made

Examples

Validate empty configuration
Validate the 1C configuration at path upload/cfempty for structural errors.
Validate real configuration
Run cf-validate on the configuration at C:\WS\tasks\cfsrc\acc_8.3.24 and show the results.
Validate with error limit
Validate the 1C configuration in test-tmp/cf but stop after 10 errors.

name: cf-validate description: Валидация конфигурации 1С. Используй после создания или модификации конфигурации для проверки корректности argument-hint: <ConfigPath> [-MaxErrors 30] allowed-tools:

  • Bash
  • Read
  • Glob

/cf-validate — валидация конфигурации 1С

Проверяет Configuration.xml на структурные ошибки: XML well-formedness, InternalInfo, свойства, enum-значения, ChildObjects, DefaultLanguage, файлы языков, каталоги объектов.

Параметры и команда

| Параметр | Описание | |----------|----------| | ConfigPath | Путь к Configuration.xml или каталогу выгрузки | | MaxErrors | Остановиться после N ошибок (default: 30) | | OutFile | Записать результат в файл (UTF-8 BOM) |

powershell.exe -NoProfile -File .claude/skills/cf-validate/scripts/cf-validate.ps1 -ConfigPath "<путь>"

Выполняемые проверки

| # | Проверка | Серьёзность | |---|----------|-------------| | 1 | XML well-formedness, MetaDataObject/Configuration, version 2.17/2.20 | ERROR | | 2 | InternalInfo: 7 ContainedObject, валидные ClassId, уникальность | ERROR | | 3 | Properties: Name непустой, Synonym, DefaultLanguage, DefaultRunMode | ERROR/WARN | | 4 | Properties: enum-значения (11 свойств) | ERROR | | 5 | ChildObjects: валидные имена типов (44 типа), нет дубликатов, порядок типов | ERROR/WARN | | 6 | DefaultLanguage ссылается на существующий Language в ChildObjects | ERROR | | 7 | Файлы языков Languages/<name>.xml существуют | WARN | | 8 | Каталоги объектов из ChildObjects существуют (spot-check) | WARN |

Вывод

=== Validation: Configuration.МояКонфигурация ===

[OK]    1. Root structure: MetaDataObject/Configuration, version 2.17
[OK]    2. InternalInfo: 7 ContainedObject, all ClassIds valid
[OK]    3. Properties: Name="МояКонфигурация", Synonym present
[OK]    4. Property values: 11 enum properties checked
[OK]    5. ChildObjects: 1 types, 1 objects, order correct
[OK]    6. DefaultLanguage "Language.Русский" found in ChildObjects
[OK]    7. Language files: 1/1 exist
[OK]    8. Object directories: spot-check passed

=== Result: 0 errors, 0 warnings ===

Exit code: 0 = OK, 1 = errors.

Примеры

# Пустая конфигурация
... -ConfigPath upload/cfempty

# Реальная конфигурация
... -ConfigPath C:\WS\tasks\cfsrc\acc_8.3.24

# С лимитом ошибок
... -ConfigPath test-tmp/cf -MaxErrors 10

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/1c-configuration-validation-mm5t8b9u/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/1c-configuration-validation-mm5t8b9u' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/1c-configuration-validation-mm5t8b9u/download' --output '.skill-downloads/1c-configuration-validation-mm5t8b9u/SKILL.md.part' && mv '.skill-downloads/1c-configuration-validation-mm5t8b9u/SKILL.md.part' '.skill-downloads/1c-configuration-validation-mm5t8b9u/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/1c-configuration-validation-mm5t8b9u/SKILL.md' && test -s '.skill-downloads/1c-configuration-validation-mm5t8b9u/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/cf-validate' && cp -R '.skill-downloads/1c-configuration-validation-mm5t8b9u' '.claude/skills/cf-validate'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/1c-configuration-validation-mm5t8b9u'

openskills read '1c-configuration-validation-mm5t8b9u'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/1c-configuration-validation-mm5t8b9u/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills