1c-enterprise-skill: developing 1C configurations from XML and BSL
1c-enterprise-skill
A skill with a linter and templates: an agent creates and edits 1C 8.3 configurations in XML and BSL sources without manual entry in the Configurator
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Scripts create and overwrite configuration files in the given folder
- Generated metadata is loaded into a database through the Configurator, and an error in it can break the load
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/1c-enterprise-skillDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Scripts create and overwrite configuration files in the given folder
- Generated metadata is loaded into a database through the Configurator, and an error in it can break the load
This is third-party code. Review the repository files before installing.
What it does
The skill helps an agent develop 1C:Enterprise 8.3 configurations straight from source files. `SKILL.md` collects metadata schema rules: which tags are valid for documents, catalogs and forms, how to set string qualifiers and where to call server functions. The `templates/` folder holds reference XML for a catalog, a document, accumulation and information registers, a data processor and a form. Three Python scripts cover the routine. `init_project.py` creates a configuration skeleton, `validate_config.py` checks XML, forbidden tags, qualifiers and BSL procedure contexts before loading, and `generate_config_dump_info.py` builds the `ConfigDumpInfo.xml` manifest with correct UUIDs and UTF-8 with BOM encoding. The result is loaded in the Configurator with the "Load configuration from files" command.
Who it is for. 1C developers who keep configurations in Git and ask agents to generate metadata, forms and BSL modules.
Good fit when
- A new configuration is needed from scratch and building a skeleton with correct metadata containers by hand is tedious
- On load the Configurator answers "Metadata container is missing" because of the dump manifest
- Generating an accumulation register fails with a DBMS error about TEXT fields in an index
- Before a commit to Git you need a linter that checks XML and BSL call contexts
Not a fit when
- Ordinary forms and platforms below 8.3: the skill is written for the 1C 8.3 managed application
- You need operations on existing databases and extensions: skills with `cfe-*` and `meta-*` fit better
- The task requires COM or an online connection to a database: the skill works with files only
Example request
Create a "Warehouse" configuration skeleton, add a "Nomenclature" catalog and a "Receipt" document, then check it all with the linterLimitations
The skill is written for the 1C 8.3 managed application and does not cover ordinary forms. The linter checks the schema and typical mistakes, and the final check is still done by the Configurator on load and on updating the database configuration. The README has badges and promotional wording such as "solves 100%", so treat it as the author claim. It needs Python and Windows or Linux, MIT license. One author, release 2.0.0, the last commit in September 2026.
How to disable. Delete the `1c-enterprise-skill` folder from the agent skills directory, for example `~/.claude/skills/` or `~/.gemini/config/skills/`.
FAQ
How do I create a new configuration?
Run `python scripts/init_project.py <folder> <name>`: the script builds a skeleton with metadata containers and `ConfigDumpInfo.xml`.
What does the linter check?
XML syntax, forbidden tags, number and string qualifiers, BSL procedure contexts and the manifest. On an error it prints the file and line.
What does the metadata container error mean?
The Configurator got a wrong manifest root tag or a file without the UTF-8 BOM marker. The `generate_config_dump_info.py` script writes the right header and encoding.
How do I load the result into 1C?
In the Configurator open "Configuration", choose "Load configuration from files", point to the folder and then update the database configuration with F7.
Which agents does the skill work with?
The README names Antigravity, Claude and Cursor: the skill is copied into the agent skills directory, for example `~/.gemini/config/skills/`.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsSkills covering the full 1C:Enterprise 8.3 development cycle, from XML sources to publishing and web client testing
A large set of skills, rules and commands that let an agent build and parse 1C sources in the platform's format, without the Designer
A 1C development skill collection for Codex and Claude Code: XML sources, forms, data composition, infobases, web publishing and an HTTP test bridge
A skill for 1C platform batch operations: build and unpack data processors, load and dump configurations and extensions, launch the base
An Agent Skills plugin for 1C:Enterprise 8.3 development: core domain rules plus a build-and-database skill, tested across three environments
XBSL Skills for 1C:Element
XBSL Skills
20 skills for 1C:Element projects: configuration objects, forms, access rights, deployment and Playwright checks
README in short
The README explains typical fatal 1C generation errors and their fixes, the repository structure, a quick start with three scripts, connecting to agents and the list of version 2.0.0 rules.
README badge
Original SKILL.md
--- name: 1c-enterprise-skill description: >- Expert engineering skill and authoritative guide for developing, scaffolding, validating, and troubleshooting 1C:Enterprise 8.3 (1С:Предприятие) managed application configurations directly from source files (XML + BSL). Use whenever creating or modifying 1C metadata, managed forms, registers, documents, catalogs, BSL business logic, ConfigDumpInfo.xml manifests, or resolving 1C XML parser and DBMS errors. --- # 1C:Enterprise 8.3 Managed Application Engineering Skill ## 1. When to Activate This Skill Activate this skill whenever: - Creating a new 1C:Enterprise 8.3 configuration from scratch or adding new metadata objects. - Writing or refactoring business logic in **BSL** (1C Enterprise Script). - Creating or editing **Managed Forms** (Управляемые формы), form XML layouts, or form event handlers. - Configuring **Registers** (Регистры накопления, Регистры сведений) and document posting mechanisms. - Resolving 1C Designer errors during import: