composing-1c-queries

Compose 1C:Enterprise query language queries with metadata verification and performance optimization.

224|52|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ROCTUP/1c-mcp-toolkit --skill composing-1c-queries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: composing-1c-queries
Source: https://github.com/ROCTUP/1c-mcp-toolkit/tree/main/skills/composing-1c-queries
Command: npx skills add https://github.com/ROCTUP/1c-mcp-toolkit --skill composing-1c-queries

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity and potential errors in writing 1C:Enterprise query language (язык запросов 1С), ensuring accurate and optimized data retrieval from 1C databases.

Core Features & Use Cases

  • Query Composition: Generates correct 1C queries based on specified requirements, including structure, table/field naming, joins, grouping, and parameter usage.
  • Metadata Verification: Emphasizes the critical need to use get_metadata to confirm object and field names, preventing runtime errors.
  • Performance Optimization: Provides guidance on using virtual tables correctly, indexing, and avoiding common pitfalls for efficient query execution.
  • Use Case: When an agent needs to retrieve a list of all customers from the 'Customers' catalog who made purchases over $1000 in the last month, this Skill will compose the appropriate ВЫБРАТЬ/ИЗ/ГДЕ query, ensuring correct table and field names are used.

Quick Start

Use the composing-1c-queries skill to generate a 1C query that selects the 'Name' and 'Code' fields from the 'Catalog.Customers' table, filtering for entries where the 'City' field is 'Moscow'.

Frequently Asked Questions about composing-1c-queries

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

FAQPage Schema
How do I write a 1C query to retrieve data from a specific catalog?

Writing a 1C query requires structuring a ВЫБРАТЬ/ИЗ/ГДЕ statement with correct metadata object names. This Skill composes accurate 1C:Enterprise queries by verifying table and field names against metadata, ensuring proper joins, grouping, and parameter usage for reliable data retrieval.

Why does my 1C:Enterprise query fail with a field name error?

1C:Enterprise query errors often occur when field or table names do not match the database metadata. This Skill prevents runtime failures by emphasizing metadata verification using `get_metadata` to confirm exact object naming before composing the query structure.

What is the best way to optimize 1C queries for large datasets?

Optimizing 1C queries involves using virtual tables correctly, applying indexing, and avoiding common structural pitfalls. This Skill provides performance best practices for query composition, ensuring efficient data retrieval and analysis within 1C environments.

Can I use temporary tables and joins in 1C:Enterprise query language?

Yes, 1C:Enterprise query language supports temporary tables, joins, and grouping. This Skill composes queries incorporating these advanced features while maintaining proper parameter usage and metadata verification to build accurate reports and retrieve data.

How do I filter 1C catalog entries based on specific conditions?

Filtering 1C catalog entries requires a WHERE clause in the query language referencing verified metadata fields. This Skill composes conditional queries, such as filtering customers by city or purchase amount, ensuring correct field selection and parameter usage.

Does this approach support building reports directly from 1C databases?

Yes, building reports from 1C databases is a primary use case for the query language. This Skill facilitates data querying and report building by composing structured queries with correct metadata object naming, field selection, and grouping for analysis.