CC zup-hr-api-reference
Справочник API конфигурации 1С:ЗУП 3.1 (Зарплата и управление персоналом) по кадровому учету. Используй при разработке/доработке на ЗУП 3.1, когда нужны методы КадровыйУчет, КадровыйУчетРасширенный, ЗарплатаКадры, ФизическиеЛицаЗарплатаКадры - получение кадровых данных сотрудников и физлиц, стажи, даты приема/увольнения, договоры ГПХ, совместители, штатное расписание, остатки отпусков, паспортные данные, склонение ФИО, представления СКД ЗУП. Также расчетная часть: средний заработок и его перерасчет, начисления (план видов расчета, регистр расчета), пособия и обмен с СФР (СЭДО), страховые взносы, регламентированная и статистическая отчетность, корректировка движений через ПереносДанных. НЕ использовать для БП, ERP, УТ, УНФ - только ЗУП
Справочник API конфигурации 1С:ЗУП 3.1 (Зарплата и управление персоналом) по кадровому учету. Используй при разработке/доработке на ЗУП 3.1, когда нужны…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
medium Obfuscation
uni-mixed-script-wordreferences/zup-hr-api.md:90Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (4 occurrences)**Контакты:** `АдресМестаПроживания(Представление)`, `АдресПоПрописке(Представление)`, `ТелефонМобильный(Представление)`, `EMail(EMailПредставление)`
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 593 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Structure: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 744: enough signal without eating the budget
- +3Step-by-step instructions: 26 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.