stop-slop-zh
Prevents low-quality AI-generated Chinese content from reaching users by enforcing linguistic standards, reducing brand damage and ensuring professional outpβ¦
π« Stop AI slop in Chinese writing. εΉ²ζδΈζ AI ε³ β banned words, punctuation rules, structure constraints & 4-layer QA. Works with Claude Code, Cursor, Codex CLI.
- Ask Claude to identify and remove AI-generated language patterns from Chinese technical documentation.
- Generate cleaner Chinese content by applying banned-word filters and punctuation rules automatically.
- Audit Chinese writing for artificial phrasing before publishing to catch AI-slop before release.
Prevents low-quality AI-generated Chinese content from reaching users by enforcing linguistic standards, reducing brand damage and ensuring professional output in Chinese-speaking markets.
Content teams and engineering leads producing Chinese-language documentation, marketing, or user-facing materials requiring quality gates.
https://github.com/pencil20388-eng/stop-slop-zh
By pencil20388-eng
How to Get It
claude plugins install pencil20388-eng/stop-slop-zh
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Identify and remove AI-generated language patterns from Chinese technical documentation
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good β it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 36 GitHub stars; 1 contributors; last commit 53d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying β
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 36 GitHub stars; 1 contributors; last commit 53d ago; license MIT.