krrkt
Skill13 starsChanged 8 months agoMITView on GitHub
Check Russian text quality using the krrkt CLI tool — gives an objective 0-10 score with categorized findings. Use when: (1) user writes or edits Russian text and asks to check quality, (2) user says "проверь качество текста", "проверка качества", "стоп-слова", "krrkt", "check text quality", (3) user asks to score Russian writing style, (4) user opens a Russian .md/.txt file and asks for quality feedback, (5) user asks you to write Russian text — check it with krrkt before delivering. Requires krrkt CLI (pip install krrkt). NOT for English text, translation, or spelling/grammar (use ru-textovod for that).
- Installs packages
In this repository5 other files it gives its agents.
- ascii-art-beautifierSkill
- en-ru-translator-advSkill
- ru-editorSkill
- ru-textovodSkill
- telegram-cliSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Always use --no-llm (instant, no API needed).
- Very specific: line 39
Checking existing text: Run krrkt check --no-llm, show the score and key findings (weight 80+).
- Very specific: line 41
Writing new Russian text: Write it, then run krrkt check --no-llm on your output.
- Very specific: line 55
If krrkt is not found: pip install krrkt or uvx krrkt check --no-llm "test".
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
krrkt — Russian Text Quality Checker
CLI tool that scores Russian text 0-10 and flags stop words, stamps, bureaucratese, and other informational style issues. 1200+ pattern dictionary, Glvrd-compatible scoring.
Quick check
krrkt check --no-llm "Text to check"Always use --no-llm (instant, no API needed). For files: krrkt check --no-llm /path/to/file.txt.
JSON output: krrkt check --no-llm --format json "Text"
Score only: krrkt score --no-llm "Text"
Score: 7.5+ green, 5-7.4 orange, below 5 red
Workflow
Checking existing text: Run krrkt check --no-llm, show the score and key findings (weight 80+). Suggest fixes based on finding descriptions. krrkt already categorizes issues — use its output directly rather than re-analyzing from scratch.
Writing new Russian text: Write it, then run krrkt check --no-llm on your output. If score is below 7, fix the flagged issues and re-check. Deliver the final version with the score.
Checking .md files: Extract prose only — skip YAML frontmatter, code blocks, HTML, markdown syntax.
Batch: for f in *.md; do echo "=== $f ===" && krrkt score --no-llm "$f"; done
Interpreting findings
krrkt output is self-explanatory: each finding has a rule name, weight, and often a description with fix advice. Focus on ■ markers (weight 80-100) — those are the real problems. ▲ (1-79) are suggestions. ○ (0) are informational.
The description field in JSON output often contains the specific fix (e.g., "Замените на «общение»" for pompous words). Use it.
Install
If krrkt is not found: pip install krrkt or uvx krrkt check --no-llm "test".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

