XBSL Skills for 1C:Element
XBSL Skills
20 skills for 1C:Element projects: configuration objects, forms, access rights, deployment and Playwright checks
- 45 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs Python scripts that create and modify project files
- Deployment uses an Element client secret
- Playwright checks may create records in the app
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/xbsl-skillsDetects 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.
- Runs Python scripts that create and modify project files
- Deployment uses an Element client secret
- Playwright checks may create records in the app
This is third-party code. Review the repository files before installing.
What it does
The set teaches the agent the structure of 1C:Element projects in XBSL. Skills initialize a project, add subsystems, catalogs, documents and enumerations, and build list forms, card views and a dashboard home page. Others handle register movements, row-level security, scheduled tasks, safe renames with reference updates and read-only YAML validation. xbsl-deploy manages apps on 1C:Enterprise.Element, and xbsl-playwright saves repeatable e2e tests.
Who it is for. Developers on the 1C:Element platform who want the agent to handle routine metadata object creation and deployment.
Good fit when
- You need a catalog, document or enumeration created from a description
- You need forms, attachments or images added to a configuration object
- You need to deploy a branch to Element or check app status
- You want to test a deployed app's forms and keep the tests
Not a fit when
- Projects on classic 1C:Enterprise 8 rather than Element
- The agent environment lacks Python 3.10+
Example request
Create a Counterparties catalog with INN and KPP fieldsLimitations
19 skills require Python 3.10+, and xbsl-validate also needs PyYAML 6. xbsl-playwright needs Node.js and @playwright/test in the app project. Deployment requires ELEMENT_BASE_URL, ELEMENT_CLIENT_ID and ELEMENT_CLIENT_SECRET in .env. When updating, replace the skill folder entirely.
How to disable. Delete the xbsl-* folders from the project's .claude/skills or from ~/.codex/skills.
FAQ
Do I need existing tests or sources for Playwright checks?
No. An app URL and a description of the check are enough. The agent reuses an existing Playwright setup or creates an e2e folder.
Which deploy variables are optional?
ELEMENT_APP_ID, ELEMENT_PROJECT_ID, ELEMENT_BRANCH and ELEMENT_SPACE_ID. They save time on each deploy.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA linter with autofixes, an LSP, docs search and metadata scaffolding for 1C:Element, plus an MCP server and a VS Code extension on one engine
Skills 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
1C:Element IDE skill
onec-element-ide
A Codex skill for the cloud 1C:Element IDE: pulls sources through the control panel, helps edit them locally and pushes fixes back
1C SSL Skill
1С:БСП Skill
A skill for applying the 1C Standard Subsystems Library 3.1.11: real modules and methods, execution context, stable versus internal API
A 1C development skill collection for Codex and Claude Code: XML sources, forms, data composition, infobases, web publishing and an HTTP test bridge
README in short
XBSL Skills is a set of skills for the 1C:Element platform, compatible with Claude Code and other agents. The README lists 20 skills from UUID generation to RLS and dashboards, and covers requirements and installation by copying into .claude/skills or ~/.codex/skills. It includes example requests, the Element project layout and deploy configuration via .env. The repository ships pytest tests and a GitHub Pages site. MIT license.
README badge
Original SKILL.md
---
name: xbsl-meta-add
description: >
Создание объекта конфигурации в 1С:Элемент (XBSL). Используй этот скилл когда
пользователь хочет создать новый объект метаданных в проекте
compatibility: Requires Python 3.
---
Во всех командах ниже `{python}` означает `python` в Windows и `python3` в macOS/Linux/WSL. Выбирай команду сразу по текущей ОС, не запускай оба варианта.
# Создание объекта конфигурации в 1С:Элемент
Перед созданием или дополнением `.xbsl` прочитай `docs/xbsl-spec.md`; API
HttpСервиса и других объектов сверяй по reference-файлам скилла и официальным
источникам из registry.
## HttpСервис — быстрый путь
Если тип объекта `HttpСервис` — используй скрипт вместо шагов 1–4:
### Шаг 1 — Dry-run
```bash
{python} skills/xbsl-meta-add/scripts/generate_http.py \
--name <ИмяСервиса> \
--url /<ресурс> \
--routes "GET /, POST /, GET /{id}, PUT /{id}, DELETE /{id}" \
--root <корень>
```
Опциональные флаги:
- `--subsystem <ИмяПодсистемы>` — если нужно выбрать конкретную подсистему
- `--access РазрешеноАутентифицированным` — добавить контроль доступа; без `--access` блок контроля доступа не добавляется.
`/api` зарезервирован платформой и отклоняется: платформа автоматически добавляет
этот префикс к `КорневойUrl`.
Показать вывод пользователю. Если сервис уже существует — спросить: заменить или отмена.
Если скрипт завершился с ошибкой — сообщи пользователю и остановись.
### Шаг 2 — Применить (только после подтверждения)
```bash
{python} skills/xbsl-meta-add/scripts/generate_http.py \
--name <ИмяСервиса> \
--url /<ресурс> \
--routes "GET /, POST /, GET /{id}, PUT /{id}, DELETE /{id}" \
--root <корень_проекта> \
--apply
```
### Шаг 3 — Итог
Перечислить созданные файлы из вывода скрипта:
- `<ИмяСервиса>.yaml` — объект HttpСервис с маршрутами
- `<ИмяСервиса>.xbsl` — заготовки обработчиков