Ru Score Skill for Claude

Russian Text Quality Score

Score the text provided in $ARGUMENTS (or the most recent Russian text output if no arguments) using the ru-text scoring rubric.

Procedure

Where the reference files live

This skill reads the corpus that ships with the ru-text skill, which is installed

alongside it. Locate that folder once, then read the named files from it:

• Look for a directory named references whose parent directory is named ru-text, and

which contains info-style.md. Every file named below sits in that folder.

• In Claude Code the plugin root is also available directly, which saves the search.
• Do not guess a path. If the folder cannot be found, say so and stop — a check run

against remembered rules instead of the corpus is not this command, and reporting one

as the other is the failure this whole product exists to prevent.

• Load rubric — read scoring.md for the full rubric with anchors.

• Determine domain — identify whether the text is UI/interface, business email, article, or general:
• UI text → also load ux-writing.md for the Reader Precision dimension
• Business email → also load business-writing.md for the Reader Precision dimension
• General → use info-style.md only

• Evaluate each dimension separately — score in this order:
• T — Типографика (weight 0.15): quotes, dashes, spaces, special characters per typography.md
• Ч — Чистота языка (weight 0.25): stop-words, bureaucratic language, clichés, passive voice per info-style.md + anti-patterns.md
• Г — Грамотность (weight 0.20): punctuation, agreement, tautology per editorial-grammar.md + editorial-punctuation.md
• С — Структура (weight 0.20): logical flow, paragraphs, transitions, heading use per info-style.md structure section + addenda.md
• Ц — Точность для читателя (weight 0.20): facts, evidence, reader benefit, actionability per domain rules

• For each dimension — assign a score (0.0–10.0) using the rubric anchors in scoring.md. List 1–3 specific issues, quoting the problematic text fragment.

• Apply non-compensatory rules:
• Any dimension < 3.0 → cap total at 5.0
• Typography < 4.0 → cap total at 7.0
• Grammar < 4.0 → cap total at 7.0
• Use the most restrictive cap when multiple conditions trigger

• Compute composite score:

   S = round₁(T × 0.15 + Ч × 0.25 + Г × 0.20 + С × 0.20 + Ц × 0.20)

• Short text warning — if text is under 50 words, prepend a reliability caveat.

Score labels

| Score | Label |

|---|---|

| 9.0–10.0 | Эталонный |

| 7.0–8.9 | Хороший |

| 5.0–6.9 | Средний |

| 3.0–4.9 | Слабый |

| 0.0–2.9 | Критический |

Output format

Read-only — do NOT modify the source files. ru-score reports a score and issues; it must not write to, edit, or overwrite the analysed file(s).

In Claude Code this is hardened by disallowed-tools, which removes the listed tools while the command is active — verified on 2.1.220. The list removes the direct file-writers Write, Edit and NotebookEdit, plus the command-executing tools we identified and tested: Bash, PowerShell and Monitor. It names the paths we closed, not every path that exists. allowed-tools pre-approves tools; it does not restrict them.

Four limits, stated plainly. A connected MCP server can expose write tools that a per-tool denial list cannot know about. A named subagent whose own definition grants it tools: Write is governed by that definition, not by this list. A later Claude Code release can add a tool this file does not name. And on hosts without disallowed-tools support the rule is an instruction rather than a platform guarantee.

The contract itself is behavioural and does not depend on the list: this command returns a score and never writes.

The report shape is not written twice. Read section «Output format» of scoring.md —

the mandated heading, the five Russian dimension labels, the per-cell limit of one to

three issues with quoted fragments, the weighted formula, the cap note, and the closing

«Что оценка не измеряет» section — and follow it exactly.

That file is the single source of it. A copy lived here until v2.0 and sat outside the

no-loss gate, so the two could drift and only a reader comparing them would notice.

If a dimension has no issues, write «Замечаний нет» in the remarks column.