1c Form Inspect

Community

comol

1c-form-inspect

Read 1C managed and ordinary forms — similar forms, element trees, bindings, commands, handlers, form / role / report artifacts, form XSD or format spec — via the code-metadata, graph and docs MCP. Use before generating or changing a form; mutations go through 1c-metadata-manage.

Overview

Publisher	comol
Repository	`ai_rules_1c`
Skill name	`1c-form-inspect`
Stars	496
Forks	112
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by comol on GitHub. Read the source before you install it.

Installation

Install the 1c Form Inspect AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/comol/ai_rules_1c/tree/main/content/skills/1c-form-inspect
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/comol/ai_rules_1c.git /tmp/ai_rules_1c
mkdir -p .claude/skills
cp -r /tmp/ai_rules_1c/content/skills/1c-form-inspect .claude/skills/1c-form-inspect

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 1c Form Inspect in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads 1c Form Inspect on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 1c Form Inspect is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

1c-form-inspect — read forms before touching them

Read-only. Creating or editing Form.xml is the 1c-metadata-manage skill (docs/form-manage.md, form-compile DSL); design rules — content/rules/forms.md. Hand-writing a form while the skill is available is a defect.

Tools and exact arguments

Need	Call	Arguments
Similar existing forms as examples	`search_forms` (code)	`query`, `limit=10`
Element tree, bindings, commands, handlers	`inspect_form_layout` (code)	`object_name`, `form_name=""` (empty = default form)
Form artifact with provenance	`get_form_artifact` (code)	`object_name`, `form_name` or `artifact_id`, `include_ranges=true`
Graph view of a form	`get_form_structure` / `find_form_links` (graph)	Required `form_name`, optional `object_name`, `form_kind="any"` (`managed` / `ordinary` / `any`); explicit resolved `project_id`
XML rules of the target	`get_xsd_schema` (code)	`object_type="Форма"` (also `Справочник`, `Документ`, `Роль`, `СКД`, `Макет`; English aliases accepted)
On-disk format specification	`formatspec` (docs)	`name="1c-form-spec"` or `query="реквизиты формы"`

Graph form tools use names, not form_ref. Keep the returned base project_id bound to the current roots and verify the relevant layer (content/rules/multi-contour-search.md). find_form_links resolves event/command handlers in that form's own module; an identically named routine elsewhere is not the handler.

Calls

json
{"tool": "search_forms", "args": {"query": "ФормаДокумента Реализация", "limit": 10}}
{"tool": "inspect_form_layout", "args": {"object_name": "Документ.РеализацияТоваровУслуг", "form_name": "ФормаДокумента"}}
{"tool": "get_form_structure", "args": {"project_id": "<resolved-project-id>", "object_name": "Документ.РеализацияТоваровУслуг", "form_name": "ФормаДокумента", "form_kind": "managed"}}
{"tool": "get_xsd_schema", "args": {"object_type": "Форма"}}
{"tool": "formatspec", "args": {"name": "1c-form-spec"}}

Ordinary forms

Forms/<Имя>/Ext/Form.bin is a binary container: none of the XML routes see it. Read it with unpack_ordinary_form(form_path, workspace_path) and write it back with build_ordinary_form(workspace_path, output_path, verify=true) — the contract, workspace layout and the verification.status == "match" criterion are in content/skills/v8unpack-cf/SKILL.md → Ordinary forms. Never edit Form.bin directly.

After the change

verify_xml(xml_content, object_type="Форма") plus the skill's form-validate; syntaxcheck_file on the regenerated form module — 1c-validate. Typed answers map to actions by code — content/rules/mcp-policy.md → C. Server answers → actions.

Details: content/skills/mcp-1c-tools/docs/1c-code-metadata-mcp.md → Forms, content/skills/mcp-1c-tools/docs/1c-graph-metadata-mcp.md → Forms.

Frequently asked questions

What does the 1c Form Inspect AI skill do?

Why use 1c Form Inspect on TypingMind?

Because you install it once and use it with any model. 1c Form Inspect is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install 1c Form Inspect in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/comol/ai_rules_1c/tree/main/content/skills/1c-form-inspect. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use 1c Form Inspect?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with 1c Form Inspect?

As many as you like. As long as a model supports skills, you can use 1c Form Inspect with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the 1c Form Inspect AI skill free?

It is published on GitHub by comol. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Domain Modeling

mattpocock

CommunityPopular

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.

Writing Fragments

Writing, explore: mine raw fragments, no structure yet.

Writing For Agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Auteur

Design and build cinematic, award-level web pages.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

1c-form-inspect — read forms before touching them

Tools and exact arguments

Calls

Ordinary forms

After the change

Frequently asked questions

Related AI Skills

Set up your own AI workspace now