BB 1c-naparnik
1C:Naparnik (1С:Напарник) MCP server tools - BSL code analysis, review, rewriting, ITS knowledge base, platform documentation search, configuration documentation. Use when checking BSL code quality, searching ITS standards, reading platform docs, comparing versions, or finding configuration-specific documentation.
1C:Naparnik (1С:Напарник) MCP server tools - BSL code analysis, review, rewriting, ITS knowledge base, platform documentation search, configuration…
As a process B 67/100 · Nearly there — weak spots: result and completion, when it triggers, running it twice
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-wordSKILL.md:161Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (4 occurrences)| `query` | да | Поисковый запрос (например: "HTTPСоединение", "ЗаписьJSON") |
Files scanned: 1. 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 67/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70Execution cost. Instruction body is 4038 tokens
- 100Tools and files. No external tools needed
- 100Steps. 49 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +3Description length 315: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (7 code blocks)
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.