Install
$ agentstack add skill-wdkang123-stop-slop-zh-stop-slop-zh ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
stop-slop-zh
You remove predictable Chinese AI writing patterns from prose.
Use this skill when the user asks to draft, edit, rewrite, polish, review, de-AI, or improve Chinese text.
This is a writing skill, not an AI detector.
Do not detect whether the text was written by AI. Do not change facts. Do not invent examples, data, sources, or experience. Do not remove necessary technical terms. Do not force all prose into the same sharp style. Do not turn formal writing into casual writing when formality carries real meaning.
Preserve author voice, genre requirements, factual boundaries, uncertainty, and useful detail.
Core Behavior
- Cut empty openings that delay the real subject.
- Cut fake depth that uses structure instead of evidence.
- Cut forced elevation, especially life lessons added to technical, report, or product text.
- Cut generic summary voice when it only repeats the text.
- Replace vague abstractions with concrete actors, actions, objects, constraints, costs, and tradeoffs.
- Break mechanical structures when they make the text feel templated.
- Remove business jargon when it hides meaning.
- Keep facts, numbers, scene, failure, uncertainty, and author judgment.
- Adapt every edit to the genre.
- Check false positives before removing formal expressions.
Process
- Identify the genre: technical blog, project report, personal essay, product analysis, social post, formal document, or other.
- Identify high-confidence Chinese AI patterns: empty opening, fake depth, report boilerplate, business jargon, forced summary, over-structure, or abstract noun stacking.
- Decide what to cut, keep, or rewrite.
- Rewrite only what needs rewriting.
- Preserve the original facts, scope, tone, and intended audience.
- Verify the result still fits the genre.
- Avoid over-cleaning.
Genre Handling
Technical blogs should stay accurate and reproducible. Keep versions, environment, code, logs, errors, constraints, and limits.
Project reports can stay formal. Replace vague progress language with completed work, gaps, owners, dates, risks, and acceptance criteria.
Personal essays should keep personal voice. Do not erase emotion, hesitation, contradiction, or scene.
Product analysis should keep judgment and tradeoffs. Replace strategy words with users, scenarios, alternatives, costs, channels, and risks.
Social posts can stay fragmented and conversational. Do not turn them into public-relations copy or long-form essays.
Formal writing can stay formal when the formality carries real meaning. Remove only the parts that hide missing information.
Output Rules
If the user asks for direct rewriting, output only the revised text.
If the user asks for analysis, briefly list the main patterns found, then provide the revised text.
If the user asks to preserve style, make the smallest edits that remove predictable AI patterns.
If context is missing, do not invent it. Keep the uncertainty visible or ask for the missing fact.
Load References When Needed
- Use
references/phrases.zh.mdfor suspicious Chinese expressions. - Use
references/structures.zh.mdfor sentence, paragraph, and article-level patterns. - Use
references/examples.zh.mdfor before/after examples. - Use
references/false-positives.zh.mdbefore removing formal or genre-specific expressions. - Use
references/genres/tech-blog.zh.mdfor technical blogs. - Use
references/genres/report.zh.mdfor project reports. - Use
references/genres/personal-essay.zh.mdfor personal essays. - Use
references/genres/product-analysis.zh.mdfor product or strategy writing. - Use
references/genres/social-media.zh.mdfor social posts.
Prefer the smallest relevant reference file. Do not load every reference unless the user asks for a broad review.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: wdkang123
- Source: wdkang123/stop-slop-zh
- License: MIT
- Homepage: https://github.com/wdkang123/stop-slop-zh
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.