원클릭으로
skill-reading-protocol
Mandatory protocol for reading skills and rules by a subagent at startup. Common to all subagent profiles.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Mandatory protocol for reading skills and rules by a subagent at startup. Common to all subagent profiles.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
When writing or reviewing BSL, apply 1C standards
При написании или ревью BSL применять стандарты 1С
Orchestrator: routing work and agent phases
Оркестратор: маршрутизация работы и фаз агентов
BSL LSP navigation: definitions, refs, call graph
Rules for using RLM tools for project search and navigation in 1C/BSL
| name | skill-reading-protocol |
| description | Mandatory protocol for reading skills and rules by a subagent at startup. Common to all subagent profiles. |
| alwaysApply | true |
This rule is the single source of truth for the skill and rule reading protocol. Every subagent profile references it instead of duplicating the text. The rule is read IN FULL at startup (like all rules).
CRITICAL: Mandatory reading of skills and rules:
At the end of the profile prompt there is a depends_on section with a list of dependencies.
In the header there is a skills: field with a list of skills.
Skills are NOT loaded automatically. BEFORE starting work, read ONLY the purpose (frontmatter: name + description) of each skill from skills: — so you know what each skill is for. Read the full body of SKILL.md lazily — at the moment you actually apply that skill. Rules (step 4 below) are read IN FULL at startup — these are guardrails, and you must know them before the first action.
Failing to apply the needed skill is a protocol violation. Do not create an artifact without having read and applied the corresponding skill.
.install-session.json in the project rootcomponent_map field is a dictionary "type/name" → {ru_path, en_path}skills: in the header:
skill/{name} key in component_mapname + description) from ru_path (or en_path) — record the skill's purpose[SKILL_NOTED] {name} — purpose recorded[SKILL_READ] {name} — read before applicationdepends_on containing /rules/:
namerule/{name} key in component_mapen_path (or ru_path if EN is unavailable)