stop-slop

Removes predictable AI writing patterns from Russian-language chat messages for 1C development workflows.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill stop-slop-pavelvdo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stop-slop
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/stop-slop
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill stop-slop-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI assistants produce recognizable filler patterns in Russian chat messages — empty openers, vague intensifiers, impersonal passive voice, and jargon copied verbatim from design artifacts. This Skill provides a rule catalog and scoring rubric to detect and rewrite those patterns before messages reach the user. ## Core Features & Use Cases - RU-adapted slop rules: Eight rule categories covering filler openers, artificial contrasts, empty intensifiers, impersonal passive voice, meta-commentary, pull-quotes, and vague jargon, each with before/after replacement tables. - Pre-send scoring rubric: A five-dimension self-check (directness, rhythm, trust, liveliness, density) where text scoring below 35/50 must be rewritten. - Artifact-to-chat translation: Guidance for converting English labels and codes copied from design.md, tasks.md, and verification reports into plain Russian for decision forks. - Use Case: Before sending a verify summary to a 1C developer, run the self-check against the catalog in references/ai-tells-ru.md and rewrite phrases like "Стоит отметить" or "blast radius" into concrete statements about what breaks and what the user must decide. ## Quick Start Review my draft chat message with the stop-slop rules and rewrite any AI-sounding phrases into direct Russian.

Frequently Asked Questions about stop-slop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove AI-sounding phrases from Russian chat messages?▼

Check the draft against the eight rule categories: remove filler openers like "Конечно!" and "Давайте разберёмся", replace empty intensifiers with facts, and convert impersonal passive constructions into statements with a clear subject. Score the result on the five-dimension rubric and rewrite if below 35/50.

What is the stop-slop skill used for in a 1C Cursor project?▼

It cleans AI-generated Russian text in chat during 1C development workflows. Load it when editing verify, extend, or explore templates, and as a self-check before the orchestrator sends messages to the user.

Does stop-slop allow em dashes in Russian text?▼

Yes. Unlike the English original, the Russian adaptation permits em dashes because they are normative Russian punctuation. The adaptation instead bans filler openers, empty intensifiers, and impersonal passive voice.

How do I translate technical jargon from design artifacts into chat messages?▼

Never copy labels like "Interim", "Parity", or codes like "OQ1" verbatim from design.md or tasks.md into chat. Translate them into plain Russian using the replacement tables in references/ai-tells-ru.md section 7, and move raw codes to a Sources line at the end.

When should the stop-slop scoring rubric be applied?▼

Apply it before sending any long message to the user. Rate directness, rhythm, trust, liveliness, and density; if the total falls below 35 out of 50, rewrite the text using the catalog's replacement tables.