AD cleverence-mslx
Read, understand and safely edit Cleverence Mobile SMARTS (Склад 15 / Магазин 15) configuration stored as .mslx files - the XML algorithm graphs that drive handheld terminal (ТСД) workflows in 1C integration projects. Use this skill whenever the task touches Cleverence / Mobile SMARTS / "Клеверенс" / ТСД algorithms, .mslx files, document types or operations (обработчики) on the terminal, menu/scan/КМ logic on a scanner, calling 1C online from the TSD, or "почему скан не срабатывает / действие не найдено / кнопка не работает" on a handheld - even if the user does not say ".mslx" explicitly. Covers the action graph, transition chaining, OperationAction parameter mapping, the online 1C call mechanism, marking-code (КМ) line operations, and the CL_-copy rule for not breaking vendor operations on update.
Read, understand and safely edit Cleverence Mobile SMARTS (Склад 15 / Магазин 15) configuration stored as .mslx files - the XML algorithm graphs that drive…
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
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
- 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/online-1c-call.md:18Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (3 occurrences)<InvokeParameter name="Параметр1" type="String" value="{ВыражениеMS}"/>
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 49/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
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 27 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3120 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 810: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +5Description quotes 2 example trigger phrases
- +4Structure: 12 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.