xbsl-en-skills
A Claude Code skill for deploying a 1C:Enterprise.Element (xBSL) project with English as the development language to the cloud via the Console API
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Switches a production cloud application to a new build image
- Uses the Console API client id and secret from .env
Install
- Works in
- Services
Manual install
cp -r xbsl-en-deploy /path/to/project/.claude/skills/Per-project install. For a user-wide install, copy into ~/.claude/skills instead of this path.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Switches a production cloud application to a new build image
- Uses the Console API client id and secret from .env
This is third-party code. Review the repository files before installing.
What it does
The package contains one skill, xbsl-en-deploy, for the 1C:Enterprise.Element platform where English is set as the development language (keywords like method, val, throw instead of Russian ones). The skill covers two ways to deploy an application to the 1cmycloud cloud: syncing the bound git branch on the platform side with no local build, and building a local .xasm image, uploading it and switching the application to it. It walks through build version numbering, resolving local libraries into the same image, polling application status until Running, and the mandatory check for apply errors, since a Running status alone does not guarantee a clean deploy. The skill ships no build or upload script of its own, only the sequence and the production lessons behind it.
Who it is for. For 1C developers who run a 1C:Enterprise.Element project with English as the development language and deploy it to the 1cmycloud cloud.
Good fit when
- You need to deploy or update a 1C:Enterprise.Element app in the cloud via the Console API
- Your project uses English xBSL identifiers and keywords instead of Russian ones
- You want to understand the difference between building a local .xasm image and syncing a git branch on the platform
Not a fit when
- Your project is classic 1C:Enterprise with BSL and XML configuration, a different platform
- Your Element project uses Russian as the development language, not English
Example request
Deploy the current Element project changes to the cloud application and confirm the status is Running with no apply errorsLimitations
The skill has no build or upload script, only the process and the pitfalls; you write your own script against your Console API. It deliberately omits exact endpoint paths and request fields, pointing to the official 1C:Element documentation instead. It is a single-skill, single-author package verified on one production project.
How to disable. Delete the xbsl-en-deploy folder from the project's .claude/skills or from the user's global skills folder.
FAQ
Does the skill build and upload the image itself?
No, it describes the sequence and teaches the agent to interpret statuses and errors; you bring your own build and upload script.
Does it work for classic 1C?
No, only for the 1C:Enterprise.Element (xBSL) platform with English as the development language; classic BSL-based 1C is a different product.
Discussion
No questions or reviews yet.
Related
All 1C:Element 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
An MCP server with full-text search over local 1C:Element documentation, including your own markdown and PDF files
A skill for 1C platform batch operations: build and unpack data processors, load and dump configurations and extensions, launch the base
Skills for the Melezh web server on the 1C platform
1C Melezh Skills
Six SKILL.md skills covering install, handlers, scheduled tasks, the web console and diagnostics for the Melezh web server for 1C:Enterprise
An unofficial CLI, MCP server and Python library for the 1C:Enterprise.Element Console API: apps, builds and deploys with apply verification
The all-deploy skill puts a site, app or API online: audit, preview, response check and rollback
README in short
The README explains that most existing Element skill sets use Russian keywords, while this package targets English as the development language instead. It describes the single xbsl-en-deploy skill, installation by copying the folder into .claude/skills, and scope: platform 9.2, English development language, not classic 1C. It notes the patterns were verified on a real production application, not assembled from documentation. MIT license.
README badge
Original SKILL.md
--- name: xbsl-en-deploy description: > Deploy a 1C:Enterprise.Element project to a cloud application (1cmycloud) via the management Console API. Use when asked to deploy, publish, update, restart, or check the status of an Element application, or to push the current sources to a cloud app. Covers the two deploy paths (build-from-sources and platform-side git pull), the environment/credentials needed, and the operational gotchas learned in production (which project directory to point at, local-library resolution, version numbering, waiting for Running, surfacing apply errors). This is a clean-room process guide - bring your own build/upload script or the platform's git integration. --- # Deploying an Element project to a cloud application