SkillFoxx

1c-agent-kit skill

A shared skill and tooling infrastructure for 1C development, wired in as a git submodule and laid out across several agents at once

  • 0 ★ on the repository
  • Last commit
  • MIT
Skill

Broad access

Why this level

  • Skills like db-server and epf-add-form perform operations against a real 1C database and its objects
  • The link scripts change the consumer project's file structure, including the git index and .gitignore
All reasons and checks
Russian stack

pzayash/1c-agent-kitAuthor:pZayash

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/1c-agent-kit

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Skills like db-server and epf-add-form perform operations against a real 1C database and its objects
  • The link scripts change the consumer project's file structure, including the git index and .gitignore

This is third-party code. Review the repository files before installing.

What it does

The project is not a ready set of skills to copy but an infrastructure for teams running several 1C projects who want to centrally update shared skills, rules and tools. A consumer wires the repo in as a git submodule under harness/ and runs a bootstrap script that links the vanilla cc-1c-skills, a custom Cursor overlay (rules, commands, skills like bsl-check, db-server, epf-add-form, code-analysis-orchestrator) and tools like mcp-call for JSON-RPC calls to 1C MCP servers, into several places at once: .cursor/skills, .agents/skills, .claude/skills, .pi/skills and the Kilo Code/OpenCode plugin folders. A dedicated kit-layout and kit-agent engine keeps link integrity on Windows (junctions) and Linux (symlinks), guards against kit files accidentally landing in the consumer's git history, and gives agents guard rules via hooks.

Who it is for. For teams running several 1C repositories who want one centrally updated base of skills and rules for agents instead of copying them into each project by hand.

Good fit when

  • You run several 1C projects and want to update shared skills and rules centrally through one submodule
  • Your team uses several agents at once, Cursor, pi, Kilo Code or OpenCode, and wants one skill layout across all of them
  • You need protection against kit files accidentally landing in the consumer's git history and drift control for AGENTS.md

Not a fit when

  • You just need one ready skill for one project: the git submodule and linking complexity is not worth it
  • You have no experience with git submodules, symlinks and Windows junctions: the tool documents many sharp edges in detail precisely because they really occur

Example request

Check the BSL code with the bsl-check skill and start db-server for the test database

Limitations

This is infrastructure for a specific, fairly complex workflow of the author's own team: a submodule, a layout engine, guard hooks, symlink vs junction conflicts across OSes, and AGENTS.md managed-section drift. The README devotes most of its length to pitfalls of exactly this scheme, which signals its operational weight. The canonical architecture decisions live in a separate, non-public pilot repo, so some context is unavailable from outside.

How to disable. Remove the harness gitlink from the consumer (git submodule deinit and rm harness) and delete the symlinks/junctions it created under .cursor, .agents, .claude, .pi.

FAQ

Can I just copy the skills without a submodule?

Technically yes, but the tool is built around a git submodule specifically for centralized updates, and its link scripts and pruning keep the copy in sync with upstream.

Does this only work with Cursor?

No, bootstrap also lays out skills for .claude, pi and the Kilo Code/OpenCode plugins, though the main rules/commands overlay is built for Cursor.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A set of 52 Claude Code skills and agents, plus Cursor rules, for the full 1C:Enterprise 8.3 development cycle, assembled from several community projects

SkillExtended access
Russian stack

A kit of skills, agents and rules for 1C development in Claude Code and Cursor: metadata, forms, DCS, extensions, infobases and web client

SkillBroad access170
Russian stack

A Copier project template for 1C with a bundle of SKILL.md files for Claude Code and Codex: dump, load, tests and extension builds via stable scripts

SkillExtended access2
Russian stack

A toolkit for 1C development with an agent: skills, rules, roles, an MCP server for the NinjaLive extension and an OpenCode installer for Windows

WorkflowBroad access1
Russian stack

Universal Agent Skills for safely working with 1C extensions: an isolated session, selective export and validation before applying changes

PluginExtended access24

Cursor skills for 1C

1C Cursor skills

Russian stack

A set of Cursor skills for 1C: an analyst skill with a task template, configuration and extension editing, SKD, forms, tests and platform tooling

SkillExtended access

README in short

The README covers connecting via a git submodule and bootstrap scripts, the kit-layout engine as a declarative alternative to link scripts, kit-agent guard rules for agents, and an extensive pitfalls section: symlink/junction conflicts, foreign-namespace traps in sandboxes, PowerShell encoding, submodule downgrades and pruning, symlink permissions on Windows. It separately describes the vendored cc-1c-skills, the Cursor overlay (slices A and B with specific skills), and optional pi harness integration. The license is stated in LICENSE, with third-party licenses collected in THIRD_PARTY_LICENSES.md.

README badge

Report a problem