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
- 1 ★ on the repository
- Last commit
Extended access
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
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/onec-element-ideDetects 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.
- 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
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.
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.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA 1C development skill collection for Codex and Claude Code: XML sources, forms, data composition, infobases, web publishing and an HTTP test bridge
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
A skill for fast 1C extension development: an edit-load-test loop, storage discipline and AI features through TAB's AI Library
A 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
A local read-only MCP server suite for 1C: a Rust code indexer, metadata skills, a prompt gallery and platform help search, with evidence-backed answers
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.