agentleFS
gybson63gybson63/1c-oData-skill/skills/analyst/SKILL.md

analyst

Skill8 starsChanged 5 months agoMITView on GitHub

Аналитик метаданных 1С: определяет объекты конфигурации для OData-запросов. Используй MCP conf-doc, profile конфигурации и skills analyst-conf-doc, analyst-domain, analyst-mcp. Standalone: /analyze или [analyze].

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use editor.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • QinghongLinSkill

    editor

    Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).

    Also in 3 projects that use this

The file

Files
SKILL.md

analyst — аналитик метаданных 1С

Агент не выполняет OData — только выбирает объекты метаданных и их роли.

Связанные skills

SkillНазначение
analyst-conf-docMCP conf_doc_* для поиска
analyst-domainProfile, decision trees
analyst-mcpКаталог MCP-инструментов
conf-docБазовый справочник conf-doc

Workflow

- [ ] Прочитать profile: skills/analyst/profiles/<config>.md
- [ ] conf_doc_health + conf_doc_list_configurations
- [ ] Короткие keyword → conf_doc_search (не полный текст вопроса!)
- [ ] Drill-down: conf_doc_get_object → conf_doc_get_object_chunk
- [ ] Для отчётов: чанки «Запрос СКД» → регистры-источники
- [ ] Сверить с profile (decision trees, anti-patterns)
- [ ] SearXNG — только если conf_doc + profile не хватило (см. [`docs/searxng.md`](../../docs/searxng.md))
- [ ] Выдать MetadataBrief

Profile конфигурации

Выбери profile по CONF_DOC_CONFIGURATION:

КонфигурацияProfile
ЗарплатаИУправлениеПерсоналомКОРПprofiles/zup-korp.md

Шаблон нового profile: profiles/_template.md

Формат MetadataBrief

intent: vacation_balance
primary_objects:
  - meta_type: InformationRegister
    name: АналитикаОстатковОтпусков
    odata_entity: InformationRegister_АналитикаОстатковОтпусков
    role: primary
    reason: "готовый остаток в днях"
secondary_objects: []
avoid:
  - InformationRegister_ОстаткиОтпусков
conf_doc_queries: ["остатки отпусков", "АналитикаОстатковОтпусков"]
notes: "остаток = накоплено − израсходовано"

Роли: primary | join | source | avoid

Бот

  • Standalone: /analyze <вопрос> или префикс [analyze]
  • Auto pre-step: результат вставляется в OData Step 1 как блок «АНАЛИЗ МЕТАДАННЫХ»

Конфиг: env.json → agents.analyst, shared MCP → profiles.default.mcp_servers

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.