1C Copilot Skills
A GitHub Copilot skill, dev-1c, for 1C:Enterprise 8.2 development: research, design, phased planning and BSL code review against a checklist
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- The skill only guides research and code writing; database changes still go through the developer's own separate steps
- It references an external mcp_1c MCP server whose access is configured separately
Install
Manual install
.\deploy.ps1Deploys dev-1c into the personal ~/.copilot/skills folder, available in every project. With -ProjectPath it also adds rdpi-1c into a specific project.
This is third-party code. Review the repository files before installing.
What it does
The main dev-1c skill gives Copilot a full 1C 8.2 development cycle: codebase research via mcp_1c tools, design with architecture artifacts, splitting the plan into phases, and implementing BSL code with style and design-compliance review. The bsl-standards.md reference carries the review checklist and code standards, and mcp-1c-tools.md documents the available 1C MCP tools. A second skill, rdpi-1c, is scoped to a specific Swedbank integration project and knows its files and CSV operation codes, so it only makes sense inside that project. Both skills deploy via a deploy.ps1 script into Copilot's personal folder or into a specific project.
Who it is for. For 1C developers on the 8.2 platform who use GitHub Copilot in VS Code and want a structured process instead of free-form code generation.
Good fit when
- You need to add a feature or fix a bug in 1C 8.2 with explicit research, design, plan and implement phases
- You want a BSL standards checklist for code review
- You already run a 1C MCP server and need a reference for its tools
Not a fit when
- Your project is not on the 1C:Enterprise 8.2 platform
- You want to use rdpi-1c outside its original Swedbank integration project; it is not general-purpose
- You use an agent other than GitHub Copilot
Example request
I need to add handling for a new operation type in 1C, start with codebase researchLimitations
The dev-1c skill references mcp_1c tools, but the MCP server itself is not in the repo and must be set up separately. The second skill, rdpi-1c, is tightly scoped to a specific Swedbank integration project and is not usable elsewhere as-is. The README frames the repo as a working tool for one author and one team, and several sections (registers, reports, transactions) are marked as not yet written.
How to disable. Delete the skill folder from ~/.copilot/skills or from the project's .github/skills, wherever deploy.ps1 put it.
Security check
- The skill only guides research and code writing; database changes still go through the developer's own separate steps
- It references an external mcp_1c MCP server whose access is configured separately
README in short
The README has four sections: how to use the skills (explicit invocation with / and automatic activation by phrase), how to develop them further (which file is responsible for what, how to verify changes), how to create new skills (structure, a SKILL.md template, three levels of context loading), and a list of what is still missing, including planned narrow skills like query-1c and form-1c. It ends with a quick reference for deploy and activation commands.
FAQ
How is dev-1c different from rdpi-1c?
dev-1c fits any 1C 8.2 project, while rdpi-1c knows the specific files and operation codes of a Swedbank integration project and is not general-purpose outside it.
Does the skill need an MCP server?
The mcp-1c-tools.md reference documents the mcp_1c tools the skill uses during research, but the server itself must be set up separately.
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