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
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Uploads changed files back into the cloud panel and triggers app publishing
- Asks for the control panel key and secret directly in the chat with the agent
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/onec-element-ideDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run in a terminal in the project folder
npx skills add tab1c/onec-element-ide --skill onec-element-ide -a claude-code -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add tab1c/onec-element-ide --skill onec-element-ide -a cursor -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add tab1c/onec-element-ide --skill onec-element-ide -a github-copilot -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add tab1c/onec-element-ide --skill onec-element-ide -a codex -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add tab1c/onec-element-ide --skill onec-element-ide -a gemini-cli -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add tab1c/onec-element-ide --skill onec-element-ide -a cline -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add tab1c/onec-element-ide --skill onec-element-ide -a roo -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
A fork of Roo Code, same .roo folders.
Run in a terminal in the project folder
npx skills add tab1c/onec-element-ide --skill onec-element-ide -a opencode -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Paste into the Codex chat: pull the repository https://github.com/TAB1C/onec-element-ide into ~/.codex/skills/onec-element-ide, read SKILL.md and follow it for the given IDE, asking for the 1C:Element panel key and secret if not provided.
Other ways from the author
Подтяни или обнови репозиторий https://github.com/TAB1C/onec-element-ide в ~/.codex/skills/onec-element-ide, прочитай ~/.codex/skills/onec-element-ide/SKILL.md и дальше работай по нему для IDE <IDE id или URL>. Запроси у меня ключ и секрет панели управления 1C:Element, если я не передал их сразу.
The exact text the README suggests pasting into the chat.
This is third-party code. Review the repository files before installing.
What it does
The skill asks the user for the 1C:Element control panel key and secret if not provided upfront, downloads project sources or an export locally through the panel's API, helps edit .xbsl and .yaml files in a local working folder and check for hardcoded values via local search, uploads the fixed files or package back to the panel, and verifies through the IDE or panel that changes are actually visible in the cloud source view. If the project shows Git or Source Control in its interface, the skill helps with commit, sync and push, then runs a publish-update-test loop after upload, separating 1C-wrapper issues from external backend issues.
Who it is for. For developers running a project in the 1C:Element cloud control panel who want to edit code locally instead of using the web editor.
Good fit when
- You need to download a 1C:Element project's sources for local editing
- You need an edit-upload-publish-test loop for a 1C:Element app
- You need to verify that edits actually landed in the cloud source view
Not a fit when
- You have no access to the 1C:Element control panel: a key and secret are required
- You need classic desktop 1C, not the cloud 1C:Element
Example request
Download the project from 1C:Element, fix the hardcoded URL in config.yaml and upload it back with a publishLimitations
The skill targets Codex and relies on the 1C:Element control panel API, whose details are not documented in the README itself. It asks the user for the panel key and secret directly in the chat, which calls for care when entering them. Small project: a README, SKILL.md and one helper script for the IDE ID.
How to disable. Delete the ~/.codex/skills/onec-element-ide directory.
Security check
- Uploads changed files back into the cloud panel and triggers app publishing
- Asks for the control panel key and secret directly in the chat with the agent
README in short
The Russian README gives a ready-to-paste message for Cursor or Codex that pulls or updates the skill into ~/.codex/skills/onec-element-ide, describes seven steps of the skill's work from requesting the key to publishing and testing, and points to a fallback prompt in references/starter-prompt.md if auto-detection fails.
FAQ
What if the skill does not pick up automatically?
Use the fallback prompt from references/starter-prompt.md, as noted in the README.
Does the skill verify changes reached the cloud?
Yes, a dedicated step checks through the IDE or panel that changes are visible in the cloud source view before moving on to publishing.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything