source-access

Resolve 1C metadata targets and read source snapshots through the Unica MCP server.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill source-access-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-access
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/source-access
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill source-access-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Navigating a 1C:Enterprise source tree by physical file paths is error-prone: modules, forms, and metadata objects are scattered across directories, and manual path guessing breaks whenever the layout changes. This Skill maps logical 1C targets (documents, modules, forms) to their resources and reads them safely through the Unica MCP server. ## Core Features & Use Cases - Logical target resolution: Resolve English or Russian metadata names (e.g. Document.ЗаказКлиента.ObjectModule) with unica.source.resolve, browse one tree level with unica.source.children, and convert physical paths from search results or build logs back into logical addresses with unica.source.locate. - Snapshot-safe resource reading: Inspect resource manifests (role, size, hash, text profile) via unica.source.resources, then read fragments with unica.source.read while honoring maxReadBytes, UTF-8 boundary truncation, byte offsets, BOM, and EOL profiles. - Previewed BSL patching: Apply targeted edits with unica.code.patch using insert or replace operations on a method or anchor selector, always previewing with dryRun: true before committing. - Use Case: A build log reports an error in a module file. Use unica.source.locate to find the owning metadata object, read the module fragment by fragment, then patch the failing procedure with a dry-run preview before applying the fix. ## Quick Start Ask the assistant to resolve the metadata path Document.ЗаказКлиента.ObjectModule in the main sourceSet and read its module through the Unica MCP source tools.

Frequently Asked Questions about source-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find a 1C metadata object from a physical file path?▼

Use unica.source.locate to translate a physical path from code search, a diff, or a build log into a logical metadata address. It also reports the file owner, such as the metadata object for a module, and returns typed refusals like outsideSourceSet or notAddressable.

How to read large 1C modules without exceeding size limits?▼

Read the resource in fragments with unica.source.read, advancing by the returned length rather than the requested limit. Fragments are truncated at UTF-8 boundaries, offsets address bytes not characters, and contentEncoding base64 means exact bytes rather than re-encodable text.

Can I edit BSL code through the Unica MCP source tools?▼

The resource group is read-only; edits go through unica.code.patch with insert or replace operations targeting a method or anchor selector. Always run with dryRun true first to review the diff and BSL validation, then repeat with dryRun false.

Why does a partial Russian metadata name fail to resolve?▼

In prefix mode only canonical English tokens may be incomplete, such as Doc or Su. A Russian alias like Документ works only in full form, while a partial alias like Док is rejected because it has no single canonical completion.

What are the limitations of the source-access workflow?▼

It requires the Unica MCP server and a valid sourceSet; internal MCP or CLI adapters must not be called directly. Resource access is read-only, and any patch preview must be redone if the selector or content changes.